asn.dev

Observed topology

AS8878 NFON-AS nfon AG

Unclassified RIPE

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

Transit

Upstream networks

All 24

Networks observed carrying traffic for AS8878: 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
AS33891Core-Backbone GmbHHostingIPv4 IPv640
AS6939Hurricane Electric LLCTransitIPv4 IPv622
AS1299Arelion Sweden ABTransitIPv4 IPv619
AS12337noris network AGUnclassifiedIPv410
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv68
AS8220COLT Technology Services Group LimitedHostingIPv47
AS3320Deutsche Telekom AGMobileIPv4 IPv66
AS50304Blix Solutions ASUnclassifiedIPv44
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv63

All 24 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44229nfon AGUnclassifiedIPv4 IPv693

Adjacency

Adjacent networks

All 25

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

ASNetworkTypeFamiliesPaths seen
AS44229nfon AGUnclassifiedIPv4 IPv693
AS33891Core-Backbone GmbHHostingIPv4 IPv663
AS6939Hurricane Electric LLCTransitIPv4 IPv637
AS1299Arelion Sweden ABTransitIPv4 IPv635
AS8220COLT Technology Services Group LimitedHostingIPv414
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv613
AS12337noris network AGUnclassifiedIPv410
AS3320Deutsche Telekom AGMobileIPv4 IPv69
AS50304Blix Solutions ASUnclassifiedIPv46
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv65

All 25 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.