Observed topology
AS61138 ZAPPIE-HOST-AS Zappie Host
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS61138: 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 |
|---|---|---|---|---|
| AS37153 | Xneelo (Pty) Ltd | Hosting | IPv4 IPv6 | 3,709 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 327 |
| AS55850 | Mercury NZ Limited | Residential | IPv4 IPv6 | 314 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 135 |
| AS835 | GoCodeIT Inc | Unclassified | IPv4 | 116 |
| AS270013 | J AND J SPA (INFOFRACTAL) | Unclassified | IPv4 IPv6 | 94 |
| AS924 | Cloudie Networks LLC | Hosting | IPv4 | 65 |
| AS64073 | Vetta Group | Unclassified | IPv4 IPv6 | 14 |
Transit
Downstream networks
Networks for which AS61138 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS209043 | IPRoyal Services FZE LLC | Unclassified | IPv4 | 531 |
| AS54681 | Aubrey Rose | Residential | IPv4 IPv6 | 243 |
| AS211439 | Jurgita Jurgaitiene trading as LOCOTORPI | Unclassified | IPv4 | 236 |
| AS44570 | Xodo Technology, LLC. | Unclassified | IPv4 IPv6 | 210 |
| AS9559 | Plain Communications Ltd | Unclassified | IPv4 IPv6 | 185 |
| AS39521 | TNGNET B.V. | Unclassified | IPv4 IPv6 | 95 |
| AS152586 | Kuroit | Unclassified | IPv4 IPv6 | 94 |
| AS139321 | Dennis Przytarski | Unclassified | IPv4 IPv6 | 93 |
| AS212532 | XIAO YANG WEN RUI | Unclassified | IPv4 IPv6 | 87 |
| AS206540 | BEANSUMMERHOST NEXTGEN SHED HOSTING SOLUTIONS LLC | Unclassified | IPv6 | 80 |
Adjacency
Adjacent networks
Every AS seen directly next to AS61138 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS37153 | Xneelo (Pty) Ltd | Hosting | IPv4 IPv6 | 4,476 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,713 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,234 |
| AS55850 | Mercury NZ Limited | Residential | IPv4 IPv6 | 1,132 |
| AS39521 | TNGNET B.V. | Unclassified | IPv4 IPv6 | 685 |
| AS209043 | IPRoyal Services FZE LLC | Unclassified | IPv4 | 531 |
| AS204208 | Peravix Group LTD | Unclassified | IPv4 IPv6 | 337 |
| AS54681 | Aubrey Rose | Residential | IPv4 IPv6 | 243 |
| AS211439 | Jurgita Jurgaitiene trading as LOCOTORPI | Unclassified | IPv4 | 236 |
| AS44570 | Xodo Technology, LLC. | Unclassified | IPv4 IPv6 | 210 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-24 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.94M 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.