Observed topology
AS3333 RIPE-NCC-AS Reseaux IP Europeens Network Coordination Centre RIPE NCC
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS3333: 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 |
|---|---|---|---|---|
| AS1273 | IDDQD-AS | Business | IPv4 IPv6 | 97 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 95 |
| AS1103 | SURF B.V. | Unclassified | IPv4 IPv6 | 85 |
| AS12859 | BIT BV | Hosting | IPv4 IPv6 | 31 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 19 |
| AS1136 | KPN B.V. | Residential | IPv4 IPv6 | 13 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 8 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 8 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 7 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 7 |
Transit
Downstream networks
Networks for which AS3333 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 IPv6 | 5,012 |
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 4,628 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 2,161 |
| AS5416 | B.S.C. | Unclassified | IPv4 IPv6 | 1,472 |
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 1,462 |
| AS17557 | Pakistan Telecommunication Company Limited | Unclassified | IPv4 | 1,294 |
| AS7713 | PT Telekomunikasi Indonesia | Residential | IPv4 IPv6 | 1,094 |
| AS9605 | NTT DOCOMO, INC. | Mobile | IPv4 IPv6 | 1,051 |
| AS8866 | Vivacom Bulgaria EAD | Residential | IPv4 IPv6 | 1,050 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 950 |
Adjacency
Adjacent networks
Every AS seen directly next to AS3333 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1257 | Tele2 Sverige AB | Mobile | IPv4 IPv6 | 391,074 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 142,763 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 130,810 |
| AS1273 | IDDQD-AS | Business | IPv4 IPv6 | 102,338 |
| AS1103 | SURF B.V. | Unclassified | IPv4 IPv6 | 87,860 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 67,052 |
| AS1136 | KPN B.V. | Residential | IPv4 IPv6 | 45,824 |
| AS2914 | NTT America, Inc. | Transit | IPv6 | 43,948 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 38,062 |
| AS12859 | BIT BV | Hosting | IPv4 IPv6 | 18,353 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.22M 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.