asn.dev

Observed topology

AS44733 THAT_ESCALATED_QUICKLY_BV

Unclassified RIPE

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS44733: 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
AS50917Diederik Focko de ZeeUnclassifiedIPv447
AS35133Eranium B.V.HostingIPv4 IPv636
AS29632Netassist International EOODUnclassifiedIPv62
AS50304Blix Solutions ASUnclassifiedIPv62
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv61
AS17639Converge ICT Solutions Inc.UnclassifiedIPv61
AS24482SG.GSHostingIPv61
AS25091IP-Max SAUnclassifiedIPv61
AS33891Core-Backbone GmbHHostingIPv61
AS48185team.blue NVUnclassifiedIPv61

All 12 upstreams →

Transit

Downstream networks

inferred

Networks for which AS44733 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 12

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

ASNetworkTypeFamiliesPaths seen
AS50917Diederik Focko de ZeeUnclassifiedIPv447
AS35133Eranium B.V.HostingIPv4 IPv636
AS29632Netassist International EOODUnclassifiedIPv62
AS50304Blix Solutions ASUnclassifiedIPv62
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv61
AS17639Converge ICT Solutions Inc.UnclassifiedIPv61
AS24482SG.GSHostingIPv61
AS25091IP-Max SAUnclassifiedIPv61
AS33891Core-Backbone GmbHHostingIPv61
AS48185team.blue NVUnclassifiedIPv61

All 12 adjacent →

Provenance

Where this comes from

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