User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
kensho.com · AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 221 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 228 ms | 0 |
| Mon 22 | 0 | 0.0 | 271 ms | 0 |
| Tue 00 | 0 | 0.0 | 236 ms | 0 |
| Tue 02 | 0 | 0.0 | 264 ms | 0 |
| Tue 04 | 0 | 0.0 | 283 ms | 0 |
| Tue 06 | 0 | 0.0 | 201 ms | 0 |
| Tue 08 | 0 | 0.0 | 254 ms | 0 |
| Tue 10 | 0 | 0.0 | 218 ms | 0 |
| Tue 13 | 0 | 0.0 | 199 ms | 0 |
| Tue 15 | 0 | 0.0 | 254 ms | 0 |
| Tue 17 | 0 | 0.0 | 272 ms | 0 |
| Tue 19 | 0 | 0.0 | 4563 ms | 0 |
| Tue 22 | 0 | 0.0 | 224 ms | 0 |
| Wed 00 | 0 | 0.0 | 248 ms | 0 |
| Wed 02 | 0 | 0.0 | 228 ms | 0 |
| Wed 04 | 0 | 0.0 | 84 ms | 0 |
| Wed 07 | 0 | 0.0 | 198 ms | 0 |
| Wed 09 | 0 | 0.0 | 111 ms | 0 |
| Wed 11 | 0 | 0.0 | 64 ms | 0 |
| Wed 13 | 0 | 0.0 | 231 ms | 0 |
| Wed 15 | 0 | 0.0 | 235 ms | 0 |
| Wed 17 | 0 | 0.0 | 137 ms | 0 |
| Wed 20 | 0 | 0.0 | 227 ms | 0 |
| Wed 22 | 0 | 0.0 | 226 ms | 0 |
| Thu 00 | 0 | 0.0 | 193 ms | 0 |
| Thu 02 | 0 | 0.0 | 248 ms | 0 |
| Thu 04 | 0 | 0.0 | 273 ms | 0 |
| Thu 06 | 0 | 0.0 | 297 ms | 0 |
| Thu 08 | 0 | 0.0 | 282 ms | 0 |
| Thu 10 | 0 | 0.0 | 223 ms | 0 |
| Thu 12 | 0 | 0.0 | 223 ms | 0 |
| Thu 15 | 0 | 0.0 | 403 ms | 0 |
| Thu 17 | 0 | 0.0 | 263 ms | 0 |
| Thu 19 | 0 | 0.0 | 280 ms | 0 |
| Thu 21 | 0 | 0.0 | 230 ms | 0 |
| Thu 23 | 0 | 0.0 | 222 ms | 0 |
| Fri 01 | 0 | 0.0 | 251 ms | 0 |
| Fri 03 | 0 | 0.0 | 262 ms | 0 |
| Fri 05 | 0 | 0.0 | 285 ms | 0 |
| Fri 07 | 0 | 0.0 | 226 ms | 0 |
| Fri 08 | 0 | 0.0 | 206 ms | 0 |
| Fri 10 | 0 | 0.0 | 219 ms | 0 |
| Fri 12 | 0 | 0.0 | 222 ms | 0 |
| Fri 14 | 0 | 0.0 | 291 ms | 0 |
| Fri 16 | 0 | 0.0 | 154 ms | 0 |
| Fri 18 | 0 | 0.0 | 172 ms | 0 |
| Fri 20 | 0 | 0.0 | 286 ms | 0 |
| Fri 22 | 0 | 0.0 | 221 ms | 0 |
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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Kensho yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Kensho goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Kensho alerts to Slack, Discord or a webhook — free.
We track Kensho (kensho.com) as part of the AI group. Kensho Technologies, an S&P Global company, provides AI infrastructure, ML and NLP building blocks, and data retrieval solutions powering trusted agentic workflows in business and finance. Explore the Kensho LLM-ready API, core capabilities like Kensho Extract, and our industry-leading AI resear
Kensho publishes an official status page at status.kensho.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 233 ms average, 154–291 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Kensho incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
233 ms on average over the last 24 hours (154–291 ms).
Yes, at https://status.kensho.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Kensho here at once, the problem is on Kensho'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 Kensho. 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.