Network · data from 2026-11-12
AS208205 talsion TALSION SASU
Registry name: talsion TALSION SASU, FR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208205, 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.
| 178.17.220.0/24 | Valid | None | 673 100% |
| 178.17.221.0/24 | Valid | None | 673 100% |
| 178.17.222.0/24 | Valid | None | 673 100% |
| 178.17.223.0/24 | Valid | None | 673 100% |
AS-SET
AS208205 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 4 are in fix.csv.
- Route object: none4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 178.17.220.0/24 | No route object for it. Add a route object with origin AS208205 in the RIR database for the space. |
| Route object: none | 178.17.221.0/24 | No route object for it. Add a route object with origin AS208205 in the RIR database for the space. |
| Route object: none | 178.17.222.0/24 | No route object for it. Add a route object with origin AS208205 in the RIR database for the space. |
| Route object: none | 178.17.223.0/24 | No route object for it. Add a route object with origin AS208205 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS208205 is announced.
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.