User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is kagi down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → kagi.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 22 min ago. Last stored result reached it in 214 ms.
Official status
All clear
All systems operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 255 ms | 0 |
| Nov 7 | 0 | 0.0 | 233 ms | 0 |
| Nov 7 | 0 | 0.0 | 233 ms | 0 |
| Nov 7 | 0 | 0.0 | 127 ms | 0 |
| Nov 8 | 0 | 0.0 | 212 ms | 0 |
| Nov 8 | 0 | 0.0 | 202 ms | 0 |
| Nov 8 | 0 | 0.0 | 136 ms | 0 |
| Nov 8 | 0 | 0.0 | 181 ms | 0 |
| Nov 9 | 0 | 0.0 | 195 ms | 0 |
| Nov 9 | 0 | 0.0 | 264 ms | 0 |
| Nov 9 | 0 | 0.0 | 201 ms | 0 |
| Nov 9 | 0 | 0.0 | 247 ms | 0 |
| Nov 10 | 0 | 0.0 | 237 ms | 0 |
| Nov 10 | 0 | 0.0 | 392 ms | 0 |
| Nov 10 | 0 | 0.0 | 155 ms | 0 |
| Nov 10 | 0 | 0.0 | 467 ms | 0 |
| Nov 11 | 0 | 0.0 | 197 ms | 0 |
| Nov 11 | 0 | 0.0 | 183 ms | 0 |
| Nov 11 | 0 | 0.0 | 200 ms | 0 |
| Nov 11 | 0 | 0.0 | 174 ms | 0 |
| Nov 12 | 0 | 0.0 | 224 ms | 0 |
| Nov 12 | 0 | 0.0 | 228 ms | 0 |
| Nov 12 | 0 | 0.0 | 190 ms | 0 |
| Nov 12 | 0 | 0.0 | 244 ms | 0 |
| Nov 13 | 0 | 0.0 | 192 ms | 0 |
| Nov 13 | 0 | 0.0 | 221 ms | 0 |
| Nov 13 | 0 | 0.0 | 202 ms | 0 |
| Nov 13 | 0 | 0.0 | 193 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live kagi badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
Having trouble with kagi?
One report per service every 10 minutes from this network. No account.
Follow kagi
Get an email when kagi goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send kagi alerts to Slack, Discord or a webhook — free.
About kagi
We track kagi (kagi.com) as part of the Cloud & developer group. Better search results. No ads. We pull from the leading search engines, then re-rank everything and filter out spam.
kagi publishes an official status page at status.kagi.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. We logged 1 public incident since monitoring began 8 days ago.
Response time over the last 24 hours: 276 ms average, 68–856 ms range across 21 successful checks.
Questions
Is kagi down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was kagi last down?
The most recent public incident we recorded started 2026-11-06 and lasted 12 h 49 min. 1 incident since monitoring began 8 days ago.
What is kagi's uptime?
From our own checks: 100% over 8 days of checks.
How fast does kagi respond?
276 ms on average over the last 24 hours (68–856 ms).
Does kagi have an official status page?
Yes, at https://status.kagi.com.
kagi not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report kagi here at once, the problem is on kagi's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with kagi. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.