Observed topology
AS39642 Sinal-AS Sinal A/S
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS39642: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 782 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 495 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 425 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 132 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 50 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 50 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 50 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 50 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 50 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 50 |
Transit
Downstream networks
Networks for which AS39642 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS210149 | Esbjerg Kommune | Unclassified | IPv4 | 649 |
| AS49974 | Bo data ApS | Unclassified | IPv4 IPv6 | 292 |
| AS8273 | Norlys Telco A/S | Residential | IPv4 | 236 |
| AS57030 | Itm8 A/S | Unclassified | IPv4 | 184 |
| AS50490 | Sinal A/S | Unclassified | IPv4 IPv6 | 153 |
| AS42355 | Sinal A/S | Unclassified | IPv4 | 118 |
| AS62090 | Randers Kommune | Unclassified | IPv4 | 118 |
| AS207934 | WNB A/S | Unclassified | IPv4 | 100 |
| AS213320 | Norlys Telco A/S | Unclassified | IPv4 IPv6 | 96 |
| AS213032 | Fleggaard Holding A/S | Unclassified | IPv6 | 89 |
Adjacency
Adjacent networks
Every AS seen directly next to AS39642 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,421 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 810 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 799 |
| AS210149 | Esbjerg Kommune | Unclassified | IPv4 | 649 |
| AS49974 | Bo data ApS | Unclassified | IPv4 IPv6 | 361 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 280 |
| AS8273 | Norlys Telco A/S | Residential | IPv4 | 236 |
| AS213320 | Norlys Telco A/S | Unclassified | IPv4 IPv6 | 188 |
| AS57030 | Itm8 A/S | Unclassified | IPv4 | 184 |
| AS50490 | Sinal A/S | Unclassified | IPv4 IPv6 | 153 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M 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.