Économie
Paxos completes trading maintenance on its v2 API and FIX
Paxos announced that scheduled maintenance ended on November 8 at 4:00 a.m. Paris time. Its v2 API order service and FIX trading were subsequently listed as operational.

Maintenance ended at 4:00 a.m. in Paris
Paxos said maintenance on two of its trading services was complete on Sunday, November 8, 2026. The official report records completion at 3:00 a.m. UTC, or 4:00 a.m. in Paris. The company had reported that the work began at 1:00 a.m. UTC, or 2:00 a.m. in Paris. On the US East Coast, that was 8:00 p.m. on Saturday, November 7. The first notice was posted on Friday, November 6.
The status page listed a window from 1:00 a.m. to 3:00 a.m. UTC. The notice warned that trading would pause during the work. Paxos marked the maintenance complete within seconds of the scheduled end. The report provides no minute-by-minute record of availability. The window therefore establishes when maintenance took place without showing the exact duration of the interruption each customer experienced.
The work affected v2 API orders and FIX trading
Paxos named two components in its report. The first handles trading orders in its v2 API. The second is trading via FIX, a messaging protocol used to pass instructions and market information between financial systems. The notice covered trading through these interfaces. After the maintenance ended, Paxos’s status page listed both components as operational.
Paxos’s dashboard lists these two components separately from market data, pricing, and quotation services, as well as fiat and crypto asset transfers. The maintenance report does not list those other services among the affected components. This distinction defines the scope the company announced. It does not establish the outcome of individual transfers or the availability of services operated by partners.
The report leaves open what happened to outstanding orders
The closing notice confirms that the maintenance is over. It does not describe how orders that were open before the pause were handled. It gives no indication whether requests submitted shortly before the window were accepted, rejected, or left pending. It also does not explain how any delay in sending confirmations was cleared. Those details concern the status of individual orders, beyond the overall status of the service.
The public page records three moments documented by Paxos. A first notice announced the work, a second confirmed that it had started, and a third marked its completion. The subsequent operational status indicates that Paxos considered both interfaces available at the time of the check. The status page provides no tally of affected orders or results for transactions in any individual account.
