User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / 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 380 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 102 ms | 0 |
| Mon 17 | 0 | 0.0 | 133 ms | 0 |
| Mon 19 | 0 | 0.0 | 267 ms | 0 |
| Mon 21 | 0 | 0.0 | 54 ms | 0 |
| Mon 23 | 0 | 0.0 | 287 ms | 0 |
| Tue 01 | 0 | 0.0 | 101 ms | 0 |
| Tue 03 | 0 | 0.0 | 105 ms | 0 |
| Tue 06 | 0 | 0.0 | 107 ms | 0 |
| Tue 08 | 0 | 0.0 | 213 ms | 0 |
| Tue 10 | 0 | 0.0 | 267 ms | 0 |
| Tue 12 | 0 | 0.0 | 438 ms | 0 |
| Tue 14 | 0 | 0.0 | 108 ms | 0 |
| Tue 16 | 0 | 0.0 | 166 ms | 0 |
| Tue 19 | 0 | 0.0 | 233 ms | 0 |
| Tue 21 | 0 | 0.0 | 68 ms | 0 |
| Tue 23 | 0 | 0.0 | 64 ms | 0 |
| Wed 01 | 0 | 0.0 | 152 ms | 0 |
| Wed 04 | 0 | 0.0 | 167 ms | 0 |
| Wed 06 | 0 | 0.0 | 336 ms | 0 |
| Wed 08 | 0 | 0.0 | 38 ms | 0 |
| Wed 10 | 0 | 0.0 | 104 ms | 0 |
| Wed 13 | 0 | 0.0 | 189 ms | 0 |
| Wed 15 | 0 | 0.0 | 84 ms | 0 |
| Wed 17 | 0 | 0.0 | 133 ms | 0 |
| Wed 19 | 0 | 0.0 | 84 ms | 0 |
| Wed 21 | 0 | 0.0 | 84 ms | 0 |
| Wed 23 | 0 | 0.0 | 107 ms | 0 |
| Thu 02 | 0 | 0.0 | 84 ms | 0 |
| Thu 04 | 0 | 0.0 | 97 ms | 0 |
| Thu 06 | 0 | 0.0 | 132 ms | 0 |
| Thu 08 | 0 | 0.0 | 179 ms | 0 |
| Thu 10 | 0 | 0.0 | 94 ms | 0 |
| Thu 12 | 0 | 0.0 | 111 ms | 0 |
| Thu 14 | 0 | 0.0 | 104 ms | 0 |
| Thu 16 | 0 | 0.0 | 106 ms | 0 |
| Thu 18 | 0 | 0.0 | 173 ms | 0 |
| Thu 20 | 0 | 0.0 | 116 ms | 0 |
| Thu 22 | 0 | 0.0 | 75 ms | 0 |
| Thu 23 | 0 | 0.0 | 85 ms | 0 |
| Fri 01 | 0 | 0.0 | 92 ms | 0 |
| Fri 03 | 0 | 0.0 | 230 ms | 0 |
| Fri 05 | 0 | 0.0 | 120 ms | 0 |
| Fri 07 | 0 | 0.0 | 75 ms | 0 |
| Fri 09 | 0 | 0.0 | 104 ms | 0 |
| Fri 12 | 0 | 0.0 | 187 ms | 0 |
| Fri 14 | 0 | 0.0 | 80 ms | 0 |
| Fri 16 | 0 | 0.0 | 92 ms | 0 |
| Fri 18 | 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for cognee 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 cognee goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send cognee alerts to Slack, Discord or a webhook — free.
We track cognee (cognee.ai) as part of the AI group. Cognee is the open-source agent memory platform for LLM agents. Build persistent memory across sessions with graph, vector, and relational retrieval that runs self-hosted, in Docker, on-prem, or on Cognee Cloud.
cognee publishes an official status page at status.cognee.ai; 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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 126 ms average, 62–380 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public cognee incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
126 ms on average over the last 24 hours (62–380 ms).
Yes, at https://status.cognee.ai.
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 cognee here at once, the problem is on cognee'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 cognee. 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.