Affected Components: Trading API (CLOB)

Sep 1, 20:21:40 GMT+0
Investigating - We are currently investigating this incident..

Duration: 2 hours

Affected Components: Perpetuals API, Perpetuals trading, Perpetuals market data

Sep 1, 07:30:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

Sep 1, 07:30:00 GMT+0
Identified - Maintenance is now in progress..

Sep 1, 08:52:01 GMT+0
Identified - Maintenance extended. .

Sep 1, 09:30:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 4 hours and 39 minutes

Affected Components: Trading API (CLOB)

Sep 1, 01:07:50 GMT+0
Resolved - This incident has been resolved..

Aug 31, 20:28:59 GMT+0
Investigating - We are currently investigating this incident..

Aug 31, 23:09:43 GMT+0
Identified - Trading will be temporarily paused for a short while we apply a fix. Cancel-only mode will be enabled before normal trading resumes..

Sep 1, 00:54:20 GMT+0
Monitoring - The fix is complete and we are currently in cancel-only mode. Trading will resume in 5 minutes..

Duration: 4 hours and 25 minutes

Affected Components: Trading API (CLOB)

Aug 31, 06:23:02 GMT+0
Investigating - We are currently investigating this incident..

Aug 31, 06:30:48 GMT+0
Identified - We are pausing trading while we continue to address this incident. There will be a cancel-only mode before trading is resumed..

Aug 31, 08:29:16 GMT+0
Identified - A fix for the issue is in progress. We are targeting to resume trading by latest 10:00am UTC, but will send an updated ETA as we have it. There will be 15 minutes of cancel-only before trading resumes..

Aug 31, 09:40:29 GMT+0
Identified - The fix for the issue is still being applied. We are targeting 11:00am UTC for full trading resumption, with cancel-only mode for at least 15 minutes beforehand..

Aug 31, 10:23:58 GMT+0
Monitoring - The fix has been applied and we will remain in cancel-only mode until 10:40am UTC before trading resumes..

Aug 31, 10:47:41 GMT+0
Resolved - This incident has been resolved..

Duration: 32 minutes

Affected Components: Trading API (CLOB)

Aug 31, 00:40:54 GMT+0
Investigating - We are currently investigating this incident..

Aug 31, 01:06:43 GMT+0
Identified - We are currently in cancel-only mode and monitoring..

Aug 31, 01:12:28 GMT+0
Resolved - This incident has been resolved..

Duration: 52 minutes

Affected Components: Trading API (CLOB)

Aug 30, 17:36:54 GMT+0
Investigating - We are currently investigating this incident..

Aug 30, 17:55:47 GMT+0
Investigating - We are pausing trading while we investigate the issue.

Aug 30, 18:18:58 GMT+0
Identified - We are currently in cancel-only mode while monitoring the fix pushed out for the issue..

Aug 30, 18:29:16 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour

Affected Components: Trading API (CLOB)

Aug 27, 21:39:07 GMT+0
Identified - A scheduled CLOB release requires a brief restart, with downtime of up to \~10 minutes. Order placement, cancels, and fills may be temporarily unavailable..

Aug 28, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Aug 28, 05:00:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 38 minutes

Affected Components: Perpetuals API, Perpetuals trading, Perpetuals market data

Aug 28, 08:00:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

Aug 28, 08:02:46 GMT+0
Identified - Maintenance is now in progress..

Aug 28, 08:40:18 GMT+0
Completed - Maintenance has completed successfully..

Duration: 1 hour

Affected Components: Clob Websocket, Trading API (CLOB)

Aug 26, 22:03:01 GMT+0
Identified - We are updating periphery services for the CLOB. No downtime is expected. Users may experience temporary degradation around API key creation and deletes..

Aug 27, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Aug 27, 05:00:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 3 hours and 30 minutes

Affected Components: Clob Websocket, Trading API (CLOB)

Aug 25, 18:24:49 GMT+0
Identified - A scheduled CLOB release requires a brief restart, with downtime of up to \~10 minutes. Order placement, cancels, and fills may be temporarily unavailable..

Aug 26, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Aug 26, 04:53:13 GMT+0
Identified - Apologies, due to technical issues the maintenance window for CLOB will be extended by 1 hour till 6am UTC..

Aug 26, 05:50:12 GMT+0
Identified - The team is still addressing the issue, the maintenance window for CLOB will be extended by another 1 hour till 7am UTC..

Aug 26, 06:56:19 GMT+0
Identified - We are in-process of restoring databases to previous snapshots. Trading is still degraded. Expected resolution is 7:30am UTC..

Aug 26, 07:30:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 3 hours and 30 minutes

Affected Components: Perpetuals API, Perpetuals trading, Perpetuals market data

Aug 24, 18:20:14 GMT+0
Investigating - Trading is temporarily degraded, trading will be disabled while the team addresses an issue affecting trading performance..

Aug 24, 19:51:23 GMT+0
Resolved - This incident has been resolved..

Aug 24, 20:35:00 GMT+0
Investigating - We are currently investigating this incident..

Aug 24, 21:39:51 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Aug 24, 21:50:00 GMT+0
Resolved - This incident has been resolved..

Duration: 32 minutes

Affected Components: Perpetuals API, Perpetuals trading, Perpetuals market data

Aug 24, 17:40:08 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Aug 24, 17:49:23 GMT+0
Resolved - This incident has been resolved..

Aug 24, 17:17:28 GMT+0
Investigating - Trading will be temporarily disabled while the team addresses an issue affecting trading performance..

Duration: 1 hour and 36 minutes

Affected Components: Perpetuals API, Perpetuals trading, Perpetuals market data

Aug 24, 13:30:00 GMT+0
Identified - Trading is temporarily disabled while the team addresses an issue affecting trading performance..

Aug 24, 15:06:18 GMT+0
Resolved - The incident has been resolved. The team is monitoring performance closely..

Duration: 2 hours and 39 minutes

Affected Components: Perpetuals API, Perpetuals trading

Aug 24, 08:40:53 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

Aug 24, 08:45:31 GMT+0
Identified - Maintenance is now in progress..

Aug 24, 10:00:54 GMT+0
Identified - Maintenance has been extended as the release process is taking longer than expected. It should be completed within the next 30 minutes. We will update here when completed..

Aug 24, 11:24:34 GMT+0
Completed - Maintenance is complete and trading is fully operational. We apologize again for the extended maintenance window..

Duration: 38 minutes

Affected Components: Trading API (CLOB)

Aug 22, 13:13:25 GMT+0
Identified - Trading is paused due to an issue with balances, will resume in cancel only mode for 2 mins once resolved..

Aug 22, 13:13:33 GMT+0
Identified - We are continuing to work on a fix for this incident..

Aug 22, 13:38:00 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Aug 22, 13:51:15 GMT+0
Resolved - This incident has been resolved..

Affected Components: Trading API (CLOB)

Aug 19, 11:23:40 GMT+0
Identified - We are continuing to work on a fix for this incident..

Aug 19, 11:23:41 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour and 39 minutes

Affected Components: Clob Websocket, Trading API (CLOB)

Aug 19, 09:19:08 GMT+0
Investigating - We are currently investigating this incident..

Aug 19, 10:11:03 GMT+0
Identified - We are continuing to work on a fix for this incident..

Aug 19, 10:28:15 GMT+0
Identified - The team is at the final stages of testing a fix to restore the service. The system is already in post+cancel-only mode. It will remain in post+cancel-only for 5 minutes after the service is restored..

Aug 19, 10:47:30 GMT+0
Monitoring - We will resume trading in 2 minutes currently in cancel only mode. .

Aug 19, 10:58:06 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour and 30 minutes

Affected Components: Clob Websocket, Trading API (CLOB)

Aug 18, 17:30:27 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

Aug 19, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Aug 19, 04:47:15 GMT+0
Identified - Apologies, the maintenance window will be extended to 5.30am UTC..

Aug 19, 05:30:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 30 minutes

Affected Components: Trading API (CLOB)

Aug 17, 15:36:23 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

Aug 17, 21:15:01 GMT+0
Identified - Maintenance is now in progress.

Aug 17, 21:45:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 6 days, 9 hours and 29 minutes

Affected Components: Markets and Position data

Aug 17, 12:45:00 GMT+0
Identified - The team is working on an issue affecting **Crypto Market Resolution**. Users may experience delays in resolution of crypto market outcomes..

Aug 17, 15:18:28 GMT+0
Resolved - This incident has been resolved..

Duration: 41 minutes

Affected Components: Perpetuals API, Perpetuals market data, Perpetuals trading

Aug 17, 07:53:33 GMT+0
Identified - Scheduled maintenance. Trading may be temporarily unavailable during this time..

Aug 17, 08:00:01 GMT+0
Identified - Maintenance is now in progress.

Aug 17, 08:40:56 GMT+0
Completed - Maintenance has completed successfully. The team is monitoring metrics. .

Duration: 1 hour and 19 minutes

Affected Components: Trading API (CLOB)

Aug 14, 22:13:06 GMT+0
Investigating - We are currently investigating this incident..

Aug 14, 23:04:28 GMT+0
Identified - We have identified the issue and are working on a fix..

Aug 14, 23:13:38 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Aug 14, 23:21:35 GMT+0
Monitoring - We are seeing slight degradation again and are monitoring..

Aug 14, 23:31:47 GMT+0
Resolved - This incident has been resolved..

Duration: 53 minutes

Affected Components: Trading API (CLOB)

Aug 13, 05:26:34 GMT+0
Investigating - We are currently investigating this incident..

Aug 13, 06:19:26 GMT+0
Resolved - This incident has been resolved..

Aug 13, 05:48:07 GMT+0
Identified - We are pausing trading while we continue to investigate..

Aug 13, 05:58:06 GMT+0
Monitoring - We are restarting in the next 5 minutes to address the issues..

Aug 13, 06:11:30 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Duration: 30 minutes

Affected Components: Clob Websocket, Polymarket Web app, Trading API (CLOB)

Aug 12, 19:55:02 GMT+0
Identified - We will perform scheduled maintenance on the CLOB 4:30AM UTC - 5AM UTC. During this window, users may receive HTTP 503 errors when placing or cancelling orders, or when viewing open orders and order status. Please cancel any unwanted open orders before maintenance begins..

Aug 13, 04:30:01 GMT+0
Identified - Maintenance is now in progress.

Aug 13, 05:00:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 57 minutes

Affected Components: Polymarket Web app, Trading API (CLOB)

Aug 12, 15:04:48 GMT+0
Identified - We are continuing to work on a fix for this incident..

Aug 12, 15:00:00 GMT+0
Investigating - We are currently investigating this incident..

Aug 12, 15:54:37 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Aug 12, 15:57:20 GMT+0
Resolved - This incident has been resolved..

Duration: 46 minutes

Affected Components: Perpetuals API, Perpetuals market data, Perpetuals trading

Aug 12, 08:30:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

Aug 12, 09:16:18 GMT+0
Completed - Maintenance has completed successfully..

Duration: 17 hours and 3 minutes

Affected Components: Perpetuals API, Perpetuals market data, Perpetuals trading

Aug 11, 15:08:53 GMT+0
Identified - We are continuing to work on a fix for this incident..

Aug 11, 21:30:00 GMT+0
Resolved - This incident has been resolved..

Duration: 4 hours and 47 minutes

Affected Components: Perpetuals API, Perpetuals market data, Perpetuals trading

Aug 10, 10:00:45 GMT+0
Investigating - We are currently investigating this incident..

Aug 10, 14:48:03 GMT+0
Resolved - This incident has been resolved..

Duration: 15 minutes

Affected Components: Trading API (CLOB)

Aug 7, 17:21:21 GMT+0
Identified - An internal service upgrade will be deployed. No downtime is expected and trading should continue as normal, but there may be brief instability during this window. Specifically, rest api might face some responses for brief period..

Aug 7, 22:02:01 GMT+0
Identified - Maintenance is now in progress.

Aug 7, 22:17:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 45 minutes

Affected Components: Perpetuals API, Perpetuals market data, Perpetuals trading

Aug 6, 08:30:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

Aug 6, 09:10:21 GMT+0
Completed - Maintenance has completed successfully..

Duration: 1 hour and 14 minutes

Affected Components: Clob Websocket

Aug 5, 14:19:54 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Aug 5, 15:34:07 GMT+0
Resolved - This incident has been resolved..

Duration: 23 minutes

Affected Components: Websocket (RTDS), Polymarket Web app, Trading API (CLOB)

Aug 4, 22:49:05 GMT+0
Identified - Scheduled maintenance for an infrastructure improvement for the price history service * Trading will be briefly disabled with some requests returning 503 * Websocket messages for trades and orders (user and market channels) will also be under maintenance during this time Brief post-only window after restart (2 min) before normal matching resumes. Post-only: only orders explicitly set with `postOnly: true` are accepted. Regular limit orders without the flag, market orders, and any taking liquidity will be rejected. Cancels for existing orders will still go through. See [**POST /order API reference**](https://docs.polymarket.com/api-reference/trade/post-a-new-order#body-post-only) for the post-only flag.

Aug 5, 04:27:31 GMT+0
Identified - Maintenance is now in progress..

Aug 5, 04:50:43 GMT+0
Completed - Maintenance has completed successfully..

Duration: 10 minutes

Affected Components: Markets and Position data, Polymarket Web app

Aug 4, 21:40:01 GMT+0
Identified - Maintenance is now in progress.

Aug 4, 21:30:02 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

Aug 4, 21:50:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 40 minutes

Affected Components: Trading API (CLOB)

Aug 4, 15:35:36 GMT+0
Resolved - This incident has been resolved..

Aug 4, 14:55:59 GMT+0
Investigating - We have detected that some users may have issues whilst trying to do sports trading, we're currently investigating the issue..

Aug 4, 15:21:33 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Duration: 1 hour and 43 minutes

Affected Components: Perpetuals trading, Perpetuals API, Perpetuals market data

Aug 4, 08:30:00 GMT+0
Identified - We are currently investigating this incident. Balances and prices aren't displayed, and trading unavailable..

Aug 4, 10:12:48 GMT+0
Resolved - The issue affecting trading has been fixed. Balances, prices, and order placement are all working normally again. We're continuing to monitor to confirm things stay stable. Thanks for your patience..

Duration: 1 hour and 8 minutes

Affected Components: Perpetuals trading, Perpetuals API

Aug 3, 08:18:00 GMT+0
Identified - Scheduled maintenance for release..

Aug 3, 09:26:24 GMT+0
Completed - Maintenance has completed successfully..

Duration: 35 minutes

Affected Components: Trading API (CLOB)

Jul 30, 10:20:00 GMT+0
Investigating - We are currently investigating an incident causing slowed order processing..

Jul 30, 10:55:00 GMT+0
Resolved - This incident has been resolved..

Duration: 6 hours and 18 minutes

Affected Components: Polymarket Web app, Trading API (CLOB)

Jul 29, 15:30:00 GMT+0
Investigating - We are currently investigating an incident involving lag in the /price-history endpoint. This causes charts on markets to load slowly or not load in some cases..

Jul 29, 21:47:39 GMT+0
Resolved - This incident has been resolved..

Duration: 6 hours and 27 minutes

Affected Components: Trading API (CLOB)

Jul 28, 18:42:46 GMT+0
Identified - We are continuing on backfill to populate back the data.

Jul 28, 17:00:00 GMT+0
Investigating - We are currently investigating this incident..

Jul 28, 18:10:38 GMT+0
Resolved - This incident has been resolved..

Jul 28, 23:27:22 GMT+0
Resolved - This incident has been resolved..

Duration: 2 hours and 55 minutes

Affected Components: Trading API (CLOB)

Jul 28, 12:52:41 GMT+0
Identified - We are continuing to work on a fix for this incident..

Jul 28, 15:48:05 GMT+0
Resolved - This incident has been resolved..

Duration: 55 minutes

Affected Components: Trading API (CLOB)

Jul 28, 08:39:10 GMT+0
Identified - The team is revert the latest change which caused trading disruption. Trading will be paused, followed by post-only mode..

Jul 28, 08:40:01 GMT+0
Identified - Maintenance is now in progress.

Jul 28, 08:57:36 GMT+0
Identified - Maintenance extended for rollback procedure.

Jul 28, 09:34:51 GMT+0
Completed - Maintenance has completed successfully..

Duration: 1 hour and 31 minutes

Affected Components: Trading API (CLOB)

Jul 28, 09:35:57 GMT+0
Resolved - This incident has been resolved..

Jul 28, 08:04:45 GMT+0
Investigating - Trading is experiencing degraded performance. We are investigating and will post updates here..

Duration: 57 minutes

Affected Components: Trading API (CLOB)

Jul 27, 19:50:34 GMT+0
Identified - Finalizing the async db release. This cuts latency on the core matching engine, but it changes how you get transaction hashes after posting an order. **What to expect:** * Trading intermittent during maintenance, for up to 1.5h. * Brief post-only window after restart (2 min) before normal matching resumes. Cancels accepted. * There may be 503 errors during the maintenance, where trades would not be accepted * There will be brief period of degradation with the get /orders endpoint. Post-only: only orders explicitly set with postOnly: true are accepted. Regular limit orders without the flag, market orders, and any taking liquidity will be rejected. Cancels for existing orders will still go through. [**See POST /order API reference for the post-only flag.**](https://docs.polymarket.com/api-reference/trade/post-a-new-order#body-post-only) **What's changing** **for developers** Today, `POST /order` and `POST /orders` return `transactionHashes` inline on successful FAK/FOK matches. After this rollout, those endpoints won't return `transactionHashes` at all — you'll get `tradeIDs` instead. * tradeIDs behavior itself isn't changing: on a match you get tradeIDs back, on no match or failure you don't. * Websocket updates are unchanged. If you're already reading fills off the websocket, nothing to do here. **What you need to do** On CLOB client (TS / Python / Rust): it handles this for you — resolves transactions after posting and returns hashes, successful trades, and any failures. Just bump to the latest version. Custom API integration: if you depend on `transactionHashes` from the REST response, you'll need to resolve them yourself off `tradeIDs` — poll trades until each has a hash or comes back `FAILED`. Reference PRs: * TypeScript: <https://github.com/Polymarket/clob-client-v2/pull/89> * Python: <https://github.com/Polymarket/py-clob-client-v2/pull/101> * Rust: <https://github.com/Polymarket/rs-clob-client-v2/pull/83>.

Jul 28, 05:00:01 GMT+0
Identified - Maintenance is now in progress.

Jul 28, 05:57:02 GMT+0
Completed - Maintenance has completed successfully..

Duration: 25 days, 12 hours and 1 minute

Affected Components: Trading API (CLOB)

Jul 23, 18:52:45 GMT+0
Identified - Latency-focused release, with the introduction of our async-db pipeline. This cuts latency on the core matching engine, but it changes how you get transaction hashes after posting an order. **What to expect:** * Trading intermittent during maintenance, for up to 1.5h. * Brief post-only window after restart (2 min) before normal matching resumes. Cancels accepted. * There may be 503 errors during the maintenance, where trades would not be accepted Post-only: only orders explicitly set with postOnly: true are accepted. Regular limit orders without the flag, market orders, and any taking liquidity will be rejected. Cancels for existing orders will still go through. [**See POST /order API reference for the post-only flag.**](https://docs.polymarket.com/api-reference/trade/post-a-new-order#body-post-only) **What's changing** **for developers** Today, `POST /order` and `POST /orders` return `transactionHashes` inline on successful FAK/FOK matches. After this rollout, those endpoints won't return `transactionHashes` at all — you'll get `tradeIDs` instead. * tradeIDs behavior itself isn't changing: on a match you get tradeIDs back, on no match or failure you don't. * Websocket updates are unchanged. If you're already reading fills off the websocket, nothing to do here. **What you need to do** On CLOB client (TS / Python / Rust): it handles this for you — resolves transactions after posting and returns hashes, successful trades, and any failures. Just bump to the latest version. Custom API integration: if you depend on `transactionHashes` from the REST response, you'll need to resolve them yourself off `tradeIDs` — poll trades until each has a hash or comes back `FAILED`. Reference PRs: * TypeScript: <https://github.com/Polymarket/clob-client-v2/pull/89> * Python: <https://github.com/Polymarket/py-clob-client-v2/pull/101> * Rust: <https://github.com/Polymarket/rs-clob-client-v2/pull/83> .

Jul 24, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Jul 24, 05:04:46 GMT+0
Completed - Maintenance has completed successfully. Quick heads up: the txnHash change isn’t live yet. We held off enabling it in prod while we sort out an extra dependency first. No action needed on your end - you’re still getting transactionHashes in the response as usual, and there’s no latency impact from this. We’ll follow up with prod release timing once it’s confirmed.”.

Duration: 30 minutes

Affected Components: Trading API (CLOB)

Jul 22, 22:51:25 GMT+0
Identified - Routine maintenance for gateway components. Trading may be briefly degraded during the window, with no downtime; we'll update this page once it's complete..

Jul 23, 03:30:01 GMT+0
Identified - Maintenance is now in progress.

Jul 23, 04:00:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 45 minutes

Affected Components: Trading API (CLOB)

Jul 22, 14:46:25 GMT+0
Identified - Routine maintenance. Trading may be briefly degraded during the window, with no downtime; we'll update this page once it's complete..

Jul 22, 16:00:01 GMT+0
Identified - Maintenance is now in progress.

Jul 22, 16:45:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 51 minutes

Affected Components: Trading API (CLOB)

Jul 21, 04:10:00 GMT+0
Identified - Maintenance is now in progress..

Jul 21, 04:00:00 GMT+0
Identified - What to expect: * Trading intermittent for up to 35 minutes. * Brief post-only window after restart (2 min) before normal matching resumes. Cancels accepted. Post-only: only orders explicitly set with postOnly: true are accepted. Regular limit orders without the flag, market orders, and any taking liquidity will be rejected. Cancels for existing orders will still go through. [See POST /order API reference for the post-only flag.](https://docs.polymarket.com/api-reference/trade/post-a-new-order#body-post-only).

Jul 21, 05:00:51 GMT+0
Completed - Maintenance has completed successfully..

Duration: 10 minutes

Affected Components: Markets and Position data, Account Access & Authentication, On-chain settlement (Polygon RPC), Websocket (RTDS), Polymarket Web app, Trading API (CLOB)

Jul 16, 09:51:24 GMT+0
Identified - We are planning a Data API release during this time. Combo positions may not appear in your portfolio for up to 10 minutes. Your funds are safe, and position tracking will resume at the end of the maintenance window..

Jul 16, 10:00:01 GMT+0
Identified - Maintenance is now in progress.

Jul 16, 10:10:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 35 minutes

Affected Components: Trading API (CLOB)

Jul 15, 18:55:47 GMT+0
Identified - What to expect: * Trading intermittent for up to 1 hour. * Brief post-only window after restart (2 min) before normal matching resumes. Cancels accepted. Post-only: only orders explicitly set with postOnly: true are accepted. Regular limit orders without the flag, market orders, and any taking liquidity will be rejected. Cancels for existing orders will still go through. [See POST /order API reference for the post-only flag.](https://docs.polymarket.com/api-reference/trade/post-a-new-order#body-post-only).

Jul 16, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Jul 16, 04:34:39 GMT+0
Completed - Maintenance has completed successfully..

Duration: 20 minutes

Affected Components: Trading API (CLOB)

Jul 13, 17:43:16 GMT+0
Identified - An internal service upgrade will be deployed. No downtime is expected and trading should continue as normal, but there may be brief instability during this window. Specifically, websockets might face some delayed responses for brief period. .

Jul 13, 18:00:01 GMT+0
Identified - Maintenance is now in progress.

Jul 13, 18:20:00 GMT+0
Completed - Maintenance has completed successfully.