asn.dev

Observed topology

AS42567 MOJHOST-EU

Hosting RIPE Content

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

Transit

Upstream networks

All 27

Networks observed carrying traffic for AS42567: 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 IPv6157
AS396998Path Network, Inc.UnclassifiedIPv460
AS174Cogent Communications, LLCTransitIPv4 IPv655
AS3257GTT Communications Inc.TransitIPv4 IPv633
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS13477Neutral NetworksUnclassifiedIPv432

Adjacency

Adjacent networks

All 28

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6171
AS174Cogent Communications, LLCTransitIPv4 IPv664
AS396998Path Network, Inc.UnclassifiedIPv460
AS3257GTT Communications Inc.TransitIPv4 IPv639
AS13477Neutral NetworksUnclassifiedIPv432
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv68
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65

Provenance

Where this comes from

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