polymarket.health
Lesson 12·Regulation & Risk·8 min read

Polymarket Outage History: Notable Incidents & Lessons

Polymarket has been remarkably reliable, but its biggest incidents have come at the worst possible times.

Polymarket maintains 99.9%+ uptime in the aggregate, but the incidents that have happened — especially during the 2024 US election and 2025 Fed cycles — illustrate the platform's structural weak points. Because Polymarket is non-custodial, no incident has ever resulted in lost user funds. Every incident has, however, meant lost trading windows during exactly the moments traders most wanted to act.

Election night 2024

On the evening of November 5, 2024, Polymarket experienced multiple degradations as US election results came in. Order book latency spiked, the front-end loaded slowly for many users, and some reported failed wallet connections at critical moments. The platform stayed online technically, but its largest day of volume was also its most stressed. Users on the embedded wallet saw longer sign-in times; users on external wallets got RPC errors from Polygon providers.

Root cause was a combination of front-end request volume overwhelming autoscaling and Polygon RPC providers throttling under aggregate load. Polymarket's public post-mortem cited both. Volume peaked at over $50 million in a single hour.

RPC provider incidents

Several Polymarket slowdowns have been caused by Polygon RPC degradation upstream — Alchemy, Infura, or QuickNode having issues simultaneously affects every Polygon front-end, not just Polymarket. These incidents are often resolved by the RPC providers within minutes but can stretch to hours during Ethereum-level congestion. If everything you see is red at once, always check status.polygon.technology before assuming Polymarket is broken.

UMA resolution controversies

Several markets have been disputed at the UMA oracle stage. The Ukraine/Zelensky suit market in early 2025 is the most cited example — a market phrased ambiguously about whether Zelensky had "worn a suit" at a specific event triggered a multi-day dispute cycle. These aren't outages in the uptime sense, but they're failures of the platform's information layer that matter to users who trusted the resolution.

The lesson: read the resolution criteria carefully before trading, and prefer markets with unambiguous outcome sources ("Federal Reserve press release") over subjective ones ("was the event notable?").

Wallet and onboarding issues

The embedded wallet system has had periodic sign-in issues, usually tied to auth-provider outages (Magic, Privy) or SMS delivery failures. External wallet users have had WalletConnect relay outages that made signing impossible. These issues typically affect a subset of users at a time and are resolved within an hour.

Common failure signatures

The most common Polymarket failure signatures for users are: transactions pending indefinitely (RPC issue), positions not showing (front-end / indexing lag), inability to sign a trade (wallet issue), and markets showing but orders not filling (matching engine backlog). Each has a different root cause and a different workaround.

For pending transactions, waiting is usually enough — the transaction is on-chain and will confirm eventually. For missing positions, refresh and check your wallet address on Polygonscan directly. For wallet issues, try a different browser or reconnect via WalletConnect.

Worked example: election-night defensive playbook

If you plan to trade election night, do the following in advance: (1) deposit funds and confirm the balance shows, (2) place any core positions before US market close so you're not fighting congestion, (3) keep 5–10 MATIC on hand for gas, (4) note your wallet address so you can check positions on Polygonscan if the UI fails, and (5) have a fallback exchange (Kalshi, Robinhood) ready if you're in a jurisdiction where both work.

Protecting yourself

If you're trading on a high-volume night, place orders early, use limit orders rather than market orders, keep some MATIC for gas, and have a wallet you can sign with off-platform. When the front-end fails, your positions are still safe on-chain — Polymarket cannot lose or seize your USDC. The worst realistic outcome is missing an entry or exit, not losing principal.

When to worry

A single minor incident is normal. Multiple incidents in a week on the same component is a pattern worth watching. If UMA disputes are recurring on markets you care about, wait for resolution before adding more capital in that category. If the front-end is down for hours and Polygon is fine, that's an internal Polymarket engineering incident and worth checking Twitter for updates.

Frequently asked

Has Polymarket ever lost user funds?
No. Because Polymarket is non-custodial, USDC stays in user wallets or on-chain market contracts. There has never been an exchange-style theft of customer balances. The worst realistic outcome from an outage is missing a trade, not losing principal.
What was the biggest Polymarket outage?
Election night 2024 was the most consequential — not a full outage but sustained degradation during the platform's highest-volume window ever. Users reported slow loads, failed wallet connections, and delayed order fills. The platform stayed online but under significant strain.
Are Polymarket outages usually its fault or Polygon's?
It's roughly split. When Polygon RPC providers degrade, every Polygon app suffers simultaneously — that's an upstream issue. When only Polymarket is affected, it's an internal engineering problem. The status page above tries to separate the two.
What happens to my open orders during an outage?
Open limit orders sit in Polymarket's off-chain order book. If the matching engine is down, they don't match. If the front-end is down but matching still runs, they can still fill. Your positions and USDC are on-chain and unaffected either way.
How do I check Polymarket status independently?
Use an independent monitor like polymarket.health, check the Polymarket Twitter account, and cross-reference with status.polygon.technology if you suspect a Polygon-wide issue. Discord and Reddit report user-visible issues fastest.
Can I get compensation for lost trading opportunity?
No. Polymarket's terms disclaim any liability for missed trades or opportunity cost during outages. Because it's non-custodial and unregulated in the US, there's no consumer-protection body to appeal to.
What's the best time to trade to avoid outages?
Ordinary trading hours (US morning through evening) are the smoothest. Peak-load windows — election night, Fed announcement moments, major sports finals — are where outages cluster. If you can front-run those windows with pre-placed limit orders, you avoid most stress.
Does Polymarket publish post-mortems?
Sometimes, on major incidents. Post-mortems are typically posted on the Polymarket blog or Twitter within a few days of a significant event. They're useful for understanding root cause and forward-looking mitigations.

The .health network

Independent status monitors for the tools and markets we track.

AI models

AI platforms

Dev platforms

Prediction markets