🔥 News & Announcements
A significant NOAA/weather.gov data outage on Sep 20 caused multi-hour gaps in temperature data for numerous international stations (RPLL, ZBAA, ZGGG, LEMD, LTAC, EPWA, ZSQD, WSSS and others), with the daily temperature extreme falling inside the gap for several of them. The outage appears to be a systemic ingestion failure in the WRH Time Series Viewer rather than a total website outage — NOAA/NWS confirmed the missing observations exist in other official NWS systems and in the 04Z METAR cycle archive. A user flagged wallet
0x13f995ad154da3e078ac2a1dd923bf2b265dd352 for unusual trading activity timed around when the data gap became publicly visible; no wrongdoing has been proven. sanhwy noted that Burwick Law is publicly investigating potential claims from Polymarket traders involving disputed market resolutions.sanhwy called on Polymarket to restore the older, clearer rule wording: "If NOAA data is unavailable or missing for the observation period, Weather Underground will be used as the secondary resolution source" — arguing the current wording does not cover partial data gaps. As of early Sep 21, the same METAR feed outage appears to be recurring on weather.gov.
A separate incident: a bot trader (gs7422) reported a loss after Polymarket's own embedded native feed prematurely marked the Vitória SC vs. Moreirense FC match as Full-Time with a stale 0-1 score, before a late equalizer made it 1-1. The bot bought "No draw" based on that feed and lost. phoenyx69 pointed out the feed's own disclaimer states it "should not be used as the basis for any trading decision," and gs7422 acknowledged he had not seen that disclaimer.
⚠️ Bugs & Issues
Multiple technical problems were reported across Sep 20–21:
• PnL charts: eljefe_30457 reported charts only updating every ~8 hours instead of hourly, with incorrect historical data.
• CLOB "not enough balance" bug: honeybear0x reported that the CLOB treats already-settled and redeemed positions as still matched, blocking use of the full wallet balance for new orders. GitHub issues filed at py-clob-client-v2 #112 and py-clob-client #342. No fix confirmed yet.
• Order maker queue full: berth6833 reported hitting the order maker queue capacity during simultaneous NFL markets, noting that BUY and SELL appear to have separate queues ("order queue full for maker <wallet>-BUY").
• API latency and errors: multiple users (bzhksrg, toto6328, superair233, satatardy, chrisv3537) reported intermittent "Unauthorized/Invalid api key" errors, doubled latency, 429 rate-limit errors on GET positions, and frequent request exceptions.
• Limit orders not executing: adrya407 reported limit orders from the UI neither filling nor appearing as resting orders.
• Cloudflare WAF issue: cylex_2 reported a WAF block also affecting the Gamma API, likely misreading
0x... IDs as SQL-style hex literals. exo_pm (team) confirmed they will check the WAF rule.• LP rewards not showing: audunlkleveland reported LP rewards not displaying.
• Portfolio sorting removed: nicoco_89 requested the return of alphabetical and "resolving soonest" sorting in portfolios.
📋 Clarifications
The core unresolved question for Sep 20 weather markets is whether a partial NOAA/WRH data gap — where some rows exist but the daily extreme falls in the missing interval — triggers the Weather Underground fallback rule. The current rule only switches to WU if all NOAA data for the observation date is unavailable by 11:59 PM ET the following day. modali1 and lightningfella consistently argued that as long as any NOAA data point exists for the day, NOAA data is used exclusively, citing prior team clarifications. sanhwy countered that a known ingestion failure in the WRH viewer — where the observation already existed in NOAA's own systems — should not be treated as the authoritative NOAA reading for that interval, and requested an official Polymarket team response before resolution.
hermie_28217_08100 clarified the Chicago (KMDW) Polymarket US market: the 72°F high was recorded at 5: