Observed topology
AS215296 LOWPING-NL Raoul Brouns is trading as LowPing NL
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS215296: 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 |
|---|---|---|---|---|
| AS401066 | LowPing | Unclassified | IPv4 IPv6 | 113 |
| AS213753 | InterEdge B.V. | Unclassified | IPv4 IPv6 | 105 |
| AS50917 | Diederik Focko de Zee | Unclassified | IPv4 IPv6 | 47 |
| AS64289 | Macarne.com | Unclassified | IPv4 IPv6 | 37 |
| AS37989 | DCS1 Pte. Ltd. | Hosting | IPv4 IPv6 | 13 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 9 |
| AS58057 | Securebit AG | Unclassified | IPv4 IPv6 | 9 |
| AS204092 | Association GRIFON | Unclassified | IPv4 IPv6 | 9 |
| AS213241 | TECHIT.BE SRL | Residential | IPv4 IPv6 | 9 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 9 |
Transit
Downstream networks
Networks for which AS215296 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20598 | IDDQD-AS | Hosting | IPv4 | 195 |
| AS403001 | Mirage | Unclassified | IPv4 IPv6 | 76 |
| AS211635 | Stefan Nagel | Unclassified | IPv4 IPv6 | 74 |
| AS218569 | Viktor Nesmeianov | Unclassified | IPv4 IPv6 | 61 |
| AS219092 | Marcel van den Bosch trading as 12spark Software | Unclassified | IPv4 IPv6 | 50 |
| AS210578 | Niels Groenewegen trading as NeNet | Unclassified | IPv4 IPv6 | 48 |
| AS210825 | Sebastian Pfeifer | Unclassified | IPv4 IPv6 | 43 |
| AS197191 | Virtical Operations B.V. | Unclassified | IPv4 IPv6 | 42 |
| AS202119 | Malthe Kragh Tankred | Unclassified | IPv6 | 32 |
| AS275732 | Newvox Telecomunicacoes LTDA | Unclassified | IPv6 | 27 |
Adjacency
Adjacent networks
Every AS seen directly next to AS215296 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS213753 | InterEdge B.V. | Unclassified | IPv4 IPv6 | 415 |
| AS20598 | IDDQD-AS | Hosting | IPv4 | 195 |
| AS50917 | Diederik Focko de Zee | Unclassified | IPv4 IPv6 | 173 |
| AS64289 | Macarne.com | Unclassified | IPv4 IPv6 | 143 |
| AS401066 | LowPing | Unclassified | IPv4 IPv6 | 113 |
| AS213241 | TECHIT.BE SRL | Residential | IPv4 IPv6 | 79 |
| AS218569 | Viktor Nesmeianov | Unclassified | IPv4 IPv6 | 78 |
| AS403001 | Mirage | Unclassified | IPv4 IPv6 | 76 |
| AS211635 | Stefan Nagel | Unclassified | IPv4 IPv6 | 74 |
| AS219092 | Marcel van den Bosch trading as 12spark Software | Unclassified | IPv4 IPv6 | 50 |
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.