asn.dev

Observed topology

AS214602 DATACENTER-CLUSTER-FL-AS FIRST SERVER LIMITED

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS214602: 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 LimitedUnclassifiedIPv633

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207569IHOR HOSTING LTDUnclassifiedIPv4 IPv64,297
AS204339FIRST SERVER LIMITEDUnclassifiedIPv4 IPv63,407
AS200740FIRST SERVER LIMITEDUnclassifiedIPv4 IPv6681
AS62251FZCOUnclassifiedIPv666

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS51765Oy Crea Nova Hosting Solution LtdHostingIPv4 IPv68,245
AS207569IHOR HOSTING LTDUnclassifiedIPv4 IPv64,297
AS204339FIRST SERVER LIMITEDUnclassifiedIPv4 IPv63,407
AS200740FIRST SERVER LIMITEDUnclassifiedIPv4 IPv6681
AS9002RETN LimitedUnclassifiedIPv4 IPv6239
AS62251FZCOUnclassifiedIPv666

Provenance

Where this comes from

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