Observed topology
AS33489 COMCAST-33489 - Comcast Cable Communications, LLC
Unclassified ARIN Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS33489: 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.
Transit
Downstream networks
Networks for which AS33489 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS14625 | PGA Tour | Unclassified | IPv4 | 232 |
| AS10851 | St Johns County BOCC | Unclassified | IPv4 IPv6 | 124 |
| AS400952 | KISS NAIL PRODUCTS, INC | Unclassified | IPv4 | 108 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 90 |
| AS36040 | Google LLC | Hosting | IPv4 | 58 |
| AS54135 | TEGNA Inc. | Unclassified | IPv4 | 58 |
| AS54943 | Stillwater Insurance Services, Inc | Unclassified | IPv4 | 58 |
| AS395202 | Bradford County Board of County Commissioners | Unclassified | IPv4 | 58 |
| AS399653 | Charleston County Aviation Authority | Unclassified | IPv4 | 58 |
| AS36174 | Baptist Health System | Unclassified | IPv4 | 47 |
Adjacency
Adjacent networks
Every AS seen directly next to AS33489 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS7922 | Comcast Cable Communications, LLC | Residential | IPv4 IPv6 | 2,340 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 255 |
| AS14625 | PGA Tour | Unclassified | IPv4 | 232 |
| AS10851 | St Johns County BOCC | Unclassified | IPv4 IPv6 | 124 |
| AS400952 | KISS NAIL PRODUCTS, INC | Unclassified | IPv4 | 108 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 90 |
| AS36040 | Google LLC | Hosting | IPv4 | 58 |
| AS54135 | TEGNA Inc. | Unclassified | IPv4 | 58 |
| AS54943 | Stillwater Insurance Services, Inc | Unclassified | IPv4 | 58 |
| AS395202 | Bradford County Board of County Commissioners | Unclassified | IPv4 | 58 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.