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 38 min ago. Last stored result reached it in 193 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 15 | 0 | 0.0 | 230 ms | 0 |
| Tue 18 | 0 | 0.0 | 150 ms | 0 |
| Tue 20 | 0 | 0.0 | 78 ms | 0 |
| Tue 22 | 0 | 0.0 | 215 ms | 0 |
| Wed 00 | 0 | 0.0 | 319 ms | 0 |
| Wed 02 | 0 | 0.0 | 132 ms | 0 |
| Wed 05 | 0 | 0.0 | 211 ms | 0 |
| Wed 07 | 0 | 0.0 | 181 ms | 0 |
| Wed 09 | 0 | 0.0 | 260 ms | 0 |
| Wed 12 | 0 | 0.0 | 85 ms | 0 |
| Wed 14 | 0 | 0.0 | 195 ms | 0 |
| Wed 16 | 0 | 0.0 | 267 ms | 0 |
| Wed 18 | 0 | 0.0 | 215 ms | 0 |
| Wed 20 | 0 | 0.0 | 273 ms | 0 |
| Wed 22 | 0 | 0.0 | 135 ms | 0 |
| Thu 00 | 0 | 0.0 | 246 ms | 0 |
| Thu 03 | 0 | 0.0 | 246 ms | 0 |
| Thu 05 | 0 | 0.0 | 121 ms | 0 |
| Thu 07 | 0 | 0.0 | 144 ms | 0 |
| Thu 09 | 0 | 0.0 | 170 ms | 0 |
| Thu 11 | 0 | 0.0 | 208 ms | 0 |
| Thu 13 | 0 | 0.0 | 125 ms | 0 |
| Thu 15 | 0 | 0.0 | 241 ms | 0 |
| Thu 17 | 0 | 0.0 | 261 ms | 0 |
| Thu 19 | 0 | 0.0 | 181 ms | 0 |
| Thu 21 | 0 | 0.0 | 225 ms | 0 |
| Thu 23 | 0 | 0.0 | 152 ms | 0 |
| Fri 01 | 0 | 0.0 | 187 ms | 0 |
| Fri 03 | 0 | 0.0 | 97 ms | 0 |
| Fri 05 | 0 | 0.0 | 181 ms | 0 |
| Fri 07 | 0 | 0.0 | 108 ms | 0 |
| Fri 09 | 0 | 0.0 | 135 ms | 0 |
| Fri 10 | 0 | 0.0 | 102 ms | 0 |
| Fri 12 | 0 | 0.0 | 150 ms | 0 |
| Fri 14 | 0 | 0.0 | 119 ms | 0 |
| Fri 15 | 0 | 0.0 | 174 ms | 0 |
| Fri 17 | 0 | 0.0 | 200 ms | 0 |
| Fri 19 | 0 | 0.0 | 215 ms | 0 |
| Fri 21 | 0 | 0.0 | 152 ms | 0 |
| Fri 23 | 0 | 0.0 | 87 ms | 0 |
| Sat 00 | 0 | 0.0 | 201 ms | 0 |
| Sat 02 | 0 | 0.0 | 82 ms | 0 |
| Sat 04 | 0 | 0.0 | 172 ms | 0 |
| Sat 06 | 0 | 0.0 | 143 ms | 0 |
| Sat 08 | 0 | 0.0 | 160 ms | 0 |
| Sat 10 | 0 | 0.0 | 191 ms | 0 |
| Sat 12 | 0 | 0.0 | 179 ms | 0 |
| Sat 15 | 0 | 0.0 | 193 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Gojiberry AI 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 Gojiberry AI goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Gojiberry AI alerts to Slack, Discord or a webhook — free.
We track Gojiberry AI (gojiberry.ai) as part of the AI group. Gojiberry AI detects warm leads from 15+ buying and social signals, filters them by your ICP, and runs personalized outreach to book qualified demos automatically.
Gojiberry AI publishes an official status page at status.gojiberry.ai; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 171 ms average, 82–262 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Gojiberry AI incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
171 ms on average over the last 24 hours (82–262 ms).
Yes, at https://status.gojiberry.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 Gojiberry AI here at once, the problem is on Gojiberry AI'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 Gojiberry AI. 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.