asn.dev

Observed topology

AS57356 HIGHNET-AS Highland Network Ltd

Residential RIPE

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS57356: 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
AS174Cogent Communications, LLCTransitIPv4985
AS6939Hurricane Electric LLCTransitIPv4313
AS34549meerfarbig GmbH & Co. KGHostingIPv475
AS33891Core-Backbone GmbHHostingIPv450
AS50304Blix Solutions ASUnclassifiedIPv450
AS3303Swisscom (Schweiz) AGResidentialIPv441
AS24482SG.GSHostingIPv428
AS3216PJSC "Vimpelcom"MobileIPv425
AS4657StarHub LtdResidentialIPv425
AS6797GlobalConnect ABUnclassifiedIPv425

All 19 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57477Monsternet Highland LtdUnclassifiedIPv457
AS210314Marlink ASUnclassifiedIPv435

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv41,077
AS6939Hurricane Electric LLCTransitIPv4313
AS34549meerfarbig GmbH & Co. KGHostingIPv475
AS57477Monsternet Highland LtdUnclassifiedIPv457
AS33891Core-Backbone GmbHHostingIPv450
AS50304Blix Solutions ASUnclassifiedIPv450
AS3303Swisscom (Schweiz) AGResidentialIPv441
AS210314Marlink ASUnclassifiedIPv435
AS24482SG.GSHostingIPv428
AS3216PJSC "Vimpelcom"MobileIPv425

All 21 adjacent →

Provenance

Where this comes from

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