asn.dev

Observed topology

AS208505 TURTLEBIT TurtleBit network - AS208505

Unclassified RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS208505: 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
AS20473The Constant Company, LLCHostingIPv644
AS6939Hurricane Electric LLCTransitIPv623
AS11967Hop179 OUUnclassifiedIPv610
AS29632Netassist International EOODUnclassifiedIPv64
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv62
AS9002RETN LimitedUnclassifiedIPv62
AS17639Converge ICT Solutions Inc.UnclassifiedIPv62
AS24482SG.GSHostingIPv62
AS25091IP-Max SAUnclassifiedIPv62
AS34019Hivane AssociationUnclassifiedIPv62

All 14 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS20473The Constant Company, LLCHostingIPv644
AS6939Hurricane Electric LLCTransitIPv623
AS11967Hop179 OUUnclassifiedIPv610
AS29632Netassist International EOODUnclassifiedIPv64
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv62
AS9002RETN LimitedUnclassifiedIPv62
AS17639Converge ICT Solutions Inc.UnclassifiedIPv62
AS24482SG.GSHostingIPv62
AS25091IP-Max SAUnclassifiedIPv62
AS34019Hivane AssociationUnclassifiedIPv62

All 14 adjacent →

Provenance

Where this comes from

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