Network · data from 2026-11-12
AS49425 Digital Realty United Kingdom
Registry name: DIGITAL-REALTY-UK Digital Realty (UK) Limited, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49425, 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.
| 83.142.64.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 91.206.118.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 91.206.118.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.206.119.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 45.75.132.0/23 | Valid | Nonecovered by 45.75.128.0/17 | 673 100% |
| 45.75.131.0/24 | Valid | Nonecovered by 45.75.128.0/17 | 672 100% |
| 185.169.144.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 45.75.128.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 74.115.206.0/24 | Valid | RIR databaseARIN | 672 100% |
| 2a0a:4900::/29 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS49425: AS-DRT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS49425 isn't in the set, or no route object for AS49425 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS49425 in it | Not covered |
|---|---|---|---|---|---|
| AS-DRT | RIPE | 171 | 17 | Yes | 0 |
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 10 are in fix.csv.
- ROA: none4
- Route object: none2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 83.142.64.0/21 | No ROA covers it. Add a ROA for AS49425, maxLength 21. |
| ROA: none | 91.206.118.0/23 | No ROA covers it. Add a ROA for AS49425, maxLength 23. |
| ROA: none | 91.206.118.0/24 | No ROA covers it. Add a ROA for AS49425, maxLength 24. |
| ROA: none | 91.206.119.0/24 | No ROA covers it. Add a ROA for AS49425, maxLength 24. |
| Route object: none | 45.75.132.0/23 | No route object for it. A route object for 45.75.128.0/17 with origin AS49425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49425 in the RIR database for the space. |
| Route object: none | 45.75.131.0/24 | No route object for it. A route object for 45.75.128.0/17 with origin AS49425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49425 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS49425 whose prefix no peer sees AS49425 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.75.192.0/18 | RIPE | Valid |
| 185.29.46.0/24 | ALTDB, RIPE | No ROA |
| 185.169.145.0/24 | RIPE | Valid |
| 2a0a:4900::/30 | RIPE | Invalid: maxLength |
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.