Network · data from 2026-11-12
AS29400 TULLETT-AS TP ICAP GROUP SERVICES LIMITED
Registry name: TULLETT-AS TP ICAP GROUP SERVICES LIMITED, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29400, 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.
| 194.32.72.0/23 | No ROA | None | 2 0%low visibility |
| 192.149.225.0/24 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 673 100% |
| 193.130.195.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 193.130.196.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 193.130.197.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 198.99.68.0/24 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 673 100% |
| 185.180.116.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 193.130.200.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 194.32.72.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.32.73.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.32.74.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 198.99.67.0/24 | No ROA | RIR databaseARIN, RADB, RIPE-NONAUTH | 673 100% |
| 216.131.38.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 185.180.117.0/24 | No ROA | RIR databaseRIPE | 4 1%low visibility |
AS-SET
AS29400 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 25 are in fix.csv.
- ROA: none14
- Route object: none1
- Route object: RIR5
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 194.32.72.0/23 | No ROA covers it. Add a ROA for AS29400, maxLength 23. |
| Route object: none | 194.32.72.0/23 | No route object for it. Add a route object with origin AS29400 in the RIR database for the space. |
| ROA: none | 192.149.225.0/24 | No ROA covers it. Add a ROA for AS29400, maxLength 24. |
| Route object: RIR | 192.149.225.0/24 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 193.130.195.0/24 | No ROA covers it. Add a ROA for AS29400, maxLength 24. |
| Route object: RIR | 193.130.195.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 193.130.196.0/24 | No ROA covers it. Add a ROA for AS29400, maxLength 24. |
| Route object: RIR | 193.130.196.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 193.130.197.0/24 | No ROA covers it. Add a ROA for AS29400, maxLength 24. |
| Route object: RIR | 193.130.197.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 198.99.68.0/24 | No ROA covers it. Add a ROA for AS29400, maxLength 24. |
| Route object: RIR | 198.99.68.0/24 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 185.180.116.0/23 | No ROA covers it. Add a ROA for AS29400, maxLength 23. |
| ROA: none | 193.130.200.0/23 | No ROA covers it. Add a ROA for AS29400, maxLength 23. |
| ROA: none | 194.32.72.0/24 | No ROA covers it. Add a ROA for AS29400, maxLength 24. |
| ROA: none | 194.32.73.0/24 | No ROA covers it. Add a ROA for AS29400, maxLength 24. |
| ROA: none | 194.32.74.0/24 | No ROA covers it. Add a ROA for AS29400, maxLength 24. |
| ROA: none | 198.99.67.0/24 | No ROA covers it. Add a ROA for AS29400, maxLength 24. |
| ROA: none | 216.131.38.0/24 | No ROA covers it. Add a ROA for AS29400, maxLength 24. |
| ROA: none | 185.180.117.0/24 | No ROA covers it. Add a ROA for AS29400, maxLength 24. |
Route objects not announced
Route objects with origin AS29400 whose prefix no peer sees AS29400 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.180.116.0/24 | RIPE | No ROA |
| 193.130.196.0/23 | RADB | No ROA |
| 193.130.200.0/24 | RIPE | No ROA |
| 193.130.201.0/24 | RIPE | No ROA |
| 198.99.66.0/24 | RIPE-NONAUTH | 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.