Network · data from 2026-11-12
AS62827 THALES-DIS-COO-DFW-01 - Thales DIS USA, Inc.
Registry name: THALES-DIS-COO-DFW-01 - Thales DIS USA, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62827, 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.
| 205.216.51.0/24 | No ROA | RIR databaseARIN | 2 0%low visibility |
| 205.219.238.0/24 | No ROA | RIR databaseARIN | 2 0%low visibility |
| 216.227.196.0/24 | No ROA | RIR databaseARIN | 2 0%low visibility |
| 198.17.211.0/24 | Valid | RIR databaseARIN | 673 100% |
AS-SET
AS62827 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 14 are in fix.csv.
- ROA: none3
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 205.216.51.0/24 | No ROA covers it. Add a ROA for AS62827, maxLength 24. |
| ROA: none | 205.219.238.0/24 | No ROA covers it. Add a ROA for AS62827, maxLength 24. |
| ROA: none | 216.227.196.0/24 | No ROA covers it. Add a ROA for AS62827, maxLength 24. |
Route objects not announced
Route objects with origin AS62827 whose prefix no peer sees AS62827 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 158.51.232.0/22 | ARIN | Valid |
| 198.96.5.0/24 | ARIN | Valid |
| 204.71.234.0/24 | ARIN | No ROA |
| 205.219.252.0/24 | ARIN | No ROA |
| 205.219.253.0/24 | ARIN | No ROA |
| 206.128.129.0/24 | ARIN | No ROA |
| 209.209.108.0/22 | ARIN | Valid |
| 216.14.171.0/24 | ARIN | No ROA |
| 216.34.166.0/24 | ARIN | No ROA |
| 216.182.205.0/24 | ARIN | No ROA |
| 2620:7f:a000::/48 | ARIN | Valid |
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.