Observed topology
AS48185 TEAM_BLUE team.blue backbone
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS48185: 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 | 27 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 21 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 18 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 16 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 IPv6 | 2 |
| AS6696 | VERIXI SA | Unclassified | IPv4 IPv6 | 2 |
| AS1103 | SURF B.V. | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS48185 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,108 |
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 4,960 |
| AS34762 | Combell NV | Hosting | IPv4 IPv6 | 4,062 |
| AS20857 | Signet B.V. | Hosting | IPv4 IPv6 | 3,261 |
| AS35470 | Signet B.V. | Hosting | IPv4 IPv6 | 2,959 |
| AS9009 | M247 Europe SRL | Hosting | IPv4 IPv6 | 2,335 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 2,222 |
| AS714 | Apple Inc. | Hosting | IPv4 IPv6 | 1,712 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 1,685 |
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 1,519 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48185 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 470,242 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 183,564 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 168,622 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 96,704 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 75,300 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 IPv6 | 40,654 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 19,035 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 IPv6 | 14,766 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 13,021 |
| AS39386 | Saudi Telecom Company JSC | Unclassified | IPv4 IPv6 | 11,390 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M 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.