🔥 News & Announcements
0x3577 noted that weather market rules need improvement, stating "we are having too many loopholes who are making people lose money from wrong results." They expect the data source to change as NWS is "failing every week," and hinted a rule update is coming soon.
⚠️ Bugs & Issues
A significant CLOB degradation occurred during the day. The order status API went down, causing bots to incorrectly treat filled orders as cancelled — orders were appearing, disappearing, and reappearing in a loop. walem confirmed the order status API was down but noted it did not immediately affect order placement, adding that "the last few times CLOB went down shortly thereafter." polywatchdog confirmed: "CLOB is degraded. Cancel and orders endpoints not consistent." chickenwing_14999 pinged staff noting the Trades API was broken again.
artex6666 raised serious complaints about cancel latency: averaging 250ms on P90 cancels, and getting fills after cancel responses — requesting the taker delay be restored to 500ms or a proper FIFO system be implemented. The issue was described as "catastrophic" over the last two days.
A separate recurring bug causes orders to be filled after cancellation (sometimes 30+ minutes later), reported by artex6666 and berth6833. honeybear0x noted this bug has been unfixed "for weeks."
whaleeddy reported their bot address was banned while trading BTC 5-minute markets, receiving HTTP 400 errors. artex6666 suggested contacting support.
A user (bullbear_95834) noted the GET order endpoint started taking 4–5 seconds to return order details after placement, a delay not present before.
Other reported issues: positions not showing after purchase (silvaselva), inability to open the Venezuela/Israel market (jimmybuzzard), and the stats page disappearing (nz377).
brenmaelen publicly called out staff for ignoring DMs regarding $6,000 lost due to an outage, with suhailkakar responding to look into it.
📋 Clarifications
Crypto Up/Down settlement logic: artex6666 clarified (from personal code and observation) that Polymarket uses the Chainlink report with the latest
validFromTimestamp ≤ T (expiration), not the first message received after T. A message arriving after T can still be ignored if its validFromTimestamp predates expiration. artex6666 noted this is based on their own code/observations rather than official documentation.Taker delays for sports markets: berth6833 shared that the taker delay is 1 second across most sports markets, but 0 seconds for MLB and NBA.
API rate limits: blunkoed clarified that rate limit tiers are automatically updated based on trading volume. CLOB rate limits are per wallet; Cloudflare limits are per IP.
⚡ Disputes
Panama City weather market — 32°C vs 31°C: A dispute is ongoing over whether Panama's temperature reached 32°C. sakula1 argues that Panama's civil aviation authority website showed a METAR reading of 32°C for over an hour before being corrected, and that some bots traded on this early reading. modali1 counters that the NWS (the official resolution source) only ever showed 31°C, and that the order book was being cleared 15–30 minutes before the official METAR timestamp — suggesting foreknowledge or a data anomaly rather than a legitimate 32°C reading. The situation is complicated by late METAR issuance (sometimes 35+ minutes past the hour) and alleged DDoS-like bot traffic hitting the Panama aviation site around METAR release times. No official resolution has been announced. user_v123 noted a 33°C SPECI report also appeared later.