asn.dev

Observed topology

AS30456 COSMIC

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS30456: 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
AS13335Cloudflare, Inc.HostingIPv41,081
AS2914NTT America, Inc.TransitIPv4 IPv6213
AS3257GTT Communications Inc.TransitIPv4183
AS1299Arelion Sweden ABTransitIPv4101

Transit

Downstream networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS400758CORTAVISUnclassifiedIPv4300
AS26863GameserverkingsHostingIPv4216
AS50131Spartan Host LtdUnclassifiedIPv4198
AS400810BreezeHostUnclassifiedIPv4161
AS1015Server Starter Host LLCUnclassifiedIPv4 IPv692
AS60841berrybyte LimitedUnclassifiedIPv460
AS211339Vortia LtdUnclassifiedIPv460
AS33211RisingNet, LLCHostingIPv454
AS54365Digital Innovations by RyanUnclassifiedIPv4 IPv647
AS1002Bytefilter LLCUnclassifiedIPv436

All 14 downstreams →

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv41,081
AS2914NTT America, Inc.TransitIPv4 IPv6891
AS3257GTT Communications Inc.TransitIPv4525
AS1299Arelion Sweden ABTransitIPv4489
AS400758CORTAVISUnclassifiedIPv4300
AS26863GameserverkingsHostingIPv4216
AS50131Spartan Host LtdUnclassifiedIPv4198
AS400810BreezeHostUnclassifiedIPv4161
AS60841berrybyte LimitedUnclassifiedIPv4120
AS1015Server Starter Host LLCUnclassifiedIPv4 IPv692

All 19 adjacent →

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.