asn.dev

Observed topology

AS8902 IFB Internet For Business Limited

Residential RIPE

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS8902: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6225
AS3356Level 3 Parent, LLCTransitIPv4 IPv642
AS174Cogent Communications, LLCTransitIPv4 IPv626
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv616
AS24482SG.GSHostingIPv4 IPv66
AS48185team.blue NVUnclassifiedIPv4 IPv66
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv66
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv66
AS3741Dimension DataUnclassifiedIPv45
AS17639Converge ICT Solutions Inc.UnclassifiedIPv45

All 16 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197282Wood Group UK LimitedUnclassifiedIPv4197
AS1996294MS Network Solutions Ltd.UnclassifiedIPv4102

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6470
AS197282Wood Group UK LimitedUnclassifiedIPv4197
AS1996294MS Network Solutions Ltd.UnclassifiedIPv4102
AS3356Level 3 Parent, LLCTransitIPv4 IPv660
AS174Cogent Communications, LLCTransitIPv4 IPv655
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv616
AS48185team.blue NVUnclassifiedIPv4 IPv69
AS3741Dimension DataUnclassifiedIPv48
AS24482SG.GSHostingIPv4 IPv66
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv66

All 18 adjacent →

Provenance

Where this comes from

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