Network · data from 2026-11-12
AS21371 EQUINIX-UK-ASN EQUINIX (SERVICES) LIMITED
Registry name: EQUINIX-UK-ASN EQUINIX (SERVICES) LIMITED, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS21371, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 151.106.193.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.191.208.0/23 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS21371 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 14 are in fix.csv.
- ROA: none2
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 151.106.193.0/24 | No ROA covers it. Add a ROA for AS21371, maxLength 24. |
| ROA: none | 185.191.208.0/23 | No ROA covers it. Add a ROA for AS21371, maxLength 23. |
Route objects not announced
Route objects with origin AS21371 whose prefix no peer sees AS21371 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.46.0.0/21 | RIPE | Valid |
| 80.69.0.0/19 | RIPE | Valid |
| 88.84.128.0/21 | RIPE | Invalid: origin |
| 89.187.96.0/19 | RIPE | Valid |
| 151.106.201.0/24 | RIPE | No ROA |
| 157.234.219.0/24 | RIPE-NONAUTH | No ROA |
| 185.2.164.0/22 | RIPE | Valid |
| 194.145.30.0/24 | RIPE | No ROA |
| 199.233.130.0/24 | RIPE-NONAUTH | No ROA |
| 2001:1a08::/32 | RIPE | Invalid: origin |
| 2a03:6980::/32 | RIPE | Valid |
| 2a03:6c80::/32 | RIPE | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.