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 1 hr 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 |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 579 ms | 0 |
| Nov 7 | 0 | 0.0 | 272 ms | 0 |
| Nov 7 | 0 | 0.0 | 397 ms | 0 |
| Nov 7 | 0 | 0.0 | 380 ms | 0 |
| Nov 8 | 0 | 0.0 | 302 ms | 0 |
| Nov 8 | 0 | 0.0 | 408 ms | 0 |
| Nov 8 | 0 | 0.0 | 391 ms | 0 |
| Nov 8 | 0 | 0.0 | 390 ms | 0 |
| Nov 9 | 0 | 0.0 | 382 ms | 0 |
| Nov 9 | 0 | 0.0 | 395 ms | 0 |
| Nov 9 | 0 | 0.0 | 399 ms | 0 |
| Nov 9 | 0 | 0.0 | 429 ms | 0 |
| Nov 10 | 0 | 0.0 | 423 ms | 0 |
| Nov 10 | 0 | 0.0 | 372 ms | 0 |
| Nov 10 | 0 | 0.0 | 551 ms | 0 |
| Nov 10 | 0 | 0.0 | 408 ms | 0 |
| Nov 11 | 0 | 0.0 | 413 ms | 0 |
| Nov 11 | 0 | 0.0 | 415 ms | 0 |
| Nov 11 | 0 | 0.0 | 413 ms | 0 |
| Nov 11 | 0 | 0.0 | 400 ms | 0 |
| Nov 12 | 0 | 0.0 | 460 ms | 0 |
| Nov 12 | 0 | 0.0 | 407 ms | 0 |
| Nov 12 | 0 | 0.0 | 420 ms | 0 |
| Nov 12 | 0 | 0.0 | 481 ms | 0 |
| Nov 13 | 0 | 0.0 | 384 ms | 0 |
| Nov 13 | 0 | 0.0 | 411 ms | 0 |
| Nov 13 | 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.