asn.dev

Observed topology

AS57811 REDGETECHNOLOGIES

Hosting RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS57811: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6380
AS6939Hurricane Electric LLCTransitIPv4 IPv6136
AS3356Level 3 Parent, LLCTransitIPv4 IPv6111
AS39603P4 Sp. z o.o.ResidentialIPv458
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv650
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv637
AS24482SG.GSHostingIPv4 IPv613
AS33891Core-Backbone GmbHHostingIPv46
AS34927iFog GmbHHostingIPv43
AS24748Atman Sp. z o.o.HostingIPv62

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS201029Redge Technologies sp. z o.o.UnclassifiedIPv4 IPv6312

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6644
AS201029Redge Technologies sp. z o.o.UnclassifiedIPv4 IPv6546
AS6939Hurricane Electric LLCTransitIPv4 IPv6232
AS3356Level 3 Parent, LLCTransitIPv4 IPv6223
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv6100
AS8308PANSTWOWY INSTYTUT BADAWCZYUnclassifiedIPv472
AS39603P4 Sp. z o.o.ResidentialIPv458
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv653
AS262287Latitude.sh LTDAHostingIPv634
AS24482SG.GSHostingIPv4 IPv623

All 17 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-19 10: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.