Is user_data_timestamp outdated most of the time for anyone else now?
Is user_data_timestamp outdated most of the time for anyone else now?
2026-07-07 · Kalshi · 18 条相关讨论
Is user_data_timestamp outdated most of the time for anyone else now?
Is user_data_timestamp outdated most of the time for anyone else now?
The idea is that it is always outdated and it tells you how out of date it is. Are you seeing more latency than usual?
The idea is that it is always outdated and it tells you how out of date it is. Are you seeing more latency than usual?
Yeah, before when I fetched position immediately after ordering it had my updated position
Yeah, before when I fetched position immediately after ordering it had my updated position
API-wise
API-wise
Kalshi website also seems to be laggy in the same way
Kalshi website also seems to be laggy in the same way
I can order something and position / orderbook will be stale
I can order something and position / orderbook will be stale
Yes. The REST API is eventually consistent. The user data timestamp tells you when it was last updated.
Yes. The REST API is eventually consistent. The user data timestamp tells you when it was last updated.
But has it been slower for anyone else?
But has it been slower for anyone else?
Kalshi has made clear that when order books are untrustworthy, API traders should stop trading if they depend on order books.
Kalshi has made clear that when order books are untrustworthy, API traders should stop trading if they depend on order books.
Before I didn't even have the need to fetch the timestamp bc it was instantly updated pretty much
Before I didn't even have the need to fetch the timestamp bc it was instantly updated pretty much
Seems pretty good to me lately: ```select * from performance_metric where name='KalshiUserDataTimestampAge' order by timestamp desc limit 20 name|value|timestamp KalshiUserDataTimestampAge|0.097226997|1774902623992427 KalshiUserDataTimestampAge|0.061221057|1774902608861482 KalshiUserDataTimestampAge|0.045842825|1774902593751724 KalshiUserDataTimestampAge|0.032496992|1774902577488431 KalshiUserDataTimestampAge|0.056566414|1774902560001591 KalshiUserDataTimestampAge|0.062418379|1774902468115376 KalshiUserDataTimestampAge|0.090488454|1774902452845908 KalshiUserDataTimestampAge|0.103652282|1774902347004317 KalshiUserDataTimestampAge|0.131838069|1774902331912142 KalshiUserDataTimestampAge|0.161286923|1774899765359736 KalshiUserDataTimestampAge|0.123257642|1774899750224505 KalshiUserDataTimestampAge|0.048711014|1774899735156124 KalshiUserDataTimestampAge|0.049383044|1774899719609340 KalshiUserDataTimestampAge|0.064319321|1774899703974550 KalshiUserDataTimestampAge|0.087006098|1774899688895211 KalshiUserDataTimestampAge|0.060041015|1774899623205659 KalshiUserDataTimestampAge|0.079946661|1774899608011498 KalshiUserDataTimestampAge|0.057685518|1774899592905565 KalshiUserDataTimestampAge|0.05471152|1774899577598883 KalshiUserDataTimestampAge|0.073111515|1774899562456576 ```
Seems pretty good to me lately: ```select * from performance_metric where name='KalshiUserDataTimestampAge' order by timestamp desc limit 20 name|value|timestamp KalshiUserDataTimestampAge|0.097226997|1774902623992427 KalshiUserDataTimestampAge|0.061221057|1774902608861482 KalshiUserDataTimestampAge|0.045842825|1774902593751724 KalshiUserDataTimestampAge|0.032496992|1774902577488431 KalshiUserDataTimestampAge|0.056566414|1774902560001591 KalshiUserDataTimestampAge|0.062418379|1774902468115376 KalshiUserDataTimestampAge|0.090488454|1774902452845908 KalshiUserDataTimestampAge|0.103652282|1774902347004317 KalshiUserDataTimestampAge|0.131838069|1774902331912142 KalshiUserDataTimestampAge|0.161286923|1774899765359736 KalshiUserDataTimestampAge|0.123257642|1774899750224505 KalshiUserDataTimestampAge|0.048711014|1774899735156124 KalshiUserDataTimestampAge|0.049383044|1774899719609340 KalshiUserDataTimestampAge|0.064319321|1774899703974550 KalshiUserDataTimestampAge|0.087006098|1774899688895211 KalshiUserDataTimestampAge|0.060041015|1774899623205659 KalshiUserDataTimestampAge|0.079946661|1774899608011498 KalshiUserDataTimestampAge|0.057685518|1774899592905565 KalshiUserDataTimestampAge|0.05471152|1774899577598883 KalshiUserDataTimestampAge|0.073111515|1774899562456576 ```
Is value in seconds? Should I just add a .5 second delay before fetching newly added positions lol
Is value in seconds? Should I just add a .5 second delay before fetching newly added positions lol
But for your format, what is value?
But for your format, what is value?
Mine is consistently outdated by over a second currently: > [Kalshi] User data is stale by 1087ms. Aborting fetch. Now: 1783386549259, asOfTime: 1783386548172
Mine is consistently outdated by over a second currently: > [Kalshi] User data is stale by 1087ms. Aborting fetch. Now: 1783386549259, asOfTime: 1783386548172
For my system, `value` is seconds. I capture `user_data_timestamp` and compare it to my NTP clock.
For my system, `value` is seconds. I capture `user_data_timestamp` and compare it to my NTP clock.
Okay I guess I'm doing something wrong
Okay I guess I'm doing something wrong
I added a 5 second delay and I'm still getting that it was updated like 1 second before I call "Get User Data Timestamp"
I added a 5 second delay and I'm still getting that it was updated like 1 second before I call "Get User Data Timestamp"
Okay yeah idk why my logic was so weird before, thx
Okay yeah idk why my logic was so weird before, thx