asn.dev

Observed topology

AS57433 INTERCOLO-AS intercolo IP-Backbone

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS57433: 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
AS9002RETN LimitedUnclassifiedIPv4 IPv6794
AS12586GHOSTnet GmbHHostingIPv4 IPv6218
AS6939Hurricane Electric LLCTransitIPv4 IPv658
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv623
AS24482SG.GSHostingIPv4 IPv618
AS202365Omer GOLGELIUnclassifiedIPv413
AS25091IP-Max SAUnclassifiedIPv65
AS212508Lowhosting services of Davide GennariUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60461intercolo GmbHUnclassifiedIPv4 IPv694
AS47637INFERNA LIMITEDUnclassifiedIPv635
AS59592intercolo GmbHUnclassifiedIPv635
AS62454intercolo GmbHUnclassifiedIPv635

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4 IPv6885
AS12586GHOSTnet GmbHHostingIPv4 IPv6219
AS6939Hurricane Electric LLCTransitIPv4 IPv6156
AS60461intercolo GmbHUnclassifiedIPv4 IPv694
AS47637INFERNA LIMITEDUnclassifiedIPv635
AS59592intercolo GmbHUnclassifiedIPv635
AS62454intercolo GmbHUnclassifiedIPv635
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv626
AS24482SG.GSHostingIPv4 IPv621
AS202365Omer GOLGELIUnclassifiedIPv413

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.