asn.dev

Observed topology

AS21886 RICOH USA IT SERVICES

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS21886: 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
AS3356Level 3 Parent, LLCTransitIPv4382
AS2914NTT America, Inc.TransitIPv4230
AS174Cogent Communications, LLCTransitIPv4135
AS19151BroadbandONE, LLCHostingIPv496
AS54004Cablevision Lightpath LLCUnclassifiedIPv478
AS6939Hurricane Electric LLCTransitIPv472
AS3257GTT Communications Inc.TransitIPv48
AS24482SG.GSHostingIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS19862Bridgehampton National BankUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4384
AS2914NTT America, Inc.TransitIPv4230
AS174Cogent Communications, LLCTransitIPv4135
AS19151BroadbandONE, LLCHostingIPv496
AS54004Cablevision Lightpath LLCUnclassifiedIPv478
AS6939Hurricane Electric LLCTransitIPv472
AS3257GTT Communications Inc.TransitIPv48
AS24482SG.GSHostingIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS19862Bridgehampton National BankUnclassifiedIPv42

Provenance

Where this comes from

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