Observed topology
AS6300 CCI-TEXAS - Fidium
Residential ARIN Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS6300: 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 AS6300 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS19201 | Eastex Telephone Cooperative, Inc. | Unclassified | IPv4 IPv6 | 1,213 |
| AS17093 | Fidium | Unclassified | IPv4 | 295 |
| AS16716 | Lake Livingston Communications Inc. | Unclassified | IPv4 | 220 |
| AS30350 | Region VII Education Service Center | Unclassified | IPv4 IPv6 | 185 |
| AS53423 | Brazos WiFi | Unclassified | IPv4 | 152 |
| AS62467 | TXNet Communications LLC | Unclassified | IPv4 IPv6 | 100 |
| AS25798 | Vexus Fiber | Unclassified | IPv4 | 63 |
| AS33128 | Apogee Telecom Inc. | Unclassified | IPv4 | 59 |
| AS395183 | ETEC | Unclassified | IPv4 | 59 |
| AS395868 | Fort Bend Independent School District | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6300 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 4,733 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,391 |
| AS19201 | Eastex Telephone Cooperative, Inc. | Unclassified | IPv4 IPv6 | 1,269 |
| AS17093 | Fidium | Unclassified | IPv4 | 295 |
| AS16716 | Lake Livingston Communications Inc. | Unclassified | IPv4 | 220 |
| AS53423 | Brazos WiFi | Unclassified | IPv4 | 208 |
| AS30350 | Region VII Education Service Center | Unclassified | IPv4 IPv6 | 185 |
| AS14907 | Wikimedia Foundation Inc. | Hosting | IPv4 IPv6 | 113 |
| AS971 | PureVoltage Hosting Inc. | Unclassified | IPv4 | 109 |
| AS62467 | TXNet Communications LLC | Unclassified | IPv4 IPv6 | 100 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-02 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.44M 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.