Bot for Kalshi
Service status

Current operating health.

This page reports customer-facing checks without exposing account data, internal error logs or infrastructure details.

Current status

Active checks operationalSynthetic checks are passing; integrations without a safe test call are labeled as usage-monitored below.
Trading engineEvaluates your bots and places orders last cycle 0.4 min ago
Operational
Website & dashboardThis site and the customer dashboard 53 ms now · 48 ms median (24h) · 100.0% uptime (7d)
Operational
Sign-inAccount login and sessions 17 ms now · 13 ms median (24h) · 100.0% uptime (7d)
Operational
Kalshi market data APILive market prices and orderbooks your bots trade on 168 ms now · 183 ms median (24h) · 98.7% uptime (7d)
Operational
Core databaseBot state, orders, receipts and accounts 23 ms now · 21 ms median (24h) · 100.0% uptime (7d)
Operational
Payments (Stripe)Checkout and subscription billing 244 ms now · 274 ms median (24h) · 100.0% uptime (7d)
Operational
Email delivery (Resend)Receipts, alerts and offer emails
Monitored via usage
AI bot builder (Anthropic)Plain-English bot building
Monitored via usage
External signal feedsSports, weather, crypto and macro data sources
Operational

Latency shown is from our automated checks (every 10 minutes), measured from our infrastructure.

Last automated check: . Checks older than 25 minutes are shown as unavailable instead of green.

Kalshi API as observed from our servers

Your bots reach Kalshi over its public API, so we check that API on a schedule and publish what we see. This is our observation from our own infrastructure — it is not Kalshi’s official status, and Kalshi has not reviewed or endorsed it. A problem on our side of the internet can look like a Kalshi problem here, and a Kalshi problem local to another region may not show up at all.

Reachable
Last check
Latency (last check)
168 ms
Median latency (24h)
183 ms
Checks passed (24h)
100.0%
Checks passed (7d)
98.7%

Every 10 minutes our monitor makes 3 calls to Kalshi: the exchange-status endpoint, which we only count as green when it reports the exchange and trading as active; a public market read; a Sports milestone read. “Checks passed” is the share of those runs that fully succeeded — it is our success rate against Kalshi, not Kalshi’s uptime.

Kalshi does not publish an official public status page that we could link here (checked September 12, 2026); third-party Kalshi monitors exist but are not operated by Kalshi. The closest first-party surface is Kalshi’s own exchange status endpoint, which our check reads. For an account-specific problem, contact Kalshi.

Incident communication

No separate public incident timeline is available yet.During an active customer-facing issue, component health above will reflect the latest automated checks. If your account is affected while this page looks healthy, contact support so the specific path can be investigated.

Need help with your account?

Service-wide health cannot diagnose an individual configuration. Visit Support or email support@botforkalshi.com.