asn.dev

Observed topology

AS5564 SOL-AS Commercial internet service provider

Hosting RIPE Content

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS5564: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6198
AS13335Cloudflare, Inc.HostingIPv4130
AS174Cogent Communications, LLCTransitIPv461
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv67
AS9002RETN LimitedUnclassifiedIPv63
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv63
AS48185team.blue NVUnclassifiedIPv4 IPv63
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv63
AS3741Dimension DataUnclassifiedIPv42

All 17 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208564Bedroq LimitedUnclassifiedIPv448

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6246
AS13335Cloudflare, Inc.HostingIPv4130
AS174Cogent Communications, LLCTransitIPv463
AS208564Bedroq LimitedUnclassifiedIPv448
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv613
AS24482SG.GSHostingIPv4 IPv65
AS3741Dimension DataUnclassifiedIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS48185team.blue NVUnclassifiedIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64

All 19 adjacent →

Provenance

Where this comes from

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