Skip to main content
Polymarket logo

Is Polymarket Down?

No — Polymarket is up

Reachable from all 8 checked regions

Average response time: 120ms

Last checked · checks run every 6 hours

Official status page: https://status.polymarket.com

Polymarket uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
204ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 17 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

17-day clean streak
Sep 12: no data
Sep 13: no data
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: 100.00% uptime, 16 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 31 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 48 checks
Oct 1: 100.00% uptime, 31 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Sep 12 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

arn
75ms
DNS 0ms TCP 2ms TLS 6ms TTFB 50ms
cdg
98ms
DNS 6ms TCP 2ms TLS 7ms TTFB 78ms
dfw
214ms
DNS 83ms TCP 1ms TLS 6ms TTFB 189ms
ewr
105ms
DNS 14ms TCP 1ms TLS 8ms TTFB 86ms
fra
122ms
DNS 7ms TCP 2ms TLS 8ms TTFB 103ms
gru
111ms
DNS 13ms TCP 2ms TLS 9ms TTFB 83ms
iad
120ms
DNS 14ms TCP 1ms TLS 9ms TTFB 98ms
jnb
122ms
DNS 7ms TCP 1ms TLS 9ms TTFB 99ms

What Polymarket does

Polymarket is a prediction market: users trade shares in the outcomes of real-world events with each other, and prices reflect the market's view of how likely each outcome is. Orders are matched off-chain by Polymarket's order book, the CLOB, and settled on the Polygon blockchain in pUSD. The platform is non-custodial, so funds and positions sit in the user's own wallet. It also runs a Perpetuals product.

What an outage looks like

Most incidents are trading problems rather than a dead website. The status page labels them Trading Degraded: order placement, cancels or fills stop, or open orders read back late. During recovery Polymarket often switches to cancel-only mode, where new orders are rejected with a message that trading is currently cancel-only while cancels still work. Slow Polygon block production, as on September 19, 2026, also delays trades.

What to do about it

Check status.polymarket.com and read the Predictions Trading API (CLOB) and On-chain Settlement (Polygon RPC) rows, not only the Web App row. In cancel-only mode you can still cancel resting orders; new orders wait until trading resumes. Planned matching engine restarts are announced ahead of time in Polymarket's Telegram and Discord trading API channels. Funds and positions are held on-chain in your wallet, not on the website.

Is it down for everyone, or just you?

If this page says Polymarket is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

C
Coinbase
O
OpenSea
D
DraftKings
Underdog
Underdog

Polymarket outage FAQ

What is cancel-only mode on Polymarket?
Cancel-only mode is a restricted trading state in which new orders are rejected but cancel requests still go through. Polymarket's documentation says order endpoints return a 503 error saying trading is currently cancel-only. The status page shows Polymarket used it repeatedly during the August 30 to September 1 and September 19, 2026 incidents, sometimes announcing a 15-minute cancel-only window before normal trading resumed.
What happens to my open orders when Polymarket trading is paused?
Polymarket's docs say a resting limit order stays open until another order matches it, you cancel it, or a Good Till Date order expires. In cancel-only mode you can still withdraw orders. API traders who have turned on heartbeats are the exception: if the order book gets no valid heartbeat for 10 seconds, it cancels every open order for those API credentials. After a matching engine restart, two minutes of post-only trading follow.
Does Polymarket hold my funds during an outage?
No. Polymarket's documentation describes the platform as non-custodial: assets are held in your own wallet, secured by your private key, and trades and positions are recorded on-chain. The docs also say the exchange operator can match orders but cannot execute trades users did not authorize. Settlement is atomic, so a matched trade either completes in full on Polygon or does not happen at all.
Why is Polymarket trading down when the website loads?
Because the website and the order book are separate systems with separate rows on status.polymarket.com. Polymarket Web App and Account Access and Authentication sit apart from the Predictions group, which holds the Trading API (CLOB), both websockets, Markets and Position Data, and On-chain Settlement (Polygon RPC). Most recent incidents were Trading Degraded on the Predictions side, and the Web App row has logged far less downtime.
How long do Polymarket outages usually last?
Recent trading incidents have lasted from under 20 minutes to about four hours. On the status page, the September 23, 2026 Trading Degraded incident was resolved in about 17 minutes, and September 19 brought two, of about two hours and about 40 minutes. The longest recent one, on August 31, paused trading for over four hours while a fix for delayed open order reads was applied.

How we measure this

  • We request Polymarket's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Polymarket publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Polymarket goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required