Polymarket Outage History: A Sourced Incident Evidence Notebook

This page is a static, curated sample of incidents published on Polymarket's official status page, reviewed on October 26, 2026. It is not a complete history, it is not our own uptime measurement, and it says nothing about Polymarket's current status. For the full record, use the official history pages; for live status, use the official status page. Our homepage checks only test whether services are reachable from your browser; they are not official operational status.

All times below are in UTC unless stated otherwise. Where the official page shows a duration, we reproduce it as operator-reported rather than computing our own.

In-depth record: “Issues with delayed open order read responses”

Source: the official incident page, fetched October 26, 2026. Official title: “Issues with delayed open order read responses.” Date: August 31, 2026 (UTC).

Published updates, as reported: 00:40 UTC — investigating. 01:06 UTC — identified; the update describes a cancel-only mode while the issue was monitored. 01:12 UTC — resolved.

Affected component, as reported: Predictions — Trading API (CLOB). Reported impact: major outage from 00:40 to 01:06 UTC, partial outage from 01:06 to 01:12 UTC.

Duration: the page headline states 31 minutes (operator-reported). The rendered clock times span 00:40 to 01:12; we do not substitute our own duration for the published figure.

What we do not infer: the title describes delayed responses when reading open orders. It does not by itself tell us the root cause, whether any user lost money, or whether any particular order filled, failed or settled.

Annotated source timeline

Each row is a published status update or record, with our annotation of what it does and does not establish.

What the operator says vs. what you can infer

A status record is evidence from the operator about the operator's own scope. This matrix separates the layers.

Why cancel-only is not “all healthy”

Cancel-only is a mode the operator describes as permitting cancellations while restricting new orders. It does not guarantee that each individual cancel was accepted. A page that loads, or an order list that reads correctly, does not mean new orders are being accepted. Treat a cancel-only update as a specific restriction, and wait for a resolution update before assuming normal trading.

Evidence-capture worksheet

Keep these notes privately if you think an incident affected you. Do not post identifiers publicly.

1. Time you noticed the problem, with timezone. 2. Which action: page load, sign-in, order read, order placement, cancel, withdrawal. 3. Exact status text or sanitized error (remove keys, signatures and wallet details). 4. Any order hash or transaction hash you already have. 5. The official incident link and update times that overlap your window. 6. What your official order and trade history shows after resolution.

If records are missing or ambiguous, contact official Polymarket support. Missing records alone are not proof of failure, and resubmitting while an original order is pending can create duplicates.

How to navigate the official sources

Start with the official history pages, open each incident, and read every update — not just the headline. Polymarket also documents a public status API; we link to it for reference but do not poll it from this page.

This page records nothing about your account, does not check settlement, and makes no promise about current or future availability.