asn.dev

Observed topology

AS49775 LunarDigital Lunar Digital Solutions Limited

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49775: 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
AS9002RETN LimitedUnclassifiedIPv4 IPv6151
AS174Cogent Communications, LLCTransitIPv4 IPv6125
AS6461Zayo BandwidthTransitIPv484
AS6939Hurricane Electric LLCTransitIPv4 IPv681
AS61049Exascale LtdResidentialIPv448
AS24482SG.GSHostingIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215262Cloud Nord LimitedUnclassifiedIPv4 IPv6121
AS206232Acuity Unified Communications LimitedUnclassifiedIPv4102
AS209594IGC Technical Solutions LtdUnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4 IPv6257
AS174Cogent Communications, LLCTransitIPv4 IPv6224
AS215262Cloud Nord LimitedUnclassifiedIPv4 IPv6121
AS61049Exascale LtdResidentialIPv4104
AS206232Acuity Unified Communications LimitedUnclassifiedIPv4102
AS6939Hurricane Electric LLCTransitIPv4 IPv697
AS6461Zayo BandwidthTransitIPv484
AS209594IGC Technical Solutions LtdUnclassifiedIPv458
AS24482SG.GSHostingIPv412

Provenance

Where this comes from

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