Observed topology
AS2544 METRO-AS
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS2544: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 836 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 181 |
| AS14361 | HopOne Internet Corporation | Hosting | IPv4 | 110 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 44 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 22 |
| AS7575 | Australian Academic and Research Network (AARNet) | Education | IPv4 | 22 |
| AS24482 | SG.GS | Hosting | IPv4 | 22 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 22 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 | 22 |
Transit
Downstream networks
Networks for which AS2544 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS33348 | Pierce County | Unclassified | IPv4 | 319 |
| AS32148 | King County Library System | Unclassified | IPv4 | 177 |
| AS30198 | Kent School District | Unclassified | IPv4 | 164 |
| AS399987 | Tacoma-Pierce County Health Department | Unclassified | IPv4 | 116 |
| AS63432 | Puget Sound Regional Fire Authority | Unclassified | IPv4 | 58 |
| AS396890 | City of Redmond Washington | Unclassified | IPv4 | 58 |
| AS19014 | NORCOM | Unclassified | IPv4 | 8 |
Adjacency
Adjacent networks
Every AS seen directly next to AS2544 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 1,387 |
| AS33348 | Pierce County | Unclassified | IPv4 | 319 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 305 |
| AS14361 | HopOne Internet Corporation | Hosting | IPv4 | 203 |
| AS32148 | King County Library System | Unclassified | IPv4 | 177 |
| AS30198 | Kent School District | Unclassified | IPv4 | 165 |
| AS399987 | Tacoma-Pierce County Health Department | Unclassified | IPv4 | 116 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 79 |
| AS63432 | Puget Sound Regional Fire Authority | Unclassified | IPv4 | 58 |
| AS396890 | City of Redmond Washington | Unclassified | IPv4 | 58 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.