SPEED-IX Route Servers

BGP inherited
Cluster stats
Netblocks8
All fragments 9 blocks across 2 clusters
Cluster ID213183749
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.222.253/32 SPEED-IX Route Servers PEERINGDB ASSIGNED ● high
185.1.222.255/32 SPEED-IX Route Servers PEERINGDB ASSIGNED ● high
185.1.223.0/32 SPEED-IX Route Servers PEERINGDB ASSIGNED ● high
185.1.223.253/32 SPEED-IX Route Servers PEERINGDB ASSIGNED ● high
185.1.223.254/32 SPEED-IX Route Servers PEERINGDB ASSIGNED ● high
2001:7f8:b7::a504:1441:1/128 SPEED-IX Route Servers PEERINGDB ASSIGNED ● high
2001:7f8:b7::a504:1441:2/128 SPEED-IX Route Servers PEERINGDB ASSIGNED ● high
2001:7f8:b7::a505:673:253/128 SPEED-IX Route Servers PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SPEED IX” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

NIC Handles

AS41441