Polymarket temporarily halted activity on its international trading platform on October 29 after identifying a security incident involving a third-party provider. The company said the issue had been fixed, reported it to law enforcement, and promised to make affected users whole. Its official status history marked the incident resolved at 19:05 UTC.
The recorded incident timeline
According to Polymarket’s official incident history, the platform entered cancel-only mode at 18:05 UTC, with relayer actions paused during an investigation. At 18:37 UTC, Polymarket identified a compromised third-party provider as the trigger and said the problem affecting Polymarket.com had been addressed.
At 18:55 UTC the company posted a monitoring update. The notice was marked resolved at 19:05 UTC. The status history documents the interruption; it does not by itself establish the number of affected accounts or the amount of any losses.
What Polymarket committed to users
The company said anyone impacted would be made whole and that relevant law enforcement had been contacted. It did not publish a complete compensation process, customer-level impact breakdown or named root-cause report in the cited notice.
Customers should therefore rely on authenticated communications and their account records when assessing whether they are affected. A general reimbursement promise is not the same as proof that all claims have been processed.
How third-party risk enters trading
Prediction-market services often rely on several providers for interfaces, data, authentication, analytics or transaction routing. A compromised provider may create a security exposure even when core matching or settlement software is not itself alleged to have been exploited.
The exact trust boundary involved in this event has not been established by Polymarket’s short status notice. A separate example of external-provider risk appears in BlockBriefing’s Bloom Trading security report, although the technical circumstances differ. Reporting should avoid inventing technical details about private keys, access tokens or attack methods.
What remains unanswered
The company has yet to provide a detailed public account of total customer exposure, the provider’s identity in its status record, and any long-term safeguards. A documented post-incident review would make the consequences clearer.
This article is based on the platform’s official incident history and distinguishes a confirmed, resolved interruption from broader allegations that still require evidence. For wider industry context, see BlockBriefing’s coverage of Kalshi, Polymarket and the NBA’s prediction-market partnerships.
Primary source and verification
Read the original announcement or data record for the underlying evidence. Figures and circumstances reflect the publication dates specified in this report and may change with subsequent disclosures.
BlockBriefing reports on digital assets for information, not as investment, legal or trading advice. Images created for this report are editorial illustrations, not documentation of the event.
