asn.dev

Observed topology

AS44355 COLOCATION

Hosting RIPE Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44355: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv673
AS61049Exascale LtdResidentialIPv4 IPv638
AS207841Inferno Communications LtdUnclassifiedIPv420
AS24482SG.GSHostingIPv4 IPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209735Lagrange Cloud Technologies LimitedHostingIPv4 IPv6113
AS207846Lauren Renee KellyUnclassifiedIPv4 IPv698
AS204236Daniel IonitaUnclassifiedIPv461
AS202359AS207960 CyfyngedigHostingIPv4 IPv659
AS207258Conor Liam BurnsUnclassifiedIPv657
AS211374Motion Applied LimitedUnclassifiedIPv637
AS213525Motion Applied LimitedUnclassifiedIPv637
AS214498Motion Applied LimitedUnclassifiedIPv637

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS209735Lagrange Cloud Technologies LimitedHostingIPv4 IPv6488
AS61049Exascale LtdResidentialIPv4 IPv6469
AS6939Hurricane Electric LLCTransitIPv4 IPv6362
AS207841Inferno Communications LtdUnclassifiedIPv4 IPv6337
AS202359AS207960 CyfyngedigHostingIPv4 IPv6168
AS207846Lauren Renee KellyUnclassifiedIPv4 IPv698
AS204236Daniel IonitaUnclassifiedIPv461
AS207258Conor Liam BurnsUnclassifiedIPv657
AS211374Motion Applied LimitedUnclassifiedIPv637
AS213525Motion Applied LimitedUnclassifiedIPv637

Provenance

Where this comes from

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