Network · data from 2026-11-12
AS43279 TELESPAZIO-AS Telespazio S.p.A.
Registry name: TELESPAZIO-AS Telespazio S.p.A., IT · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43279, 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.
| 185.76.100.0/22 | No ROA | None | 673 100% |
| 91.188.0.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 94.127.238.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 178.248.88.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 193.43.35.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.208.232.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS43279 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 9 are in fix.csv.
- ROA: none5
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.76.100.0/22 | No ROA covers it. Add a ROA for AS43279, maxLength 22. |
| Route object: none | 185.76.100.0/22 | No route object for it. Add a route object with origin AS43279 in the RIR database for the space. |
| ROA: none | 91.188.0.0/19 | No ROA covers it. Add a ROA for AS43279, maxLength 19. |
| ROA: none | 94.127.238.0/23 | No ROA covers it. Add a ROA for AS43279, maxLength 23. |
| ROA: none | 178.248.88.0/21 | No ROA covers it. Add a ROA for AS43279, maxLength 21. |
| ROA: none | 193.43.35.0/24 | No ROA covers it. Add a ROA for AS43279, maxLength 24. |
Route objects not announced
Route objects with origin AS43279 whose prefix no peer sees AS43279 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.188.6.0/24 | RIPE | No ROA |
| 185.76.101.0/24 | RIPE | No ROA |
| 185.76.102.0/23 | 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.