asn.dev

Observed topology

AS49033 CRITICALCORE

Unclassified RIPE

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

Transit

Upstream networks

All 25

Networks observed carrying traffic for AS49033: 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
AS35133Eranium B.V.HostingIPv4 IPv6201
AS24785Broadband Hosting B.V.HostingIPv4 IPv6161
AS20562Broadband Hosting B.V.HostingIPv4 IPv6139
AS6939Hurricane Electric LLCTransitIPv4131
AS6830Liberty Global Europe Holding B.V.ResidentialIPv4 IPv691
AS50304Blix Solutions ASUnclassifiedIPv4 IPv634
AS24482SG.GSHostingIPv4 IPv617
AS48185team.blue NVUnclassifiedIPv4 IPv617
AS6696VERIXI SAUnclassifiedIPv415
AS34927iFog GmbHHostingIPv415

All 25 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS62125Proact Netherlands B.V.UnclassifiedIPv4118

Adjacency

Adjacent networks

All 26

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

ASNetworkTypeFamiliesPaths seen
AS35133Eranium B.V.HostingIPv4 IPv6223
AS24785Broadband Hosting B.V.HostingIPv4 IPv6169
AS20562Broadband Hosting B.V.HostingIPv4 IPv6157
AS6939Hurricane Electric LLCTransitIPv4145
AS6830Liberty Global Europe Holding B.V.ResidentialIPv4 IPv6119
AS62125Proact Netherlands B.V.UnclassifiedIPv4118
AS50304Blix Solutions ASUnclassifiedIPv4 IPv638
AS24482SG.GSHostingIPv4 IPv619
AS6696VERIXI SAUnclassifiedIPv417
AS34927iFog GmbHHostingIPv417

All 26 adjacent →

Provenance

Where this comes from

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