kalshi.health
All guides
Kalshi basics

How to Fix Kalshi App Issues: Login, Location & Trading Errors

Investigate access, price updates, transfers, and uncertain orders with a cautious checklist — starting with what the available evidence can actually establish.

Last updated October 26, 2026

Outage, account problem, or uncertain order? Jump to the decision checklist

Start by checking Kalshi's own service announcements and comparing the app with the website. The browser checks at kalshi.health provide supporting reachability information, but cannot confirm whether trading, login, or an individual account is working. Note the error message before trying device-specific troubleshooting.

Independent guidance · kalshi.health

Is this an outage, an account problem, or an uncertain order?

An independently authored checklist, not an official diagnosis or a trade instruction. Green reachability does not prove trading, login, or account health. No keys, logs, or account IDs belong here.

Use “unknown” unless you have current official information. This selection does not fetch status. Exchange active alone does not mean trading active.

Separate connection evidence from service evidence

Official status is unknown. No outage diagnosis can be made from this selection or browser reachability alone.

  1. Compare the exact app and website errors and record the time and timezone privately.
  2. Read Kalshi’s official announcements. If appropriate, compare another ordinary connection; a browser restriction can affect both views.
  3. If official guidance recommends an update or restart, first reconcile any uncertain order in the official account.

Stop device troubleshooting if an order’s outcome is uncertain; use the uncertain-order checklist instead. Escalate persistent access problems through official support.

Evidence matrix: what each signal can tell you

Green browser reachability

What it establishes
This browser’s tested request completed under the check’s rules.
What it cannot establish
HTTP success, trading, login, account health, or an order’s outcome; no-CORS checks cannot inspect HTTP status or response bodies.

Failed browser check

What it establishes
The local check did not complete successfully within its limits.
What it cannot establish
A platform-wide outage or its cause; network restrictions and timeouts remain possible.

Official exchange status

What it establishes
The reported exchange_active and trading_active values at the time checked; these are distinct fields.
What it cannot establish
Account access, individual order results, or a guaranteed resume time.

Order status and fills

What it establishes
What the official account/API record reports for that order when inspected; compare resting, canceled, or executed status with fills.
What it cannot establish
That canceled means never filled, or that a timed-out request was rejected.

Pending transfer

What it establishes
The transfer is reported as pending in the view inspected.
What it cannot establish
Its cause or a universal completion date; use the method-specific in-account guidance.

Private evidence checklist for official support

  • Keep the error text, time and timezone, app/browser version, and symptom sequence privately.
  • For an uncertain order, keep only existing order/client IDs, market, and the official Orders/fills record privately; for a transfer, its existing reference and method-specific notice.
  • Sanitize screenshots: redact API keys, authorization headers, account IDs, email, bank details, and unrelated activity. Never paste keys or raw logs into this site.
  • Share sensitive references only through a verified official support channel inside your account, never in public comments or this checklist.

Kalshi official status · Kalshi official website and in-account support

Worked hypothetical cases

Illustrations only, not reports of real incidents.

Green check, login denied

Suppose the browser check is green but the official app reports a location restriction. The check is connection evidence, not eligibility evidence. Use official eligibility/support instructions and stop if access remains denied; do not infer legality or try a workaround.

Timeout, then a canceled record with fills

Suppose submit times out and the official account later shows the order as canceled with a fill. Do not repeat submit: cancellation does not erase prior fills. Match the existing reference, time, and market privately; ask support if the records still do not reconcile.

Trading paused, transfer pending

Suppose an official notice reports a trading pause and your transfer is pending. These signals do not prove the pause caused the transfer delay. Follow official pause updates without treating a resume estimate as a promise, and use the transfer method’s current in-account timing.

Official documented facts and developer note

Source review: October 26, 2026. The checklist and interpretations above are independent guidance. The following facts are from Kalshi’s documentation:

  • Exchange status distinguishes exchange_active from trading_active. An estimated trading resume time is an estimate, not a guarantee.
  • Order records include resting, canceled, and executed states and fill information. Inspect fills as well as status; cancellation does not establish that no fills occurred.
  • Developer note: the create-order quick start documents deduplication when an API retry uses the same client_order_id. This is not a retry instruction: this checklist sends no orders or API requests. A timeout does not prove failure; reconcile the existing order first.

Step 0 — Check whether Kalshi itself is down

Check Kalshi's own service announcements before diagnosing an outage. The checks on kalshi.health run from your browser and reflect that browser's connection to the tested endpoints. A failed check can result from your network, browser restrictions, a timeout, or a service problem; it does not prove a platform-wide incident. A successful check does not establish that login, deposits, or trading work. Compare the app with the website, note the time and error message, and contact Kalshi support if an account or transaction issue persists.

Geolocation verification failures

Location or eligibility messages need to be evaluated using Kalshi's current official instructions. A location error alone does not establish its cause or whether you are eligible to trade.

  • Read the exact message and follow official eligibility and location-verification instructions; do not use a workaround to bypass restrictions.
  • Review device or browser location permissions if official instructions request them.
  • Check network/privacy settings only as directed by official guidance, without masking or misrepresenting your location.
  • If eligibility is unclear or verification remains denied, stop and contact official support. This guide provides no assurance of legality.

WebSocket connection drops and stale prices

Live order-book prices stream over a WebSocket connection. Frozen prices or a reconnecting banner can indicate a streaming or connection problem, but the visible symptom alone does not identify the cause.

  • Switch networks — move from Wi-Fi to cellular or vice versa. Some corporate and campus firewalls block WebSocket traffic entirely.
  • Inspect the exact app/browser connection message, the last update time, and whether official views disagree. Follow official connection guidance rather than disabling security or privacy protections based on a guess.
  • If official guidance recommends restarting, first reconcile any uncertain order in the official account; restarting does not prove the underlying cause is resolved.
  • Compare official service announcements with your local connection evidence. Browser reachability cannot establish that the price stream or trading is healthy.

Pending or missing deposits

A pending deposit does not identify the cause of the delay. Use the transfer method's current stated processing time and status inside your official account.

  • Identify the payment method and read its current in-account processing window; do not apply a generic deadline to every method.
  • Check the account's transfer notice and your payment provider's record for any stated review, rejection, or reversal.
  • If the stated window has passed or records disagree, contact official support with the existing transfer reference privately.
  • Do not repeat a transfer solely because it is pending; ask support if the status or applicable timing is unclear.

API 403 and 500 errors

If you use the Kalshi API directly (or a third-party tool built on it), HTTP error codes are evidence to interpret alongside the response and official documentation, not a complete diagnosis. If the order and fill terms in those responses are unfamiliar, our prediction market glossary defines them.

  • For 403 Forbidden, review the specific response and official authentication/permission documentation. Do not assume a new key is required or blame the clock without evidence; never share credentials or raw logs here.
  • 429 indicates rate limiting. For safe read-only requests, follow official rate-limit guidance and backoff before another read. Do not apply automatic retries to orders or other mutations; reconcile any uncertain order first in official Orders and fills, and contact support if its outcome remains unknown.
  • 500/502/503 responses indicate a server-side error response, but do not establish whether an order executed. The browser checks on kalshi.health cannot inspect these HTTP status codes.
  • After a timeout or uncertain order response, STOP repeated submit. Check Orders and fills in the official account, retain existing order/client IDs, time, and market privately, and contact support if the outcome remains unknown. Canceled orders can have prior fills.

Clearing cache and reinstalling the app

Local state can contribute to display problems, but clearing cache is not a diagnosis or a guaranteed fix. Reconcile any uncertain order before changing app state, and make sure you can complete official account recovery if needed.

  • On iOS, follow official app/device instructions for offloading or reinstalling. Do not assume this clears all cached state or preserves login; you may need to sign in or recover access again.
  • On Android: Settings → Apps → Kalshi → Storage → Clear Cache (use Clear Data only as a last resort, since it signs you out).
  • On web: hard-refresh with Ctrl/Cmd+Shift+R, or clear site data for kalshi.com in your browser settings.
  • After reinstalling, follow the official sign-in and any verification prompts. Reinstallation does not resolve eligibility or an uncertain order outcome.

When to contact Kalshi support

Escalate persistent access problems, inconsistent transaction records, or an uncertain order outcome through the official support channel inside your Kalshi account. A green check on kalshi.health does not confirm exchange, login, or account health. Keep the exact error, a sanitized screenshot, time with timezone, and existing transaction/order references privately for official support; do not post keys, raw logs, or account IDs here.

FAQ

How do I fix Kalshi geolocation errors?
Follow Kalshi's current official eligibility and location-verification instructions, including any requested device permissions. If access remains denied or eligibility is unclear, stop and contact official support; do not bypass location checks.
Why is my Kalshi order stuck or failing?
If the order timed out or its outcome is uncertain, STOP repeated submit. Check Orders and fills in the official account, including prior fills on a canceled order. Keep existing order/client IDs, time, and market privately and contact official support if the outcome remains unknown. A timeout does not mean failure, and green reachability does not confirm trading or account health.
What should I do if Kalshi app is down?
Check Kalshi's own service announcements, record the error and time, and compare the app with the website. A failed browser check alone does not establish an outage. Contact Kalshi through its official support channels if the issue persists or concerns your account or a transaction.
How do I know if Kalshi is down or it's just me?
Use the browser checks as one clue, alongside Kalshi's own service announcements and the actual app or website error. Green means only that the tested check succeeded; red can reflect a local connection problem or a service problem. Neither result alone can distinguish an account-specific issue from a platform-wide incident.
Why does Kalshi say my location can't be verified?
The message alone does not establish the cause. Consult Kalshi's current official eligibility and location instructions, review permissions as directed, and contact official support if verification remains denied. Do not misrepresent your location or infer legality from this guide.
Why are my Kalshi prices frozen or not updating?
Frozen prices can indicate a streaming, connection, or service problem; the symptom does not prove which. Compare official app/website views and service announcements, check ordinary connection settings, and follow official refresh guidance. Do not treat stale prices or green reachability as proof of trading health.
How long do Kalshi deposits take to clear?
Use the current method-specific processing time stated inside your official account. Pending alone does not identify a cause or guarantee a completion date. Contact official support if that stated window has passed, the transfer fails, or records disagree; retain the existing reference privately and do not repeat a transfer solely because it is pending.
What does a 403 error from the Kalshi API mean?
Interpret the specific response using official authentication and permission documentation. A 403 alone does not establish that a key is expired or that your clock is wrong. Do not automatically regenerate credentials or share keys/raw logs here; seek official support if the cause remains unclear.
Will clearing the app cache delete my Kalshi account or funds?
Clearing local cache does not itself settle or cancel server-side orders. You may need to sign in or recover access afterward; this guide does not guarantee account state or any verification outcome. Reconcile uncertain orders in official Orders and fills before clearing app state, and contact official support if records remain unclear.

Keep reading

Kalshi basics
How Kalshi works: contracts, rules, and eligibility checks
Compare platforms
Kalshi vs Polymarket: verify product, access, and costs
Kalshi basics
Kalshi fees explained: a source-linked cost worksheet