2026-06-12 · Kalshi · 7 条相关讨论
got a few `{"code":25,"msg":"Subscription buffer overflow"}` errors in the hour after maintenance ended, that's a new one to me
got a few `{"code":25,"msg":"Subscription buffer overflow"}` errors in the hour after maintenance ended, that's a new one to me
Just got this error as well.
Just got this error as well.
getting a LOT of these on orderbook_delta today ``` 2026-06-11T02:27:32.871454-07:00 recv {"type":"error","sid":5,"seq":788175,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T02:37:48.037057-07:00 recv {"type":"error","sid":5,"seq":749511,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T06:27:46.255354-07:00 recv {"type":"error","sid":5,"seq":1159130,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T07:28:02.518391-07:00 recv {"type":"error","sid":5,"seq":977122,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T12:46:50.11565-07:00 recv {"type":"error","sid":5,"seq":2603712,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T12:52:09.495339-07:00 recv {"type":"error","sid":5,"seq":1135716,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T12:58:00.776629-07:00 recv {"type":"error","sid":5,"seq":1161842,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T13:05:25.052673-07:00 recv {"type":"error","sid":5,"seq":1175098,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T13:23:00.852754-07:00 recv {"type":"error","sid":5,"seq":1235265,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T14:11:02.185442-07:00 recv {"type":"error","sid":5,"seq":1492122,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T14:17:27.32136-07:00 recv {"type":"error","sid":5,"seq":1203785,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T15:12:12.074937-07:00 recv {"type":"error","sid":5,"seq":1504756,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T15:17:17.270374-07:00 recv {"type":"error","sid":5,"seq":1205601,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T15:24:10.790776-07:00 recv {"type":"error","sid":5,"seq":1246885,"msg":{"code":25,"msg":"Subscription buffer overflow"}} ```
getting a LOT of these on orderbook_delta today ``` 2026-06-11T02:27:32.871454-07:00 recv {"type":"error","sid":5,"seq":788175,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T02:37:48.037057-07:00 recv {"type":"error","sid":5,"seq":749511,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T06:27:46.255354-07:00 recv {"type":"error","sid":5,"seq":1159130,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T07:28:02.518391-07:00 recv {"type":"error","sid":5,"seq":977122,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T12:46:50.11565-07:00 recv {"type":"error","sid":5,"seq":2603712,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T12:52:09.495339-07:00 recv {"type":"error","sid":5,"seq":1135716,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T12:58:00.776629-07:00 recv {"type":"error","sid":5,"seq":1161842,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T13:05:25.052673-07:00 recv {"type":"error","sid":5,"seq":1175098,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T13:23:00.852754-07:00 recv {"type":"error","sid":5,"seq":1235265,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T14:11:02.185442-07:00 recv {"type":"error","sid":5,"seq":1492122,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T14:17:27.32136-07:00 recv {"type":"error","sid":5,"seq":1203785,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T15:12:12.074937-07:00 recv {"type":"error","sid":5,"seq":1504756,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T15:17:17.270374-07:00 recv {"type":"error","sid":5,"seq":1205601,"msg":{"code":25,"msg":"Subscription buffer overflow"}} 2026-06-11T15:24:10.790776-07:00 recv {"type":"error","sid":5,"seq":1246885,"msg":{"code":25,"msg":"Subscription buffer overflow"}} ```
looks a lot like a backpressure issue - you cannot handle the amount of messages it is sending. If so, its nice they send a message since there is no other way to know for sure. Solution: you will likely need to multi-thread, get faster infra, or optimize code that is blocking
looks a lot like a backpressure issue - you cannot handle the amount of messages it is sending. If so, its nice they send a message since there is no other way to know for sure. Solution: you will likely need to multi-thread, get faster infra, or optimize code that is blocking
i wasn't receiving skipped sequences before, it seems likely they've changed a buffer size on their end with this release. i do subscribe to a large number of markets, requiring me to start sharding would not be unreasonable. it would be nice to have official guidance about what this error means specifically
i wasn't receiving skipped sequences before, it seems likely they've changed a buffer size on their end with this release. i do subscribe to a large number of markets, requiring me to start sharding would not be unreasonable. it would be nice to have official guidance about what this error means specifically
backpressure can occur either on kalshi's end or on our end, and it can be hard to distinguish the two. i believe i have a pretty good handle on it on my end, and have taken serious effort to process incoming messages promptly and without blocking. maybe this new error message vs "Channel error" encodes some information about the source of the backpressure. or maybe it has nothing to do with backpressure at all. i am just seeking some official word about whether websocket client expectations have changed, and what those new expectations are, before speculatively sinking a bunch of effort into sharding my consumption across multiple connections
backpressure can occur either on kalshi's end or on our end, and it can be hard to distinguish the two. i believe i have a pretty good handle on it on my end, and have taken serious effort to process incoming messages promptly and without blocking. maybe this new error message vs "Channel error" encodes some information about the source of the backpressure. or maybe it has nothing to do with backpressure at all. i am just seeking some official word about whether websocket client expectations have changed, and what those new expectations are, before speculatively sinking a bunch of effort into sharding my consumption across multiple connections
I am going to take a stab at solving this (sharding across multiple websocket connections). Will let you know how it goes. For context, I subscribe to all available tickers and a single web socket connection + single orderbook subscription worked fine until Thursday. Blocking in the read thread is unlikely to be the issue for me, I simply read the data and shove it into a queue that has ample space.
I am going to take a stab at solving this (sharding across multiple websocket connections). Will let you know how it goes. For context, I subscribe to all available tickers and a single web socket connection + single orderbook subscription worked fine until Thursday. Blocking in the read thread is unlikely to be the issue for me, I simply read the data and shove it into a queue that has ample space.