Network · data from 2026-11-12
AS59655 ForexTime
Registry name: EXINITY-AS Exinity works (CY) LTD, CY · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59655, 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.
| 149.5.66.0/24 | No ROA | Other origin only | 673 100% |
| 178.255.206.0/23 | Valid | Other origin onlycovered by 178.255.200.0/21 | 671 100% |
| 176.97.156.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.97.157.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.255.201.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.255.202.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.255.203.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.255.204.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.255.205.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.199.12.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.199.13.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.199.14.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.199.15.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.255.200.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 178.255.204.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 178.255.206.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS59655's PeeringDB record names no 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 13 are in fix.csv.
- ROA: none1
- Route object: none2
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 149.5.66.0/24 | No ROA covers it. Add a ROA for AS59655, maxLength 24. |
| Route object: none | 149.5.66.0/24 | Route objects for it name AS51297. Add a route object with origin AS59655 in the RIR database for the space. |
| Route object: none | 178.255.206.0/23 | Route objects for it name AS51297. A route object for 178.255.200.0/21 with origin AS59655 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59655 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59655 whose prefix no peer sees AS59655 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 176.97.156.0/23 | RIPE | Valid |
| 178.255.200.0/21 | RIPE | No ROA |
| 178.255.202.0/23 | RIPE | Valid |
| 185.199.12.0/22 | RIPE | No ROA |
| 2a0a:92c0::/29 | RIPE | No ROA |
| 2a0a:92c0::/48 | RIPE | No ROA |
| 2a0a:92c0:1::/48 | RIPE | No ROA |
| 2a0a:92c0:2::/48 | RIPE | No ROA |
| 2a0a:92c0:3::/48 | RIPE | No ROA |
| 2a0a:92c0:206::/48 | 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.