Polymarket restores international trading after one-hour third-party security interruption

Prediction-market operator Polymarket temporarily put its international exchange in cancel-only mode on 29 October after identifying a security incident involving a third-party provider. The company's status history gives a start time of 18:05 UTC and records resolution at 19:05 UTC, a one-hour interruption to normal trading actions.[1]

The chronology is more informative than describing the episode as a generic outage. At 18:05, Polymarket said the exchange was in cancel-only mode with relayer actions paused. At 18:37, it said the affected third-party provider had been compromised, that the specific issue had been identified and fixed and that the matter had been referred to relevant law enforcement. At 18:55, it indicated trading would shortly resume; at 19:05, it marked the incident resolved.[1]

Cancel-only is a restrictive trading state, not full operation. It is intended to allow cancellation while preventing normal placement or modification of risk-increasing positions, although actual functionality depends on the platform's system design. For an existing holder, losing the ability to open or close trades for an hour can change exposure even without an outright loss of account access.[1]

Polymarket said anyone impacted would be made whole. That is a compensation commitment from the company, not evidence that all relevant claims have already been paid. Its status log did not provide a verified count of customers, an independently audited sum of losses or a final technical forensic report.[1]

The third-party dependency problem

The official incident report does not name the vendor. News organisations, including Associated Press, reported a possible connection to security problems involving monitoring provider DebugBear, but that identification should remain attributed to outside reporting rather than represented as a finding in Polymarket's own status log. Similarly, early user reports and blockchain estimates of losses need reconciliation before they can be presented as final verified figures.[1]

Prediction exchanges depend on software beyond their matching or order-management engines, including the website, identity services, market data and other client-side components. A compromise affecting an external dependency may therefore require defensive changes to trading availability, even where the operator has not publicly disclosed a compromise of its core exchange engine.[1]

Polymarket lists separate scheduled maintenance earlier on 29 October, distinct from the later security incident. The published incident timeline supports a one-hour restriction on normal trading, while the financial impact and fulfilment of the reimbursement promise remain unquantified.[1]

Report an error or submit an update