Observed topology
AS16504 GRANITE
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS16504: 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 | 6,722 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,846 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 525 |
| AS701 | Verizon Business | Residential | IPv4 | 121 |
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 | 26 |
| AS46887 | Crown Castle Fiber LLC | Unclassified | IPv4 | 16 |
Transit
Downstream networks
Networks for which AS16504 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS11394 | City of Richardson | Unclassified | IPv4 | 108 |
| AS22379 | Manifold Services Inc | Unclassified | IPv4 IPv6 | 66 |
| AS15319 | COSCO Shipping Lines (North America) Inc. | Unclassified | IPv4 | 59 |
| AS18663 | University of the Pacific | Unclassified | IPv4 | 59 |
| AS32352 | MCGRATH RENTCORP | Unclassified | IPv4 | 59 |
| AS46605 | MCGRATH RENTCORP | Unclassified | IPv4 | 59 |
| AS398219 | Inmar, Inc. | Unclassified | IPv4 | 59 |
| AS773 | Parsons Corporation | Unclassified | IPv4 | 58 |
| AS46575 | Washington Suburban Sanitary Commission | Unclassified | IPv4 | 58 |
| AS23288 | -Reserved AS- | Unclassified | IPv4 | 52 |
Adjacency
Adjacent networks
Every AS seen directly next to AS16504 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 7,295 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 5,117 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 525 |
| AS701 | Verizon Business | Residential | IPv4 | 121 |
| AS11394 | City of Richardson | Unclassified | IPv4 | 108 |
| AS22379 | Manifold Services Inc | Unclassified | IPv4 IPv6 | 66 |
| AS15319 | COSCO Shipping Lines (North America) Inc. | Unclassified | IPv4 | 59 |
| AS18663 | University of the Pacific | Unclassified | IPv4 | 59 |
| AS32352 | MCGRATH RENTCORP | Unclassified | IPv4 | 59 |
| AS46605 | MCGRATH RENTCORP | Unclassified | IPv4 | 59 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-23 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.15M 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.