Observed topology
AS6696 VERIXI
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS6696: 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 | 1,203 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 509 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 379 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 | 102 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 54 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 52 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 51 |
| AS45049 | Mohamed El Bouddunti | Residential | IPv4 IPv6 | 51 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 49 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 49 |
Transit
Downstream networks
Networks for which AS6696 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 4,584 |
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 | 3,218 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 2,168 |
| AS714 | Apple Inc. | Hosting | IPv4 IPv6 | 1,696 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,649 |
| AS8075 | Microsoft Corporation | Hosting | IPv4 IPv6 | 1,311 |
| AS15169 | Google LLC | Hosting | IPv4 | 934 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 732 |
| AS7713 | PT Telekomunikasi Indonesia | Residential | IPv4 | 708 |
| AS3786 | LG DACOM Corporation | Unclassified | IPv4 | 685 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6696 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS45049 | Mohamed El Bouddunti | Residential | IPv4 IPv6 | 1,208,410 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 373,568 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 373,433 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 130,872 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 88,955 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 | 57,045 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 16,458 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 | 10,764 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 10,189 |
| AS64049 | Reliance Jio Infocomm Pte Ltd Singapore | Unclassified | IPv4 | 9,747 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-15 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.09M 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.