Network · data from 2026-11-12
AS206399 TELECOM-OBJECT Telecom Object SARL
Registry name: TELECOM-OBJECT Telecom Object SARL, FR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206399, 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.186.228.0/24 | No ROA | Nonecovered by 185.186.228.0/22 | 673 100% |
| 185.186.229.0/24 | No ROA | Nonecovered by 185.186.228.0/22 | 673 100% |
| 185.186.230.0/24 | No ROA | Nonecovered by 185.186.228.0/22 | 673 100% |
| 185.186.231.0/24 | No ROA | Nonecovered by 185.186.228.0/22 | 673 100% |
| 2a0b:8a81::/32 | No ROA | Nonecovered by 2a0b:8a80::/29 | 629 99% |
AS-SET
AS206399 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 12 are in fix.csv.
- ROA: none5
- Route object: none5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.186.228.0/24 | No ROA covers it. Add a ROA for AS206399, maxLength 24. |
| Route object: none | 185.186.228.0/24 | No route object for it. A route object for 185.186.228.0/22 with origin AS206399 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206399 in the RIR database for the space. |
| ROA: none | 185.186.229.0/24 | No ROA covers it. Add a ROA for AS206399, maxLength 24. |
| Route object: none | 185.186.229.0/24 | No route object for it. A route object for 185.186.228.0/22 with origin AS206399 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206399 in the RIR database for the space. |
| ROA: none | 185.186.230.0/24 | No ROA covers it. Add a ROA for AS206399, maxLength 24. |
| Route object: none | 185.186.230.0/24 | No route object for it. A route object for 185.186.228.0/22 with origin AS206399 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206399 in the RIR database for the space. |
| ROA: none | 185.186.231.0/24 | No ROA covers it. Add a ROA for AS206399, maxLength 24. |
| Route object: none | 185.186.231.0/24 | No route object for it. A route object for 185.186.228.0/22 with origin AS206399 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206399 in the RIR database for the space. |
| ROA: none | 2a0b:8a81::/32 | No ROA covers it. Add a ROA for AS206399, maxLength 32. |
| Route object: none | 2a0b:8a81::/32 | No route object for it. A route object for 2a0b:8a80::/29 with origin AS206399 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206399 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS206399 whose prefix no peer sees AS206399 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.186.228.0/22 | RIPE | No ROA |
| 2a0b:8a80::/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.