asn.dev

Observed topology

AS21527 DAYSTARR-NET

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS21527: 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
AS26554US Signal Company, L.L.C.UnclassifiedIPv4986
AS174Cogent Communications, LLCTransitIPv4 IPv6244
AS12129123.Net, Inc.HostingIPv4 IPv6132
AS46208Peninsula Fiber Network, LLCUnclassifiedIPv4110
AS6939Hurricane Electric LLCTransitIPv670
AS20205Amplex Electric, Inc.ResidentialIPv423
AS30517Great Lakes Comnet, Inc.UnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS26216Invisalink WirelessUnclassifiedIPv4 IPv6492
AS63133Lennon Telephone CompanyUnclassifiedIPv4102
AS47018Covenant Eyes, Inc.UnclassifiedIPv478
AS11910LakeNet LLCResidentialIPv432

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS26554US Signal Company, L.L.C.UnclassifiedIPv41,140
AS26216Invisalink WirelessUnclassifiedIPv4 IPv6492
AS12129123.Net, Inc.HostingIPv4 IPv6483
AS174Cogent Communications, LLCTransitIPv4 IPv6318
AS46208Peninsula Fiber Network, LLCUnclassifiedIPv4187
AS6939Hurricane Electric LLCTransitIPv6105
AS63133Lennon Telephone CompanyUnclassifiedIPv4102
AS47018Covenant Eyes, Inc.UnclassifiedIPv478
AS20205Amplex Electric, Inc.ResidentialIPv434
AS11910LakeNet LLCResidentialIPv432

All 11 adjacent →

Provenance

Where this comes from

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