asn.dev

Observed topology

AS42812 DT-IT

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42812: 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
AS8455atom86 BVHostingIPv4 IPv693
AS39637ADES BVUnclassifiedIPv490
AS6939Hurricane Electric LLCTransitIPv421
AS24482SG.GSHostingIPv43
AS31500Global Network Management IncUnclassifiedIPv43
AS34019Hivane AssociationUnclassifiedIPv43
AS58057Securebit AGUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204754SysActive B.V.UnclassifiedIPv4 IPv6277
AS60820WiFi4all B.V.UnclassifiedIPv4122
AS207627C-24 B.V.UnclassifiedIPv415

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS39637ADES BVUnclassifiedIPv4282
AS204754SysActive B.V.UnclassifiedIPv4 IPv6277
AS8455atom86 BVHostingIPv4 IPv6245
AS60820WiFi4all B.V.UnclassifiedIPv4122
AS6939Hurricane Electric LLCTransitIPv463
AS207627C-24 B.V.UnclassifiedIPv415
AS24482SG.GSHostingIPv49
AS31500Global Network Management IncUnclassifiedIPv49
AS34019Hivane AssociationUnclassifiedIPv49
AS58057Securebit AGUnclassifiedIPv49

All 11 adjacent →

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.