Observed topology
AS29909 METROOPTIC
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS29909: 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 | 958 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 336 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 272 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 202 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 96 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 70 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 IPv6 | 38 |
| AS1403 | EBOX | Residential | IPv4 IPv6 | 34 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 34 |
| AS24482 | SG.GS | Hosting | IPv4 | 26 |
Transit
Downstream networks
Networks for which AS29909 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3584 | PubNIX, Inc. | Unclassified | IPv4 IPv6 | 311 |
| AS398216 | Sichuun | Unclassified | IPv4 IPv6 | 259 |
| AS14280 | Ntirety, Inc. | Hosting | IPv4 IPv6 | 206 |
| AS395663 | sergent telecom inc | Unclassified | IPv4 IPv6 | 201 |
| AS16932 | Future Electronique Inc | Unclassified | IPv4 | 177 |
| AS23471 | ited Solutions | Unclassified | IPv4 | 162 |
| AS14217 | N6 Cloud inc. | Unclassified | IPv4 IPv6 | 148 |
| AS400806 | Clearly IP Inc | Unclassified | IPv4 IPv6 | 144 |
| AS400631 | Just Some Hosting | Unclassified | IPv4 | 116 |
| AS32710 | AgniCorp Inc. | Unclassified | IPv4 | 115 |
Adjacency
Adjacent networks
Every AS seen directly next to AS29909 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,906 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 799 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 704 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 443 |
| AS3584 | PubNIX, Inc. | Unclassified | IPv4 IPv6 | 311 |
| AS398216 | Sichuun | Unclassified | IPv4 IPv6 | 259 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 252 |
| AS14280 | Ntirety, Inc. | Hosting | IPv4 IPv6 | 238 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 215 |
| AS395663 | sergent telecom inc | Unclassified | IPv4 IPv6 | 201 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M 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.