asn.dev

Observed topology

AS203478 TBSPACE tbspace Networks

Unclassified RIPE Non-Profit

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203478: 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
AS206499LOCIX LIMITEDUnclassifiedIPv4 IPv652
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv4 IPv633
AS6939Hurricane Electric LLCTransitIPv48
AS24482SG.GSHostingIPv4 IPv62
AS401753BIXCE IncUnclassifiedIPv4 IPv62
AS34927iFog GmbHHostingIPv41
AS57821Nonattached Network e.V.UnclassifiedIPv41
AS202365Omer GOLGELIUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208340Tobias SchrammUnclassifiedIPv4 IPv639

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS206499LOCIX LIMITEDUnclassifiedIPv4 IPv677
AS208340Tobias SchrammUnclassifiedIPv4 IPv639
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv4 IPv635
AS6939Hurricane Electric LLCTransitIPv414
AS24482SG.GSHostingIPv4 IPv64
AS401753BIXCE IncUnclassifiedIPv4 IPv64
AS34927iFog GmbHHostingIPv42
AS202365Omer GOLGELIUnclassifiedIPv42
AS57821Nonattached Network e.V.UnclassifiedIPv41

Provenance

Where this comes from

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