asn.dev

Observed topology

AS58269 AS-CLOUDHOSTING CloudHosting SIA

Unclassified RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58269: 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 LimitedUnclassifiedIPv4117
AS12578SIA TetResidentialIPv4115
AS20910SIA "BITE Latvija"ResidentialIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202280NBI SIAUnclassifiedIPv4564
AS204391NBI SIAUnclassifiedIPv4420
AS208996NBI SIAUnclassifiedIPv4240
AS210668SIA SpotrixUnclassifiedIPv4120
AS205045NBI SIAUnclassifiedIPv460
AS210556NBI SIAUnclassifiedIPv460
AS210830NBI SIAUnclassifiedIPv460

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS12578SIA TetResidentialIPv41,021
AS9002RETN LimitedUnclassifiedIPv4910
AS202280NBI SIAUnclassifiedIPv4564
AS204391NBI SIAUnclassifiedIPv4420
AS208996NBI SIAUnclassifiedIPv4240
AS210668SIA SpotrixUnclassifiedIPv4120
AS24651JSC BALTICOMUnclassifiedIPv498
AS61127SIA "RD Consult"UnclassifiedIPv462
AS205045NBI SIAUnclassifiedIPv460
AS210556NBI SIAUnclassifiedIPv460

All 12 adjacent →

Provenance

Where this comes from

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