User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 52 min ago. Last stored result reached it in 469 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 393 ms | 0 |
| Mon 18 | 0 | 0.0 | 429 ms | 0 |
| Mon 21 | 0 | 0.0 | 466 ms | 0 |
| Mon 23 | 0 | 0.0 | 380 ms | 0 |
| Tue 01 | 0 | 0.0 | 819 ms | 0 |
| Tue 03 | 0 | 0.0 | 412 ms | 0 |
| Tue 05 | 0 | 0.0 | 423 ms | 0 |
| Tue 07 | 0 | 0.0 | 235 ms | 0 |
| Tue 09 | 0 | 0.0 | 372 ms | 0 |
| Tue 11 | 0 | 0.0 | 412 ms | 0 |
| Tue 13 | 0 | 0.0 | 575 ms | 0 |
| Tue 16 | 0 | 0.0 | 551 ms | 0 |
| Tue 18 | 0 | 0.0 | 408 ms | 0 |
| Tue 20 | 0 | 0.0 | 331 ms | 0 |
| Tue 22 | 0 | 0.0 | 416 ms | 0 |
| Wed 01 | 0 | 0.0 | 244 ms | 0 |
| Wed 03 | 0 | 0.0 | 575 ms | 0 |
| Wed 05 | 0 | 0.0 | 413 ms | 0 |
| Wed 07 | 0 | 0.0 | 670 ms | 0 |
| Wed 10 | 0 | 0.0 | 251 ms | 0 |
| Wed 12 | 0 | 0.0 | 366 ms | 0 |
| Wed 14 | 0 | 0.0 | 564 ms | 0 |
| Wed 16 | 0 | 0.0 | 430 ms | 0 |
| Wed 18 | 0 | 0.0 | 542 ms | 0 |
| Wed 20 | 0 | 0.0 | 305 ms | 0 |
| Wed 23 | 0 | 0.0 | 400 ms | 0 |
| Thu 01 | 0 | 0.0 | 400 ms | 0 |
| Thu 03 | 0 | 0.0 | 460 ms | 0 |
| Thu 05 | 0 | 0.0 | 553 ms | 0 |
| Thu 07 | 0 | 0.0 | 492 ms | 0 |
| Thu 09 | 0 | 0.0 | 379 ms | 0 |
| Thu 11 | 0 | 0.0 | 407 ms | 0 |
| Thu 13 | 0 | 0.0 | 209 ms | 0 |
| Thu 15 | 0 | 0.0 | 444 ms | 0 |
| Thu 17 | 0 | 0.0 | 420 ms | 0 |
| Thu 19 | 0 | 0.0 | 409 ms | 0 |
| Thu 21 | 0 | 0.0 | 490 ms | 0 |
| Thu 23 | 0 | 0.0 | 481 ms | 0 |
| Fri 01 | 0 | 0.0 | 329 ms | 0 |
| Fri 03 | 0 | 0.0 | 535 ms | 0 |
| Fri 05 | 0 | 0.0 | 384 ms | 0 |
| Fri 07 | 0 | 0.0 | 246 ms | 0 |
| Fri 09 | 0 | 0.0 | 441 ms | 0 |
| Fri 10 | 0 | 0.0 | 532 ms | 0 |
| Fri 11 | 0 | 0.0 | 380 ms | 0 |
| Fri 13 | 0 | 0.0 | 421 ms | 0 |
| Fri 15 | 0 | 0.0 | 580 ms | 0 |
| Fri 17 | 0 | 0.0 | 469 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 Databot 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 Databot goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Databot alerts to Slack, Discord or a webhook — free.
We track Databot (databot.cl) as part of the Productivity group. Conecta WhatsApp, Instagram, email y más canales. Resuelve el 70% de consultas sin intervención humana.
Databot publishes an official status page at status.databot.cl; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
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: 438 ms average, 246–580 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Databot incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
438 ms on average over the last 24 hours (246–580 ms).
Yes, at https://status.databot.cl.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Databot here at once, the problem is on Databot'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 Databot. 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.