asn.dev

Observed topology

AS51155 TBTELECOM

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51155: 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, LLCTransitIPv4132
AS6939Hurricane Electric LLCTransitIPv4 IPv660
AS9002RETN LimitedUnclassifiedIPv67
AS24482SG.GSHostingIPv4 IPv64
AS8218Zayo Infrastructure France SAUnclassifiedIPv43
AS34927iFog GmbHHostingIPv43
AS50629LWLcom GmbHUnclassifiedIPv43
AS29632Netassist International EOODUnclassifiedIPv62
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS41865BIALL-NET Sp. z o.o.UnclassifiedIPv4357
AS206651Telemedian Sp. z o.o.UnclassifiedIPv459
AS56408Gdansk Airport Sp. z o.o.UnclassifiedIPv48
AS51976JP-Telekom Sp z o.o.UnclassifiedIPv42

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4445
AS41865BIALL-NET Sp. z o.o.UnclassifiedIPv4357
AS6939Hurricane Electric LLCTransitIPv4 IPv6140
AS206651Telemedian Sp. z o.o.UnclassifiedIPv459
AS24482SG.GSHostingIPv4 IPv613
AS8218Zayo Infrastructure France SAUnclassifiedIPv410
AS34927iFog GmbHHostingIPv410
AS50629LWLcom GmbHUnclassifiedIPv410
AS56408Gdansk Airport Sp. z o.o.UnclassifiedIPv48
AS9002RETN LimitedUnclassifiedIPv67

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.