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 45 min ago. Last stored result reached it in 216 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 207 ms | 0 |
| Tue 02 | 0 | 0.0 | 260 ms | 0 |
| Tue 04 | 0 | 0.0 | 667 ms | 0 |
| Tue 06 | 0 | 0.0 | 318 ms | 0 |
| Tue 08 | 0 | 0.0 | 332 ms | 0 |
| Tue 11 | 0 | 0.0 | 181 ms | 0 |
| Tue 13 | 0 | 0.0 | 289 ms | 0 |
| Tue 15 | 0 | 0.0 | 247 ms | 0 |
| Tue 17 | 0 | 0.0 | 135 ms | 0 |
| Tue 18 | 0 | 0.0 | 267 ms | 0 |
| Tue 20 | 0 | 0.0 | 263 ms | 0 |
| Tue 23 | 0 | 0.0 | 280 ms | 0 |
| Wed 01 | 0 | 0.0 | 232 ms | 0 |
| Wed 03 | 0 | 0.0 | 361 ms | 0 |
| Wed 05 | 0 | 0.0 | 215 ms | 0 |
| Wed 08 | 0 | 0.0 | 361 ms | 0 |
| Wed 10 | 0 | 0.0 | 203 ms | 0 |
| Wed 12 | 0 | 0.0 | 374 ms | 0 |
| Wed 14 | 0 | 0.0 | 356 ms | 0 |
| Wed 16 | 0 | 0.0 | 194 ms | 0 |
| Wed 18 | 0 | 0.0 | 95 ms | 0 |
| Wed 21 | 0 | 0.0 | 219 ms | 0 |
| Wed 23 | 0 | 0.0 | 222 ms | 0 |
| Thu 01 | 0 | 0.0 | 120 ms | 0 |
| Thu 03 | 0 | 0.0 | 424 ms | 0 |
| Thu 05 | 0 | 0.0 | 229 ms | 0 |
| Thu 07 | 0 | 0.0 | 306 ms | 0 |
| Thu 09 | 0 | 0.0 | 259 ms | 0 |
| Thu 11 | 0 | 0.0 | 321 ms | 0 |
| Thu 13 | 0 | 0.0 | 225 ms | 0 |
| Thu 16 | 0 | 0.0 | 204 ms | 0 |
| Thu 18 | 0 | 0.0 | 154 ms | 0 |
| Thu 20 | 0 | 0.0 | 212 ms | 0 |
| Thu 22 | 0 | 0.0 | 126 ms | 0 |
| Fri 00 | 0 | 0.0 | 164 ms | 0 |
| Fri 02 | 0 | 0.0 | 135 ms | 0 |
| Fri 04 | 0 | 0.0 | 300 ms | 0 |
| Fri 06 | 0 | 0.0 | 138 ms | 0 |
| Fri 08 | 0 | 0.0 | 140 ms | 0 |
| Fri 10 | 0 | 0.0 | 386 ms | 0 |
| Fri 11 | 0 | 0.0 | 276 ms | 0 |
| Fri 12 | 0 | 0.0 | 193 ms | 0 |
| Fri 14 | 0 | 0.0 | 465 ms | 0 |
| Fri 16 | 0 | 0.0 | 136 ms | 0 |
| Fri 17 | 0 | 0.0 | 62 ms | 0 |
| Fri 18 | 0 | 0.0 | 268 ms | 0 |
| Fri 20 | 0 | 0.0 | 104 ms | 0 |
| Fri 21 | 0 | 0.0 | 216 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 Ocoya 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 Ocoya goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ocoya alerts to Slack, Discord or a webhook — free.
Ocoya, at ocoya.com, is one of the AI services we monitor. The AI copilot for your marketing. It writes, designs, schedules and replies alongside you — across social media, SEO and, soon, email, always in your brand’s voice.
Ocoya publishes an official status page at status.ocoya.com; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 208 ms average, 62–465 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 Ocoya incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
208 ms on average over the last 24 hours (62–465 ms).
Yes, at https://status.ocoya.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 Ocoya here at once, the problem is on Ocoya'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 Ocoya. 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.