asn.dev

Observed topology

AS48610 OFORO

Unclassified RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS48610: 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
AS50509Transroute Telecom LTDUnclassifiedIPv4 IPv658
AS31500Global Network Management IncUnclassifiedIPv4 IPv614
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv68
AS28917Fiord Networks, UABUnclassifiedIPv4 IPv67
AS20764CJSC RASCOMUnclassifiedIPv4 IPv66
AS202984Chernyshov Aleksandr AleksandrovichUnclassifiedIPv43
AS24482SG.GSHostingIPv4 IPv62
AS9002RETN LimitedUnclassifiedIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41
AS49673Truenetwork LLCUnclassifiedIPv41

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210281EcoConnect LLCUnclassifiedIPv4179
AS57712NPF SOFTVIDEO Ltd.ResidentialIPv4 IPv6102

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS50509Transroute Telecom LTDUnclassifiedIPv4 IPv6268
AS210281EcoConnect LLCUnclassifiedIPv4235
AS57712NPF SOFTVIDEO Ltd.ResidentialIPv4 IPv6107
AS31500Global Network Management IncUnclassifiedIPv4 IPv672
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv628
AS28917Fiord Networks, UABUnclassifiedIPv4 IPv626
AS20764CJSC RASCOMUnclassifiedIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv68
AS9002RETN LimitedUnclassifiedIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46

All 13 adjacent →

Provenance

Where this comes from

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