asn.dev

Observed topology

AS57976 BLIZZARD

Hosting RIPE

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

Transit

Upstream networks

All 85

Networks observed carrying traffic for AS57976: 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 IPv61,491
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,389
AS6939Hurricane Electric LLCTransitIPv4 IPv61,303
AS3786LG DACOM CorporationUnclassifiedIPv41,045
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6509
AS4637Telstra GlobalUnclassifiedIPv4 IPv6450
AS17408AboveNet Communications TaiwanUnclassifiedIPv4447
AS9002RETN LimitedUnclassifiedIPv4 IPv6428
AS7018AT&T Enterprises, LLCResidentialIPv4 IPv6221
AS24482SG.GSHostingIPv4 IPv6160

All 85 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS40551Activision Publishing, Inc.UnclassifiedIPv4295

Adjacency

Adjacent networks

All 86

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv61,563
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,431
AS6939Hurricane Electric LLCTransitIPv4 IPv61,343
AS3786LG DACOM CorporationUnclassifiedIPv41,045
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6532
AS4637Telstra GlobalUnclassifiedIPv4 IPv6496
AS17408AboveNet Communications TaiwanUnclassifiedIPv4447
AS9002RETN LimitedUnclassifiedIPv4 IPv6446
AS40551Activision Publishing, Inc.UnclassifiedIPv4295
AS7018AT&T Enterprises, LLCResidentialIPv4 IPv6227

All 86 adjacent →

Provenance

Where this comes from

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