Network · data from 2026-11-12
AS43545 Teledata UK Ltd
Registry name: TELEDATA Datum Datacentres Limited, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43545, 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.
| 80.84.72.0/21 | No ROA | None | 2 0%low visibility |
| 80.84.64.0/21 | No ROA | RIR databaseRIPE | 670 100% |
| 77.74.110.0/24 | Valid | Nonecovered by 77.74.104.0/21 | 672 100% |
| 80.84.90.0/24 | Valid | Nonecovered by 80.84.88.0/21 | 672 100% |
| 78.40.144.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.146.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.150.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.151.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.84.65.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.84.67.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.84.69.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.84.73.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.113.216.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.113.219.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.74.104.0/21 | Valid | RIR databaseRIPE | 670 100% |
| 78.40.144.0/21 | Valid | RIR databaseRIPE | 670 100% |
| 80.84.80.0/21 | Valid | RIR databaseRIPE | 670 100% |
| 80.84.88.0/21 | Valid | RIR databaseRIPE | 670 100% |
| 2a02:24d0::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:24d0::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS43545's PeeringDB record names no 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 31 are in fix.csv.
- ROA: none2
- Route object: none3
- Route object: not announced26
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 80.84.72.0/21 | No ROA covers it. Add a ROA for AS43545, maxLength 21. |
| Route object: none | 80.84.72.0/21 | No route object for it. Add a route object with origin AS43545 in the RIR database for the space. |
| ROA: none | 80.84.64.0/21 | No ROA covers it. Add a ROA for AS43545, maxLength 21. |
| Route object: none | 77.74.110.0/24 | No route object for it. A route object for 77.74.104.0/21 with origin AS43545 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43545 in the RIR database for the space. |
| Route object: none | 80.84.90.0/24 | No route object for it. A route object for 80.84.88.0/21 with origin AS43545 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43545 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS43545 whose prefix no peer sees AS43545 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.74.109.0/25 | RIPE | Invalid: maxLength |
| 80.84.80.0/20 | RIPE | No ROA |
| 80.84.86.0/24 | RIPE | Valid |
| 80.84.87.0/24 | RIPE | Valid |
| 85.202.196.0/22 | RIPE | Valid |
| 185.35.56.0/22 | RIPE | Invalid: origin |
| 185.35.56.0/23 | RIPE | Invalid: origin |
| 185.35.58.0/23 | RIPE | Invalid: origin |
| 185.113.216.0/22 | RIPE | Valid |
| 185.113.217.0/24 | RIPE | Valid |
| 185.113.218.0/24 | RIPE | Valid |
| 185.182.68.0/22 | RIPE | No ROA |
| 185.182.68.0/23 | RIPE | Invalid: origin |
| 185.182.68.0/24 | RIPE | Invalid: origin |
| 185.182.69.0/24 | RIPE | Invalid: origin |
| 185.182.70.0/24 | RIPE | Invalid: origin |
| 212.84.64.0/24 | RIPE | Invalid: maxLength |
| 212.84.66.0/24 | RIPE | Invalid: maxLength |
| 212.84.68.0/24 | RIPE | Valid |
| 212.84.70.0/24 | RIPE | Invalid: maxLength |
| 212.84.71.0/24 | RIPE | Invalid: maxLength |
| 212.84.72.0/24 | RIPE | Invalid: maxLength |
| 212.84.74.0/24 | RIPE | Invalid: maxLength |
| 212.84.75.0/24 | RIPE | Invalid: maxLength |
| 212.84.76.0/24 | RIPE | Invalid: maxLength |
| 2a0f:3680::/29 | RIPE | No ROA |
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.