Observed topology
AS12213 CNSQ-AS12213
Hosting ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS12213: 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 | 1,195 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 1,028 |
| AS2686 | AT&T Enterprises, LLC | Unclassified | IPv4 | 130 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 124 |
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 IPv6 | 108 |
| AS49915 | Megaport (UK) Limited | Unclassified | IPv4 IPv6 | 84 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 35 |
| AS25091 | IP-Max SA | Unclassified | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS12213 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS26584 | VERTAFORE, INC | Unclassified | IPv4 | 312 |
| AS16910 | Farm Credit Financial Partners, Inc. | Unclassified | IPv4 | 271 |
| AS197594 | Redstor Limited | Unclassified | IPv4 | 244 |
| AS398172 | Sirius XM Connected Vehicle Services Inc. | Unclassified | IPv4 | 244 |
| AS26842 | MFXCHANGE US, INC | Unclassified | IPv4 | 226 |
| AS15248 | Metaswitch Networks Corp. | Unclassified | IPv4 IPv6 | 190 |
| AS396163 | My Digital Shield, Inc. | Hosting | IPv4 | 190 |
| AS1379 | SINCH INTERCONNECT LLC | Unclassified | IPv4 | 183 |
| AS13690 | American Medical Response, Inc. | Unclassified | IPv4 | 183 |
| AS3573 | Accenture LLP | Unclassified | IPv4 | 122 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12213 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,919 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 2,579 |
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 IPv6 | 379 |
| AS26584 | VERTAFORE, INC | Unclassified | IPv4 | 312 |
| AS16910 | Farm Credit Financial Partners, Inc. | Unclassified | IPv4 | 271 |
| AS197594 | Redstor Limited | Unclassified | IPv4 | 244 |
| AS398172 | Sirius XM Connected Vehicle Services Inc. | Unclassified | IPv4 | 244 |
| AS2686 | AT&T Enterprises, LLC | Unclassified | IPv4 | 233 |
| AS26842 | MFXCHANGE US, INC | Unclassified | IPv4 | 226 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 209 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.