asn.dev

Observed topology

AS49627 SPEAKUP Speakup BV

Unclassified RIPE

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS49627: 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
AS57866Fusix Networks B.V.UnclassifiedIPv4 IPv684
AS8455atom86 BVHostingIPv4 IPv635
AS6939Hurricane Electric LLCTransitIPv424
AS24785Broadband Hosting B.V.HostingIPv613
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv64
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS48185team.blue NVUnclassifiedIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64

Transit

Downstream networks

inferred

Networks for which AS49627 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 21

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

ASNetworkTypeFamiliesPaths seen
AS57866Fusix Networks B.V.UnclassifiedIPv4 IPv684
AS8455atom86 BVHostingIPv4 IPv635
AS6939Hurricane Electric LLCTransitIPv424
AS24785Broadband Hosting B.V.HostingIPv613
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv64
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS48185team.blue NVUnclassifiedIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64

Provenance

Where this comes from

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