Observed topology
AS39637 NETLOGICS-AS
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS39637: 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 |
|---|---|---|---|---|
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 499 |
| AS8455 | atom86 BV | Hosting | IPv4 IPv6 | 155 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 113 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 17 |
| AS37721 | Virtual-Technologies-Solutions-SA | Residential | IPv4 IPv6 | 17 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 14 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 | 14 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 14 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 14 |
| AS37100 | SEACOM-AS | Unclassified | IPv4 | 14 |
Transit
Downstream networks
Networks for which AS39637 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12595 | Onworx BV | Unclassified | IPv4 IPv6 | 400 |
| AS202482 | Iteeco Cooperatie U.A. | Unclassified | IPv4 | 244 |
| AS206188 | Zeta Datacenters B.V. | Unclassified | IPv4 IPv6 | 226 |
| AS43190 | Totaalnet Internet Works B.V. | Hosting | IPv4 IPv6 | 150 |
| AS207777 | Bluefiber Holding B.V. | Unclassified | IPv4 IPv6 | 128 |
| AS203037 | Mica IT B.V. | Unclassified | IPv4 | 122 |
| AS41887 | Prolocation B.V. | Hosting | IPv4 IPv6 | 103 |
| AS34108 | Stichting Breedband Delft | Unclassified | IPv4 IPv6 | 102 |
| AS42812 | Internet B.V | Unclassified | IPv4 | 90 |
| AS31584 | Akzo Nobel Nederland B.V. | Unclassified | IPv4 | 61 |
Adjacency
Adjacent networks
Every AS seen directly next to AS39637 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 1,857 |
| AS8455 | atom86 BV | Hosting | IPv4 IPv6 | 469 |
| AS12595 | Onworx BV | Unclassified | IPv4 IPv6 | 400 |
| AS42812 | Internet B.V | Unclassified | IPv4 | 282 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 267 |
| AS202482 | Iteeco Cooperatie U.A. | Unclassified | IPv4 | 244 |
| AS206188 | Zeta Datacenters B.V. | Unclassified | IPv4 IPv6 | 226 |
| AS43190 | Totaalnet Internet Works B.V. | Hosting | IPv4 IPv6 | 150 |
| AS207777 | Bluefiber Holding B.V. | Unclassified | IPv4 IPv6 | 128 |
| AS203037 | Mica IT B.V. | Unclassified | IPv4 | 122 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.