Observed topology
AS60068 CDN77 _
Hosting RIPE Content
Transit
Upstream networks
Networks observed carrying traffic for AS60068: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 6,358 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 3,788 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,086 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,045 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 1,696 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,539 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 1,440 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 1,067 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 985 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 670 |
Transit
Downstream networks
Networks for which AS60068 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS212238 | Datacamp Limited | Hosting | IPv4 IPv6 | 197,534 |
| AS136787 | PacketHub S.A. | VPN | IPv4 IPv6 | 42,118 |
| AS209854 | Cyberzone S.A. | VPN | IPv4 IPv6 | 18,733 |
| AS198566 | FZCO | Unclassified | IPv4 | 15,540 |
| AS40509 | Fly.io, Inc. | Unclassified | IPv4 IPv6 | 13,539 |
| AS206092 | F.N.S. HOLDINGS LIMITED | Unclassified | IPv4 | 13,161 |
| AS215294 | Lumina broadband UAB | Unclassified | IPv4 IPv6 | 10,964 |
| AS206150 | F.N.S. HOLDINGS LIMITED | Unclassified | IPv4 IPv6 | 8,770 |
| AS214647 | Yadda OU | Unclassified | IPv4 IPv6 | 7,095 |
| AS62651 | Strong Technology, LLC. | VPN | IPv4 IPv6 | 6,041 |
Adjacency
Adjacent networks
Every AS seen directly next to AS60068 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS212238 | Datacamp Limited | Hosting | IPv4 IPv6 | 197,534 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 118,733 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 103,304 |
| AS136787 | PacketHub S.A. | VPN | IPv4 IPv6 | 93,094 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 49,976 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 48,455 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 41,016 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 35,228 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 31,992 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 26,968 |
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.