Observed topology
AS4226 SUMOFIBER
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS4226: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 584 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 521 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 272 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 253 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 245 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 215 |
| AS29968 | Dunkirk & Fredonia Telephone Company | Unclassified | IPv4 | 130 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 99 |
| AS33727 | Sumofiber | Unclassified | IPv6 | 33 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 25 |
Transit
Downstream networks
Networks for which AS4226 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS397162 | Sumofiber | Unclassified | IPv4 IPv6 | 880 |
| AS46601 | CCI Communications LLC | Unclassified | IPv4 | 171 |
| AS400179 | PDQ.com Corporation | Unclassified | IPv4 IPv6 | 130 |
| AS32541 | CCI Networks Services | Unclassified | IPv4 | 77 |
| AS401579 | RyTel LLC | Unclassified | IPv4 | 58 |
| AS401758 | DD BURR INVESTMENT COMPANY LLC | Unclassified | IPv4 | 57 |
| AS401734 | LANtastic Internet | Unclassified | IPv4 | 30 |
| AS399936 | PBXIO LLC | Unclassified | IPv4 | 28 |
Adjacency
Adjacent networks
Every AS seen directly next to AS4226 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS397162 | Sumofiber | Unclassified | IPv4 IPv6 | 992 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 956 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 950 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 516 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 451 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 374 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 246 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 187 |
| AS46601 | CCI Communications LLC | Unclassified | IPv4 | 171 |
| AS29968 | Dunkirk & Fredonia Telephone Company | Unclassified | IPv4 | 130 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.