Observed topology
AS13331 METAPEER-INC - MetaPeer
Hosting ARIN Content
Transit
Upstream networks
Networks observed carrying traffic for AS13331: 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 |
|---|---|---|---|---|
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 290 |
| AS7922 | Comcast Cable Communications, LLC | Residential | IPv4 IPv6 | 102 |
| AS30081 | CacheFly | Hosting | IPv4 IPv6 | 89 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 79 |
| AS19255 | YOUR.ORG, INC. | Hosting | IPv4 | 20 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 19 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 10 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 10 |
| AS293 | ESnet | Unclassified | IPv4 | 9 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 9 |
Transit
Downstream networks
Networks for which AS13331 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS4319 | Cortland Electronics Corp. | Unclassified | IPv4 | 3 |
Adjacency
Adjacent networks
Every AS seen directly next to AS13331 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 293 |
| AS7922 | Comcast Cable Communications, LLC | Residential | IPv4 IPv6 | 102 |
| AS30081 | CacheFly | Hosting | IPv4 IPv6 | 89 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 79 |
| AS19255 | YOUR.ORG, INC. | Hosting | IPv4 | 20 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 19 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 10 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 10 |
| AS293 | ESnet | Unclassified | IPv4 | 9 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 9 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.