asn.dev

Observed topology

AS42574 NSPLUS-AS

Unclassified RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS42574: 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
AS3216PJSC "Vimpelcom"MobileIPv4 IPv61,319
AS6939Hurricane Electric LLCTransitIPv4 IPv6230
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv493
AS24482SG.GSHostingIPv4 IPv632
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv632
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv632
AS8447A1 Telekom Austria AGResidentialIPv431
AS34927iFog GmbHHostingIPv431
AS49673Truenetwork LLCUnclassifiedIPv431
AS50673Serverius Holding B.V.UnclassifiedIPv431

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47338MKU TSITiTOUnclassifiedIPv460

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS3216PJSC "Vimpelcom"MobileIPv4 IPv61,366
AS6939Hurricane Electric LLCTransitIPv4 IPv6237
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv493
AS47338MKU TSITiTOUnclassifiedIPv460
AS24482SG.GSHostingIPv4 IPv633
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv633
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv633
AS34927iFog GmbHHostingIPv432
AS49673Truenetwork LLCUnclassifiedIPv432
AS50673Serverius Holding B.V.UnclassifiedIPv432

All 12 adjacent →

Provenance

Where this comes from

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