asn.dev

Observed topology

AS207995 LIGHTNINGFIBRE

Residential RIPE Cable/DSL/ISP

Upstreams 23 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 21
Adjacent (IPv6) 10
Upstream graph Who carries AS207995, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS207995 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS207995: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv661
AS6939Hurricane Electric LLCTransitIPv4 IPv651
AS3257GTT Communications Inc.TransitIPv432
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv610
AS33891Core-Backbone GmbHHostingIPv46
AS50304Blix Solutions ASUnclassifiedIPv46
AS24482SG.GSHostingIPv4 IPv64
AS48185team.blue NVUnclassifiedIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv64

All 23 upstreams →

Transit

Downstream networks

inferred

Networks for which AS207995 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS213534Gardners Books LtdUnclassifiedIPv459
AS8676PRT Systems LimitedHostingIPv458

Adjacency

Adjacent networks

All 24

Every AS seen directly next to AS207995 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS8676PRT Systems LimitedHostingIPv4103
AS3356Level 3 Parent, LLCTransitIPv4 IPv699
AS3257GTT Communications Inc.TransitIPv498
AS6939Hurricane Electric LLCTransitIPv4 IPv659
AS213534Gardners Books LtdUnclassifiedIPv459
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv619
AS50304Blix Solutions ASUnclassifiedIPv412
AS33891Core-Backbone GmbHHostingIPv48
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv67
AS3216PJSC "Vimpelcom"MobileIPv46

All 24 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.