Polymarket trading was degraded on May 29 after an issue affected the platform’s CLOB API, temporarily disrupting one of the main trading layers behind the prediction-market platform.
The developer team said it had identified the cause and was deploying a fix, while the status page showed the CLOB API under maintenance. The incident was first marked as identified at 12:47 UTC, with a CLOB restart scheduled at 13:10 UTC to roll out the fix.
The issue did not appear to be a full platform outage. Polymarket’s website, Markets API, Polygon RPC, user authentication, and Sports API were listed as operational during the incident window. That distinction matters because users may still be able to view markets, balances, pricing data, or account pages while trading itself remains degraded.
Why The CLOB Matters
Polymarket’s central limit order book is the part of the system that handles order placement and matching. The platform uses a hybrid model where orders are created and matched offchain, while completed trades settle onchain through smart contracts on Polygon.
That setup gives Polymarket faster trading performance than a fully onchain order book, but it also means the CLOB is a critical availability layer. If the CLOB API has issues, traders may face failed orders, delayed submissions, temporary matching problems, restricted execution, or degraded market-making activity even if the broader website remains reachable.
For a prediction market, that can matter quickly. Polymarket prices often move around breaking news, sports events, political developments, market data, regulatory decisions, and crypto volatility. When trading access is degraded during a live event, users can lose the ability to enter, exit, hedge, or update positions at the moment liquidity matters most.
Timing Is Sensitive After Perps Beta Launch
The incident comes shortly after Polymarket Perps went live in beta for select users, expanding the platform beyond traditional YES/NO outcome shares and into long-short trading. That rollout makes trading infrastructure more important because perps-style products depend on continuous access, clean execution, and reliable risk controls.
Polymarket has also been dealing with access and compliance questions tied to the perps rollout. The platform recently pushed back against claims of a broader identity-check shift, saying KYC is limited to selected beta users and not being added to existing parts of polymarket.com.
A short CLOB disruption does not carry the same meaning as a failed market resolution or blockchain halt, but it still hits the same user-facing problem: prediction markets need to stay tradable when prices are changing. That becomes even more important as Polymarket moves into higher-frequency products and more active trading use cases.
Crypto Infrastructure Faces A Live Reliability Check
The Polymarket incident also lands on a day when infrastructure reliability is already under scrutiny across crypto. Sui recovered after a separate two-hour mainnet stall temporarily halted block production, showing how quickly trading, settlement, and application access can become the market’s main concern when systems pause. However, the Sui network stalled again today.
Polymarket’s issue is different because it sits at the trading-infrastructure layer rather than the base-chain consensus layer. Still, both incidents point to the same pressure on crypto platforms: uptime is now part of the product, especially when users are trading live events, perps, tokens, or app-level markets.
The immediate focus is the CLOB restart, return to normal matching, and confirmation that order placement, cancellations, market making, and API access are stable after the fix. If trading resumes cleanly, the incident may remain a short operational disruption. If the fix leaves lingering order-book or execution problems, Polymarket will face tougher questions just as its perps beta brings more attention to the platform’s trading stack.
Be the first to comment