asn.dev

Observed topology

AS208059 GRMML

Unclassified RIPE Educational/Research

Upstreams 22 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 14
Adjacent (IPv6) 17
Upstream graph Who carries AS208059, and who carries them, drawn as a map up to the transit-free core. 5 exchanges Where AS208059 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS208059: 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.

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv4 IPv6183
AS56381level66.network UG (haftungsbeschraenkt)UnclassifiedIPv4 IPv619
AS41051Openfactory GmbHUnclassifiedIPv4 IPv614
AS53667FranTech SolutionsHostingIPv614
AS20473The Constant Company, LLCHostingIPv612
AS58057Securebit AGUnclassifiedIPv612
AS35661VIRTUA SYSTEMS SASUnclassifiedIPv610
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv67
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv67

All 22 upstreams →

Transit

Downstream networks

inferred

Networks for which AS208059 was observed as the last hop before the origin, meaning it appears to provide them transit.

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 22

Every AS seen directly next to AS208059 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv4 IPv6183
AS56381level66.network UG (haftungsbeschraenkt)UnclassifiedIPv4 IPv619
AS41051Openfactory GmbHUnclassifiedIPv4 IPv614
AS53667FranTech SolutionsHostingIPv614
AS20473The Constant Company, LLCHostingIPv612
AS58057Securebit AGUnclassifiedIPv612
AS35661VIRTUA SYSTEMS SASUnclassifiedIPv610
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv67
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv67

All 22 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.