Hi guys. How do you monitor API outages? It took almost 20s to get balance and I need some confirmation that the problem is not on my side.
Hi guys. How do you monitor API outages? It took almost 20s to get balance and I need some confirmation that the problem is not on my side.
Good place to start:
https://docs.kalshi.com/websockets/connection-keep-alive
Good place to start:
https://docs.kalshi.com/websockets/connection-keep-alive
Does it work for API as well?
Does it work for API as well?
Wholesale api outages have become somewhat rare in recent months (I'm sure someone is going to contradict me on this immediately) so you sort of have to know where your pain points are and build tests around them
Wholesale api outages have become somewhat rare in recent months (I'm sure someone is going to contradict me on this immediately) so you sort of have to know where your pain points are and build tests around them
If you're asking about the REST endpoint, I'm seeing it respond in around ~10ms currently.
If you're asking about the REST endpoint, I'm seeing it respond in around ~10ms currently.
The balance endpoints have been a little wonky lately
The balance endpoints have been a little wonky lately
I think they're doing some work on them surrounding subaccounts
I think they're doing some work on them surrounding subaccounts
You've seen high latency?
You've seen high latency?
But I wouldn't be surprised if there were occaisionally latency issues. I just don't monitor those for latency
But I wouldn't be surprised if there were occaisionally latency issues. I just don't monitor those for latency
It's 140ms for me as well.
It's 140ms for me as well.
now
now
It's going to depend on where your server is too
It's going to depend on where your server is too
This only checks the simplest things. The API has been very reliable compared to the past.
https://stats.uptimerobot.com/53rOQGUdnx
This only checks the simplest things. The API has been very reliable compared to the past.
https://stats.uptimerobot.com/53rOQGUdnx
Thank you.
Now I failed to get open orders for a market after 40 seconds 😫
Thank you.
Now I failed to get open orders for a market after 40 seconds 😫
This sounds like a you problem
This sounds like a you problem
Would the downtime shown on this reflect the planned maintenance windows? Looks like wed/thurs instances
Would the downtime shown on this reflect the planned maintenance windows? Looks like wed/thurs instances
user_data_timestamp has been bouncing around a bit today, but nothing crazy:
```
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
```
user_data_timestamp has been bouncing around a bit today, but nothing crazy:
```
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
```
It has been a bit since I looked at this. If I remember right, `/exchange/status` returns a 200 during the maintenance window that says the exchange is not available, so would not show as an outage.
It has been a bit since I looked at this. If I remember right, `/exchange/status` returns a 200 during the maintenance window that says the exchange is not available, so would not show as an outage.
This made me realize it is using the deprecated hostname. Fixing that now...
This made me realize it is using the deprecated hostname. Fixing that now...
I will say around 11am EST things were slow as mud for about half an hour for me but I just assumed it was my connection
I will say around 11am EST things were slow as mud for about half an hour for me but I just assumed it was my connection