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 208 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 49 ms | 0 |
| Tue 00 | 0 | 0.0 | 219 ms | 0 |
| Tue 02 | 0 | 0.0 | 100 ms | 0 |
| Tue 04 | 0 | 0.0 | 258 ms | 0 |
| Tue 06 | 0 | 0.0 | 90 ms | 0 |
| Tue 08 | 0 | 0.0 | 99 ms | 0 |
| Tue 10 | 0 | 0.0 | 372 ms | 0 |
| Tue 12 | 0 | 0.0 | 187 ms | 0 |
| Tue 15 | 0 | 0.0 | 185 ms | 0 |
| Tue 17 | 0 | 0.0 | 120 ms | 0 |
| Tue 19 | 0 | 0.0 | 165 ms | 0 |
| Tue 21 | 0 | 0.0 | 131 ms | 0 |
| Wed 00 | 0 | 0.0 | 257 ms | 0 |
| Wed 02 | 0 | 0.0 | 85 ms | 0 |
| Wed 04 | 0 | 0.0 | 234 ms | 0 |
| Wed 06 | 0 | 0.0 | 161 ms | 0 |
| Wed 09 | 0 | 0.0 | 201 ms | 0 |
| Wed 11 | 0 | 0.0 | 74 ms | 0 |
| Wed 13 | 0 | 0.0 | 193 ms | 0 |
| Wed 15 | 0 | 0.0 | 261 ms | 0 |
| Wed 17 | 0 | 0.0 | 155 ms | 0 |
| Wed 20 | 0 | 0.0 | 293 ms | 0 |
| Wed 22 | 0 | 0.0 | 97 ms | 0 |
| Thu 00 | 0 | 0.0 | 143 ms | 0 |
| Thu 02 | 0 | 0.0 | 226 ms | 0 |
| Thu 04 | 0 | 0.0 | 147 ms | 0 |
| Thu 06 | 0 | 0.0 | 260 ms | 0 |
| Thu 08 | 0 | 0.0 | 231 ms | 0 |
| Thu 10 | 0 | 0.0 | 230 ms | 0 |
| Thu 12 | 0 | 0.0 | 138 ms | 0 |
| Thu 15 | 0 | 0.0 | 167 ms | 0 |
| Thu 17 | 0 | 0.0 | 108 ms | 0 |
| Thu 19 | 0 | 0.0 | 139 ms | 0 |
| Thu 21 | 0 | 0.0 | 240 ms | 0 |
| Thu 23 | 0 | 0.0 | 197 ms | 0 |
| Fri 01 | 0 | 0.0 | 807 ms | 0 |
| Fri 03 | 0 | 0.0 | 310 ms | 0 |
| Fri 05 | 0 | 0.0 | 187 ms | 0 |
| Fri 06 | 0 | 0.0 | 212 ms | 0 |
| Fri 08 | 0 | 0.0 | 176 ms | 0 |
| Fri 10 | 0 | 0.0 | 76 ms | 0 |
| Fri 11 | 0 | 0.0 | 81 ms | 0 |
| Fri 13 | 0 | 0.0 | 295 ms | 0 |
| Fri 14 | 0 | 0.0 | 102 ms | 0 |
| Fri 16 | 0 | 0.0 | 182 ms | 0 |
| Fri 17 | 0 | 0.0 | 113 ms | 0 |
| Fri 18 | 0 | 0.0 | 87 ms | 0 |
| Fri 19 | 0 | 0.0 | 208 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 Zarla 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 Zarla goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Zarla alerts to Slack, Discord or a webhook — free.
We track Zarla (zarla.com) as part of the AI group. Zarla's AI website builder writes your copy, picks your photos and sets up your SEO from one sentence about your business. Free to build, pay when you publish.
Zarla publishes an official status page at status.zarla.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: 218 ms average, 76–807 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 Zarla incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
218 ms on average over the last 24 hours (76–807 ms).
Yes, at https://status.zarla.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 Zarla here at once, the problem is on Zarla'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 Zarla. 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.