Network · data from 2026-11-12
AS401986 COHERENTLY - Coherently Inc
Registry name: COHERENTLY - Coherently Inc, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS401986, 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.
| 23.145.204.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 2604:20a0::/32 | No ROA | RIR databaseARIN | 635 100% |
| 45.54.44.0/24 | Valid | None | 14 2%low visibility |
| 2607:f740:e64a::/48 | Valid | Other origin only | 10 2%low visibility |
AS-SET
AS401986 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 5 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 23.145.204.0/24 | No ROA covers it. Add a ROA for AS401986, maxLength 24. |
| ROA: none | 2604:20a0::/32 | No ROA covers it. Add a ROA for AS401986, maxLength 32. |
| Route object: none | 45.54.44.0/24 | No route object for it. Add a route object with origin AS401986 in the RIR database for the space. |
| Route object: none | 2607:f740:e64a::/48 | Route objects for it name AS63911. Add a route object with origin AS401986 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS401986 whose prefix no peer sees AS401986 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 81.85.58.0/24 | 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.