Observed topology
AS17961 MITENE mitene internet co., ltd.
Unclassified RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS17961: 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 |
|---|---|---|---|---|
| AS2518 | BIGLOBE Inc. | Residential | IPv4 IPv6 | 307 |
| AS2519 | ARTERIA Networks Corporation | Unclassified | IPv4 IPv6 | 201 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 156 |
| AS2497 | Internet Initiative Japan Inc. | Unclassified | IPv4 | 34 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 15 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 15 |
| AS8966 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Mobile | IPv4 | 14 |
| AS9824 | JCOM Co., Ltd. | Residential | IPv4 | 14 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 14 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 5 |
Transit
Downstream networks
Networks for which AS17961 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS17961 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS2518 | BIGLOBE Inc. | Residential | IPv4 IPv6 | 347 |
| AS2519 | ARTERIA Networks Corporation | Unclassified | IPv4 IPv6 | 222 |
| AS2497 | Internet Initiative Japan Inc. | Unclassified | IPv4 | 164 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 156 |
| AS23777 | NTT BUSINESS SOLUTIONS CORPORATION | Unclassified | IPv4 IPv6 | 109 |
| AS10004 | Phoenix Communications Inc. | Residential | IPv4 | 82 |
| AS9824 | JCOM Co., Ltd. | Residential | IPv4 IPv6 | 37 |
| AS131911 | HONJYO CABLE VISION CO., LTD. | Residential | IPv4 IPv6 | 23 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 20 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 15 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-12 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.