Observed topology
AS10794 BANKAMERICA
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS10794: 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 |
|---|---|---|---|---|
| AS32787 | Akamai Technologies, Inc. | Hosting | IPv4 | 6,720 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 3,370 |
| AS701 | Verizon Business | Residential | IPv4 | 815 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 679 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 592 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 527 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 524 |
| AS3758 | SingNet | Residential | IPv4 | 487 |
| AS4657 | StarHub Ltd | Residential | IPv4 | 356 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 350 |
Transit
Downstream networks
Networks for which AS10794 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS10998 | Bank of America, National Association | Unclassified | IPv4 | 120 |
Adjacency
Adjacent networks
Every AS seen directly next to AS10794 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS32787 | Akamai Technologies, Inc. | Hosting | IPv4 | 6,840 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 3,370 |
| AS701 | Verizon Business | Residential | IPv4 | 815 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 679 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 592 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 527 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 524 |
| AS3758 | SingNet | Residential | IPv4 | 487 |
| AS4657 | StarHub Ltd | Residential | IPv4 | 356 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 350 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-18 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.