Observed topology
AS61430 AS-MILDE Marc Milde
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS61430: 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 |
|---|---|---|---|---|
| AS34154 | Configo Systems Gesellschaft fuer Systemloesungen mbH | Residential | IPv4 IPv6 | 522 |
| AS12586 | GHOSTnet GmbH | Hosting | IPv6 | 130 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 72 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 15 |
| AS57821 | Nonattached Network e.V. | Unclassified | IPv4 IPv6 | 15 |
| AS202365 | Omer GOLGELI | Unclassified | IPv4 | 9 |
| AS212508 | Lowhosting services of Davide Gennari | Unclassified | IPv4 | 9 |
| AS25091 | IP-Max SA | Unclassified | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS61430 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 AS61430 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS34154 | Configo Systems Gesellschaft fuer Systemloesungen mbH | Residential | IPv4 IPv6 | 619 |
| AS12586 | GHOSTnet GmbH | Hosting | IPv6 | 130 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 81 |
| AS204883 | Oliver Koehl | Unclassified | IPv4 | 61 |
| AS203123 | Jurgen Eckhard Petri | Unclassified | IPv4 | 49 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 16 |
| AS57821 | Nonattached Network e.V. | Unclassified | IPv4 IPv6 | 16 |
| AS202365 | Omer GOLGELI | Unclassified | IPv4 | 10 |
| AS212508 | Lowhosting services of Davide Gennari | Unclassified | IPv4 | 10 |
| AS25091 | IP-Max SA | Unclassified | IPv6 | 2 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.