Skip to main content
Kagi logo

Is Kagi Down?

No — Kagi is up

Reachable from all 8 checked regions

Average response time: 328ms

Last checked · checks run every 6 hours

Official status page: https://status.kagi.com

Kagi uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
449ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 19 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

19-day clean streak
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: 100.00% uptime, 16 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 30 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 30 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
246ms
DNS 37ms TCP 6ms TLS 10ms TTFB 230ms
arn
324ms
DNS 42ms TCP 5ms TLS 23ms TTFB 277ms
cdg
344ms
DNS 107ms TCP 2ms TLS 16ms TTFB 337ms
dfw
133ms
DNS 66ms TCP 2ms TLS 6ms TTFB 129ms
sin
447ms
DNS 114ms TCP 1ms TLS 6ms TTFB 403ms
sjc
325ms
DNS 170ms TCP 12ms TLS 23ms TTFB 296ms
syd
580ms
DNS 207ms TCP 2ms TLS 140ms TTFB 576ms
yyz
226ms
DNS 115ms TCP 1ms TLS 26ms TTFB 222ms

What Kagi does

Kagi is a paid, ad-free search engine. Members set it as the default search in their browser, so when it fails every address-bar search fails with it. Kagi also runs Kagi Assistant, which answers with models from OpenAI, Anthropic, Google and others, Kagi Translate and a search API. Its sister product Orion is a free WebKit browser for Mac and iOS.

What an outage looks like

Searches return a blank results page or an HTTP 500 or 502 error, sometimes after a wait of several seconds, while the logged-out kagi.com homepage still loads. Tools such as the Summarizer, FastGPT or Kagi News can fail on their own. Problems are often limited to one region: the status page lists Search and API separately for nine regions, such as us-east4 or europe-west2, plus Translate and Assistant.

What to do about it

Open the Control Center in the upper-right of any Kagi page and note the node shown as Connected to, then read that region's Search row on status.kagi.com. If only Assistant fails, switch to another model, since each model depends on its provider. Orion keeps working when Kagi is down; you can change its default search engine under Settings, Search. Kagi's support address is support@kagi.com.

Is it down for everyone, or just you?

If this page says Kagi is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

B
Bing
C
ChatGPT
C
Claude
G
Google Gemini

Kagi outage FAQ

Is Kagi down for everyone or just me?
Often it is down for one region rather than everyone. Kagi connects you automatically to its nearest node, and runs data centers in North Virginia, Los Angeles, Iowa, London, the Netherlands, Hong Kong, Singapore, Sao Paulo and Sydney. The Control Center shows your node, for example EUROPE-WEST2, and status.kagi.com lists Search and API rows for each of those regions, so compare your node's row rather than the headline.
Why does the Kagi status page say no issues when search is failing?
It has happened before. During a January 2024 outage, users saw HTTP 500 errors while the page showed no issues, and Kagi's CEO said on Hacker News that it then had to be updated by hand. The page now records outages as short as one minute for single regions, but a failing search with a green page is still worth reporting on kagifeedback.org.
Does an OpenAI or Anthropic outage affect Kagi Assistant?
Yes, for the models that provider serves. Kagi says the Assistant makes API requests to third-party model providers, including OpenAI, Anthropic and Google, to generate responses. If one model stops answering, pick a different one from the dropdown below the prompt; Kagi lets you switch models in the middle of a thread, so you do not lose the conversation.
Does a Kagi outage affect the Orion browser?
Only its searches, and only if Kagi is your default. Orion is a separate WebKit browser and ships with no preset search engine; it asks you to choose one on first use of the address bar. Browsing keeps working during a Kagi outage, and you can switch the default under Settings, Search on macOS. The status page tracks orionfeedback.org, not the browser itself.
Is there Kagi maintenance scheduled?
Check the maintenance notices at the top of status.kagi.com before assuming an outage. Kagi posts planned work there in advance, and its notices for Kagi Search database maintenance have warned that writes such as profile or settings changes could be slower during the window. Slow settings changes inside a posted window are expected; failing searches outside one are an incident worth reporting.

How we measure this

  • We request Kagi's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Kagi publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Kagi goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required