🔥 News & Announcements
The Polymarket team is actively investigating weather data source issues. ak504111 confirmed internal discussions are underway about potentially reverting to Wunderground as a temporary fix, while a longer-term solution is being developed. The team also confirmed they are looking into hourly temperature markets similar to Kalshi's new offering.
maskache07 proposed reverting to Wunderground immediately and forming a small private working group of experienced traders to design a permanent solution before any new rules are pushed.
⚠️ Bugs & Issues
Critical trade routing bug: olegs_13 reported losing $3,000 after buying shares in one market only to have the order execute in a completely different market. This has allegedly happened 3–4 times.
Redemption failure: jcsnc99 reported ~$1,577 in resolved winning positions stuck unredeemed since Sep 14 on one wallet, with "Claim all" reverting mid-process when mixing negRisk and standard markets in a batch.
Share balance not recognized: A user in #climate reported being unable to exit a ~$1,600 position, with the UI returning "Not enough shares" despite confirmed holdings. ak504111 escalated and requested a screen recording.
Weather data outages: weather.gov (via Synopticdata) has been experiencing repeated data gaps, affecting multiple city markets including Lucknow, Manila, Cape Town, and Panama. The Panama market saw no 15:00 temperature reading, with the outage confirmed on both aviationweather and Wunderground as well.
X Tracker undercounting: sabari_stocks flagged that the White House X post tracker missed several posts from Sunday's "Summer 250 Photo Dump," reporting 204 original posts for the week of Sep 15–22 and asking for a recount before resolution.
CLOB API false-positive ban: polywatchdog reported receiving a 400 "address banned" error from the CLOB API despite respecting all rate limits, and believes it is a false positive. tsmultra asked for a DM with the proxy address.
Order placement latency: Multiple users reported laggy order placement (~10 seconds). skulldoom97 stated latencies should be better, and chickenwing_14999 confirmed improvements on their end, though artex6666 reported severe latency spikes again later in the day.
WebSocket delivery skew: oleh931816 documented WS market update delays of up to 686ms (p99 >100ms) on AWS eu-west-2, with individual markets stalling while others on the same connection continue normally. 830lincoln confirmed experiencing the same, with delays up to 10+ seconds, noting the issue returned after being fixed about a year ago.
CLOB signature latency disparity: th0rped0 measured that accounts created after May 4, 2026 are locked into the deposit wallet flow (type 3 signatures), which is consistently 6–8ms slower than type 2, and ~10ms slower than legacy type 1 accounts. blunkoed suggested waiting for CLOB 2.0, expected end of year.
📋 Clarifications
Regarding the weather data source debate, notaforecaster_32454 clarified that weather.gov pulls from the Synopticdata API, while Wunderground uses weather.com's API, and suggested
https://tgftp.nws.noaa.gov/ as the closest raw source. However, user_v123 noted tgftp only retains 24 hours of history and does not include SPECIs in cycle files, making dispute resolution problematic. The aviationweather.gov API was raised as an alternative with archiving and SPECI support. user_v123 also suggested considering a switch to Celsius to avoid temperature conversion rounding issues inherent to Fahrenheit/METAR T-group parsing.ak504111 clarified that the rules already allow fallback to Wunderground when WRH data is fully missing, and indicated the team will add clarity on what constitutes "missing data" to potentially cover partial outages as well.