⚠️ Bugs & Issues
A major and prolonged CLOB latency degradation has affected Polymarket for over 12+ hours across Sept 21–22. Users reported order placement times of 400–5000ms avg, p95 up to 13,000ms, and p99 reaching 30 seconds at peak. Multiple users also reported
500 Internal Server Error: context deadline exceeded, 425 Too Early errors, failed limit orders, and cancel timeouts exceeding 5 seconds. The GET /positions (v2) endpoint was also falsely returning 429 errors for nearly 24 hours. skulldoom97 acknowledged the degradation and confirmed no CLOB restart is planned; suhailkakar stated a fix was being deployed. Separately, fill notifications on the user WebSocket stream were also delayed, which suhailkakar confirmed the team is aware of.Additional UI bugs reported: the Profit/Loss graph shows incorrect data for 1Y, YTD, and All-time views; the Favourites tab fails to display; and a general "Something went wrong" error blocks withdrawals and trades due to a failing relayer/session signing mechanism. exo_pm noted a today/tomorrow average price sort is being added, while alphabetical sort is not yet restored — the Search bar with a smoother API query is suggested as a workaround. A user also reported that the WebSocket server closes the entire connection when a subscribed market resolves, rather than just dropping that market's subscription.
⚡ Disputes
"Rebate Gate" — Users including sonderwrld, lochnload2718, and blunkoed continued pressing Polymarket over previously undisclosed 80%+ fee rebates given to certain participants. suhailkakar acknowledged the issue and promised an update "hopefully by this week," but users noted the delay has already stretched 8–10 weeks. blunkoed raised a broader trust concern: even if Polymarket claims the experiment stopped, there is no way to verify similar practices are not ongoing.
Market manipulation in 5-minute crypto markets — Multiple users reported ongoing wash trading and price manipulation in BTC 5-minute markets. sonderwrld alleged accounts honey-spot, potabmw, and stagbeetle were coordinating, with one manipulator reportedly making ~$40K in a single day. suhailkakar confirmed honey-spot was banned and stated the team is analyzing trading patterns for re-detection if they return on new accounts. He also confirmed the TWAP formula is controlled entirely by Chainlink and cannot be shared with Polymarket. Community members argued that account banning is largely ineffective without KYC, as manipulators can simply create new wallets. sonderwrld suggested blocking suspected accounts from converting pUSD as a harder deterrent.
📋 Clarifications
A recurring issue has been identified in weather markets, specifically for Tel Aviv and Manila (RPLL). User sanhwy documented that NOAA's WRH data pipeline experienced gaps on both September 20 and 21, with confirmed missing METAR observations during critical resolution windows. NOAA confirmed by email that "data appeared available on equipment but did not reach Synoptic — a communication error likely occurred." sanhwy noted that Polymarket's Aug 30 rule change narrowed the Weather Underground fallback to only trigger when NOAA data for the entire date is unavailable, creating a loophole where partial gaps — affecting specific observation hours — determine outcomes without triggering the fallback. sanhwy flagged that newly active wallets took large positions during these data-gap windows and called for an on-chain timing review, though no manipulation has been proven. The current market rules, as banisters noted, do not allow for resolution changes based on these gaps.