asn.dev

Observed topology

AS9153 BURSTFIRE-EU Burstfire Networks Ltd

Unclassified RIPE NSP

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS9153: 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
AS1299Arelion Sweden ABTransitIPv4 IPv683
AS174Cogent Communications, LLCTransitIPv4 IPv637
AS6939Hurricane Electric LLCTransitIPv427
AS34549meerfarbig GmbH & Co. KGHostingIPv49
AS50304Blix Solutions ASUnclassifiedIPv46
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS48185team.blue NVUnclassifiedIPv4 IPv64
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv64
AS3216PJSC "Vimpelcom"MobileIPv43

All 19 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202416Affiliate Squared Technologies LimitedUnclassifiedIPv4 IPv6174
AS43178unnamedUnclassifiedIPv42

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS202416Affiliate Squared Technologies LimitedUnclassifiedIPv4 IPv6174
AS1299Arelion Sweden ABTransitIPv4 IPv6165
AS174Cogent Communications, LLCTransitIPv4 IPv669
AS6939Hurricane Electric LLCTransitIPv443
AS34549meerfarbig GmbH & Co. KGHostingIPv415
AS50304Blix Solutions ASUnclassifiedIPv410
AS24482SG.GSHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv68
AS48185team.blue NVUnclassifiedIPv4 IPv68
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv68

All 23 adjacent →

Provenance

Where this comes from

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