asn.dev

Observed topology

AS62023 NYNEX NYNEX satellite OHG primary AS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS62023: 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
AS33891Core-Backbone GmbHHostingIPv4 IPv6943
AS34309Link11 GmbHUnclassifiedIPv4 IPv6303
AS6939Hurricane Electric LLCTransitIPv4 IPv6218
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv692
AS24482SG.GSHostingIPv4 IPv631
AS34019Hivane AssociationUnclassifiedIPv4 IPv631
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv631
AS212024Marc SchmittUnclassifiedIPv4 IPv631
AS6797GlobalConnect ABUnclassifiedIPv430
AS12779IT.Gate S.p.A.UnclassifiedIPv430

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200519NYNEX satellite OHGUnclassifiedIPv4 IPv6490

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS33891Core-Backbone GmbHHostingIPv4 IPv61,184
AS200519NYNEX satellite OHGUnclassifiedIPv4 IPv6490
AS34309Link11 GmbHUnclassifiedIPv4 IPv6361
AS6939Hurricane Electric LLCTransitIPv4 IPv6297
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6118
AS24482SG.GSHostingIPv4 IPv641
AS34019Hivane AssociationUnclassifiedIPv4 IPv641
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv641
AS212024Marc SchmittUnclassifiedIPv4 IPv641
AS6797GlobalConnect ABUnclassifiedIPv436

All 16 adjacent →

Provenance

Where this comes from

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