Observed topology
AS6894 KDDI-EUROPE KDDI Europe Ltd.
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS6894: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 68 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 40 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 32 |
| AS2497 | Internet Initiative Japan Inc. | Unclassified | IPv4 | 27 |
| AS2516 | KDDI CORPORATION | Mobile | IPv4 IPv6 | 10 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 4 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 4 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 4 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 4 |
| AS1257 | Tele2 Sverige AB | Mobile | IPv4 | 3 |
Transit
Downstream networks
Networks for which AS6894 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39116 | Telehouse International Corporation of Europe Ltd | Unclassified | IPv4 | 487 |
| AS329458 | FieldBase Services Limited | Unclassified | IPv4 | 59 |
| AS49978 | NIUM SYSTEMS UK LIMITED | Unclassified | IPv4 | 58 |
| AS204648 | Calligo Limited | Unclassified | IPv4 | 58 |
| AS43534 | Network Merchants Limited | Unclassified | IPv4 | 11 |
| AS12654 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6894 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39116 | Telehouse International Corporation of Europe Ltd | Unclassified | IPv4 | 487 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 321 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 175 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 140 |
| AS2497 | Internet Initiative Japan Inc. | Unclassified | IPv4 | 84 |
| AS329458 | FieldBase Services Limited | Unclassified | IPv4 | 59 |
| AS49978 | NIUM SYSTEMS UK LIMITED | Unclassified | IPv4 | 58 |
| AS204648 | Calligo Limited | Unclassified | IPv4 | 58 |
| AS2516 | KDDI CORPORATION | Mobile | IPv4 IPv6 | 44 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 16 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 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.