Polymarket Users Hit Redemption and Trading Infrastructure Problems(September 2026)

For a prediction-market trader, the moment after a winning position should be simple. The market settles, the position can be redeemed and the money becomes available.

On Thursday, September 17, 2026, that process broke for some Polymarket users.

Multiple traders reported being unable to redeem winning positions for more than 12 hours before the issue was resolved at about 11:20 UTC. At the same time, developers reported problems with the platform's new API, liquidity-reward calculations and the central limit order book.

The problems come as Polymarket prepares to offer zero fees on NFL and college football markets this weekend and continues to face questions from its trading community over preferential fee rebates.

Winning positions were temporarily stuck

The most immediate problem involved redemptions.

Users reported that they could see winning positions but could not convert them into redeemable funds for more than half a day.

A community member, ak504111, said the problem was under investigation before users later reported that redemptions were working again at around 11:20 UTC.

The incident highlights an important distinction in prediction markets.

A market settling correctly is one thing. Being able to access the resulting funds is another.

For traders who use prediction markets actively, the second step is not a minor interface feature. Capital can remain locked until a winning position is successfully redeemed.

The new API still lacks a redemption endpoint

The redemption problem is also connected to a broader change taking place behind Polymarket's interface.

Developers have been moving toward a new version of the platform's data API. During that transition, 0xdanzu confirmed that the redemption endpoint had not yet been implemented in Data API v2.

The developer said the endpoint is being reintroduced, although there was no firm estimated completion time.

That creates an awkward gap for builders.

A trader using the Polymarket website may eventually see a working redemption function, while developers building their own applications still need to wait for the corresponding API functionality.

For an ecosystem increasingly built around bots, dashboards and automated trading tools, API coverage can be just as important as the website itself.

Liquidity rewards are also raising questions

Another unresolved complaint involves liquidity-provider rewards.

adam22234 reported receiving zero rewards across multiple markets despite believing the required conditions had been met.

There was no confirmed resolution to that complaint in the community discussion.

Reward systems are particularly sensitive because traders make decisions based on expected returns. If a trader supplies liquidity because a market appears eligible for rewards, uncertainty over whether those rewards will actually be credited can change the economics of the trade.

It also makes troubleshooting harder.

A user may not know whether the problem is the market, the reward calculation, the wallet or the platform's accounting.

Traders are seeing problems with the order book

The central limit order book, or CLOB, has generated several other complaints.

miraacook reported intermittent context deadline exceeded 5552ms errors when submitting fill-and-kill orders.

berth6833 described the problem as a known intermittent issue.

A separate trader, sharkhunterr, reported stale odds appearing through the CLOB while the main Polymarket interface continued to update normally.

That difference matters for automated traders.

A human looking at the website may see a current price while a program consuming order-book data could potentially be working with older information.

The result is a mismatch between what the trader sees and what the trading system receives.

Polymarket is changing fees ahead of football weekend

Against that backdrop, Polymarket is also making a major change to trading costs.

The platform is offering zero fees on NFL and college football markets for the Sept. 19-20 weekend, according to community announcements.

The promotion is expected to cover a large number of sports markets during one of the busiest periods of the U.S. football calendar.

There is some confusion, however, over how the promotion is being represented across Polymarket's technical ecosystem.

hipp74 noted that taker fees were still appearing on third-party sites. That raised the possibility that the promotion was being handled through rebates or another mechanism that had not yet been reflected in the Gamma API.

The distinction matters to developers.

If the website displays zero fees but an API still reports the ordinary fee structure, applications built on top of the API may calculate trading costs incorrectly.

Crypto traders are also getting a faster execution window

Polymarket has separately reduced the taker delay on crypto markets.

The delay has fallen from 250 milliseconds to 150 milliseconds, with the change taking effect Aug. 17.

An earlier changelog referenced a 50-millisecond figure, but blunkoed later clarified that the actual setting was 150 milliseconds.

For ordinary users, a difference measured in milliseconds can be difficult to notice.

For automated traders competing for rapidly changing prices, it can be significant.

The delay is part of the mechanics surrounding taker orders and gives the platform another lever for balancing speed, liquidity and market fairness.

That makes accurate documentation important. A 50-millisecond setting and a 150-millisecond setting represent very different trading conditions for an automated strategy.

Builders are being moved into a new channel

Polymarket is also reorganizing how developers communicate.

displaysonx announced that builder discussions are being consolidated into a new channel, while the old channel will remain available as a read-only archive.

The move comes as the platform's developer ecosystem becomes more complicated, with traders using APIs, automated execution systems, data feeds and third-party interfaces alongside the main website.

The communication structure matters because many of the issues being reported are technical rather than purely trading-related.

A missing API endpoint, an outdated order book or an incorrect fee value can affect developers long before an ordinary trader notices a problem.

The CEO says Polymarket is working to unify its products

Polymarket CEO Shayne Coplan has also acknowledged concerns about the performance of the platform's on-chain products.

In a post on X, Coplan said the company was working "behind the scenes to unify the products."

The statement prompted a skeptical response from some members of the developer community, who argued that complaints about the platform had been circulating for months.

That reaction reflects a wider tension inside Polymarket's ecosystem.

The company has expanded from a simple prediction-market interface into a collection of trading infrastructure, APIs, liquidity programs and developer tools.

Each additional layer creates another place where the experience can diverge.

The rebate controversy has not gone away

The most politically sensitive issue inside the developer community remains the dispute over preferential taker rebates.

Community members continue to allege that selected market makers have received rebates as high as 80 percent.

Several regular participants, including lochnload2718, blunkoed and tehnoobkiddo, have been adding disclaimers to their messages warning readers about the alleged arrangement.

The important qualification is that these are community claims. The existence, scope and current status of any private rebate arrangements should not be treated as independently established simply because traders are discussing them.

The controversy has nevertheless continued.

richlb_predict said the 80 percent rebate had reportedly been paused.

blunkoed questioned whether the arrangement had actually ended or had instead been moved off-chain.

Those questions have kept the issue alive even as Polymarket promotes new fee reductions for football markets.

The distinction between a public fee promotion and a private rebate arrangement is central to the debate.

A public promotion tells every trader what the terms are.

A selective rebate can create different trading economics for different participants.

That is why the community continues to ask for clarity about eligibility and disclosure.

Traders are also questioning the value of co-location

Another technical discussion concerns co-location and latency.

blunkoed argued that completing KYC for co-location does not necessarily provide the expected speed advantage because orders still pass through Cloudflare and a separate data center.

An additional wallet check can add further latency, according to the discussion.

Some traders have also claimed that Dublin can perform as well as, or better than, the co-location setup they expected to use.

The reported KYC waiting times vary dramatically, from roughly one week to as long as six months.

Those figures are community reports rather than an official Polymarket service-level guarantee.

Still, the complaints reveal what sophisticated traders are increasingly asking from prediction-market infrastructure.

It is no longer enough to have a fast exchange.

Traders want to know exactly where orders travel, how long each step takes and whether paying for a specialized setup produces a measurable advantage.

The platform is becoming more complicated as it grows

The problems reported this week do not all point to the same underlying cause.

A redemption outage is different from a missing API endpoint. A stale order book is different from a fee promotion. Co-location latency is different again.

Yet they share one feature.

Polymarket is increasingly being used as a piece of financial infrastructure rather than simply as a website where people buy Yes or No positions.

That raises the standard users apply to it.

They expect the website, APIs, order books, rewards, fee schedules and settlement systems to tell the same story.

When they do not, even a small discrepancy can become a much larger trust problem.

The redemption issue was eventually resolved. The API endpoint is reportedly being restored. The football promotion offers traders a clear reduction in costs.

The harder questions are the ones without a quick fix: how the platform communicates changes, how rewards are calculated, how execution infrastructure is documented and whether different classes of traders receive materially different economics.

For a prediction market trying to build a larger financial ecosystem, those details are becoming the story.