POLY (297 orders last 10 minutes) Last 1817ms Avg 3684.9ms Min 39ms Max 55092ms
POLY (297 orders last 10 minutes) Last 1817ms Avg 3684.9ms Min 39ms Max 55092ms
2026-06-10 · Polymarket · 69 条相关讨论
POLY (297 orders last 10 minutes) Last 1817ms Avg 3684.9ms Min 39ms Max 55092ms
POLY (297 orders last 10 minutes) Last 1817ms Avg 3684.9ms Min 39ms Max 55092ms
My placements (maker) are alright but cancellations are atrocious
My placements (maker) are alright but cancellations are atrocious
yes I've been telling them this is insane. They need to prioritize cancels or all the liquidity will dry up and also there is ZERO point in having the taker speedbump
yes I've been telling them this is insane. They need to prioritize cancels or all the liquidity will dry up and also there is ZERO point in having the taker speedbump
yeah my p95 cancellation is alarming in that its nearly a second
yeah my p95 cancellation is alarming in that its nearly a second
Rookie numbers. I got a 6000ms cancel
Rookie numbers. I got a 6000ms cancel
is polymarket latency really fucked up for everyone too?
is polymarket latency really fucked up for everyone too?
Update: - A change pushed yesterday should have also alleviated the frequency of the tick size issue, but the problem still remains. Prio1 is latency with the trading team focused first on latency patches. - The team is working on another latency patch. Various spam patterns putting pressure on the gateway. Yesterday's reduction in cancel batch size was to prevent that, but there are other patterns emergenging that they are working on. Will update on the ticksize as soon as the engineers get back to progressing on it
Update: - A change pushed yesterday should have also alleviated the frequency of the tick size issue, but the problem still remains. Prio1 is latency with the trading team focused first on latency patches. - The team is working on another latency patch. Various spam patterns putting pressure on the gateway. Yesterday's reduction in cancel batch size was to prevent that, but there are other patterns emergenging that they are working on. Will update on the ticksize as soon as the engineers get back to progressing on it
Orders are randomly disappearing. Not sure if it's a visual bug or if they're actually getting cancelled
Orders are randomly disappearing. Not sure if it's a visual bug or if they're actually getting cancelled
**Bug Report: Order cancellation state mismatch / stuck active order near market close** Hello Polymarket Team, I want to report a possible trading bug I experienced. **Issue:** During the final ~8 minutes of the market: **Market:** Bitcoin above $60,000 on June 9? I attempted to cancel my active limit sell order so I could update my position at a new price. The cancellation request returned this error: “Error cancelling order — the order is already canceled” But after refreshing the page multiple times, the same order was still visible as active/open. When I tried placing a new limit sell order, it failed with: “Limit Sell No failed — not enough balance/allowance. Balance is not enough → sum of active orders…” This looks like the order was canceled on one side but still counted as active/reserved by the system, causing my shares to remain locked. **Impact:** I was unable to cancel, modify, or create a new order during the final minutes before market resolution, which affected my ability to trade. I have attached screenshots showing: * Active order display * Cancel error message * New order failure due to locked balance Please investigate if this was an orderbook sync issue, backend state mismatch, or high-traffic related bug. (Sync problem at end time due to traffic i think)(browser MS edge, win 11 , ) Thank you.
**Bug Report: Order cancellation state mismatch / stuck active order near market close** Hello Polymarket Team, I want to report a possible trading bug I experienced. **Issue:** During the final ~8 minutes of the market: **Market:** Bitcoin above $60,000 on June 9? I attempted to cancel my active limit sell order so I could update my position at a new price. The cancellation request returned this error: “Error cancelling order — the order is already canceled” But after refreshing the page multiple times, the same order was still visible as active/open. When I tried placing a new limit sell order, it failed with: “Limit Sell No failed — not enough balance/allowance. Balance is not enough → sum of active orders…” This looks like the order was canceled on one side but still counted as active/reserved by the system, causing my shares to remain locked. **Impact:** I was unable to cancel, modify, or create a new order during the final minutes before market resolution, which affected my ability to trade. I have attached screenshots showing: * Active order display * Cancel error message * New order failure due to locked balance Please investigate if this was an orderbook sync issue, backend state mismatch, or high-traffic related bug. (Sync problem at end time due to traffic i think)(browser MS edge, win 11 , ) Thank you.
Hey Mustafa Are you guys aware cancels are broken? Like on any decent BTC moves, cancels just aren't going through. Quite a few of us either unable to quote, or just simply scratching for rebates because cancels make making actual money hard rn Meanwhile, days after the taker delay bypass fix, bonereaper is having his best few days ever.... With mostly taker volume......
Hey Mustafa Are you guys aware cancels are broken? Like on any decent BTC moves, cancels just aren't going through. Quite a few of us either unable to quote, or just simply scratching for rebates because cancels make making actual money hard rn Meanwhile, days after the taker delay bypass fix, bonereaper is having his best few days ever.... With mostly taker volume......
The latency today is terrible. MMs have pulled their liquidity.
The latency today is terrible. MMs have pulled their liquidity.
observing the same issue as well. seems like the orders backend is behaving inconsistently.
observing the same issue as well. seems like the orders backend is behaving inconsistently.
Well, yes, but also the fact that this effect seems more concentrated at times when it's more important........
Well, yes, but also the fact that this effect seems more concentrated at times when it's more important........
I'm actually checking this RIGHT NOW!!!! ITS BROKEN!!!!!
I'm actually checking this RIGHT NOW!!!! ITS BROKEN!!!!!
about 35% of my orders are taken before i can cancel them
about 35% of my orders are taken before i can cancel them
tick size problem still here,not even alleviated latency is not your excuse,it's been so many days for this problem
tick size problem still here,not even alleviated latency is not your excuse,it's been so many days for this problem
Will the upcoming CLOB maintenance fix the tick size bug?
Will the upcoming CLOB maintenance fix the tick size bug?
Yes
Yes
tick size issue not fixed
tick size issue not fixed
“price 0.999 breaks minimum tick size rule 0.01”
“price 0.999 breaks minimum tick size rule 0.01”