Observed topology
AS208566 GIVEME-WAW
Hosting RIPE Content
Transit
Upstream networks
Networks observed carrying traffic for AS208566: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 52 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 52 |
| AS35320 | Eurotranstelecom Ltd | Unclassified | IPv4 IPv6 | 31 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 11 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 3 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 2 |
| AS201054 | Stowarzyszenie e-Poludnie | Unclassified | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS208566 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS59711 | HZ Hosting Ltd | Unclassified | IPv6 | 12 |
Adjacency
Adjacent networks
Every AS seen directly next to AS208566 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 106 |
| AS59711 | HZ Hosting Ltd | Unclassified | IPv6 | 70 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 52 |
| AS35320 | Eurotranstelecom Ltd | Unclassified | IPv4 IPv6 | 47 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 11 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 3 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 2 |
| AS201054 | Stowarzyszenie e-Poludnie | Unclassified | IPv6 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.