Network · data from 2026-11-12
AS29045 ITACTION IT Action Limited
Registry name: ITACTION IT Action Limited, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29045, 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.
| 89.107.232.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 83.136.0.0/21 | No ROA | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS29045 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 7 are in fix.csv.
- ROA: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.107.232.0/22 | No ROA covers it. Add a ROA for AS29045, maxLength 22. |
| ROA: none | 83.136.0.0/21 | No ROA covers it. Add a ROA for AS29045, maxLength 21. |
Route objects not announced
Route objects with origin AS29045 whose prefix no peer sees AS29045 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.207.40.0/23 | RIPE | No ROA |
| 31.207.42.0/24 | RIPE | No ROA |
| 89.107.232.0/21 | RIPE | No ROA |
| 89.107.236.0/22 | RIPE | No ROA |
| 2a04:1140::/32 | 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.