Observed topology
AS16524 METTEL
Unclassified ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS16524: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 6,227 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,483 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 592 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 548 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 442 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 144 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 | 85 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 60 |
| AS28394 | Bicentel SA de CV | Unclassified | IPv4 | 32 |
| AS701 | Verizon Business | Residential | IPv4 | 8 |
Transit
Downstream networks
Networks for which AS16524 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS26229 | U.S. Securities & Exchange Commission | Unclassified | IPv4 | 419 |
| AS12037 | Federal Deposit Insurance Corporation | Unclassified | IPv4 | 344 |
| AS21617 | National Archives and Records Administration | Unclassified | IPv4 | 298 |
| AS36569 | Hearst-Argyle Television, Inc. | Unclassified | IPv4 | 61 |
| AS39983 | Pension Benefit Guaranty Corp. | Unclassified | IPv4 | 60 |
| AS40323 | Virginia Farm Bureau Mutual Insurance Company | Unclassified | IPv4 | 60 |
| AS400454 | DataRemote, Inc. | Unclassified | IPv4 | 48 |
Adjacency
Adjacent networks
Every AS seen directly next to AS16524 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 6,439 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,963 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 974 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 592 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 526 |
| AS26229 | U.S. Securities & Exchange Commission | Unclassified | IPv4 | 419 |
| AS12037 | Federal Deposit Insurance Corporation | Unclassified | IPv4 | 344 |
| AS21617 | National Archives and Records Administration | Unclassified | IPv4 | 298 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 216 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 | 85 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.