Observed topology
AS59645 WYBT-NET Making it ping and putting the Mau into meowmeow.
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS59645: 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 |
|---|---|---|---|---|
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 390 |
| AS34927 | iFog GmbH | Hosting | IPv4 IPv6 | 209 |
| AS24961 | WIIT AG | Hosting | IPv4 IPv6 | 147 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 135 |
| AS29670 | Individual Network Berlin ("IN-Berlin") e.V. | Unclassified | IPv4 IPv6 | 74 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 14 |
| AS56662 | Marcin Gondek | Unclassified | IPv6 | 11 |
| AS58057 | Securebit AG | Unclassified | IPv6 | 11 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 8 |
| AS34800 | Securebit AG | Unclassified | IPv4 | 3 |
Transit
Downstream networks
Networks for which AS59645 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS211286 | Tobias Fiebig | Unclassified | IPv4 IPv6 | 228 |
| AS216441 | Jakob Riepler | Unclassified | IPv6 | 111 |
| AS208135 | Carl Fabian Luepke | Unclassified | IPv4 IPv6 | 98 |
| AS215250 | Tobias Fiebig | Unclassified | IPv4 IPv6 | 85 |
| AS206506 | Markus Witt | Unclassified | IPv6 | 75 |
| AS201567 | Vivian Band | Unclassified | IPv6 | 39 |
| AS198686 | Technische Universitaet Wien | Unclassified | IPv6 | 38 |
| AS216355 | Jurgen Kloosterman | Unclassified | IPv6 | 38 |
| AS212488 | Ralph Koning | Unclassified | IPv6 | 9 |
| AS214844 | Chemnitzer StudentenNetz KdoeR | Unclassified | IPv6 | 3 |
Adjacency
Adjacent networks
Every AS seen directly next to AS59645 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 551 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 413 |
| AS34927 | iFog GmbH | Hosting | IPv4 IPv6 | 270 |
| AS24961 | WIIT AG | Hosting | IPv4 IPv6 | 255 |
| AS211286 | Tobias Fiebig | Unclassified | IPv4 IPv6 | 228 |
| AS29670 | Individual Network Berlin ("IN-Berlin") e.V. | Unclassified | IPv4 IPv6 | 134 |
| AS216441 | Jakob Riepler | Unclassified | IPv6 | 111 |
| AS208135 | Carl Fabian Luepke | Unclassified | IPv4 IPv6 | 98 |
| AS215250 | Tobias Fiebig | Unclassified | IPv4 IPv6 | 85 |
| AS206506 | Markus Witt | Unclassified | IPv6 | 75 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M 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.