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 436 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 220 ms | 0 |
| Mon 20 | 0 | 0.0 | 159 ms | 0 |
| Mon 22 | 0 | 0.0 | 377 ms | 0 |
| Tue 00 | 0 | 0.0 | 356 ms | 0 |
| Tue 02 | 0 | 0.0 | 236 ms | 0 |
| Tue 04 | 0 | 0.0 | 230 ms | 0 |
| Tue 06 | 0 | 0.0 | 141 ms | 0 |
| Tue 08 | 0 | 0.0 | 255 ms | 0 |
| Tue 10 | 0 | 0.0 | 202 ms | 0 |
| Tue 13 | 0 | 0.0 | 116 ms | 0 |
| Tue 15 | 0 | 0.0 | 262 ms | 0 |
| Tue 17 | 0 | 0.0 | 232 ms | 0 |
| Tue 19 | 0 | 0.0 | 207 ms | 0 |
| Tue 22 | 0 | 0.0 | 137 ms | 0 |
| Wed 00 | 0 | 0.0 | 218 ms | 0 |
| Wed 02 | 0 | 0.0 | 174 ms | 0 |
| Wed 04 | 0 | 0.0 | 205 ms | 0 |
| Wed 06 | 0 | 0.0 | 264 ms | 0 |
| Wed 09 | 0 | 0.0 | 2574 ms | 0 |
| Wed 11 | 0 | 0.0 | 109 ms | 0 |
| Wed 13 | 0 | 0.0 | 324 ms | 0 |
| Wed 15 | 0 | 0.0 | 232 ms | 0 |
| Wed 17 | 0 | 0.0 | 434 ms | 0 |
| Wed 19 | 0 | 0.0 | 211 ms | 0 |
| Wed 22 | 0 | 0.0 | 274 ms | 0 |
| Wed 23 | 0 | 0.0 | 253 ms | 0 |
| Thu 01 | 0 | 0.0 | 255 ms | 0 |
| Thu 03 | 0 | 0.0 | 239 ms | 0 |
| Thu 05 | 0 | 0.0 | 292 ms | 0 |
| Thu 07 | 0 | 0.0 | 204 ms | 0 |
| Thu 09 | 0 | 0.0 | 163 ms | 0 |
| Thu 11 | 0 | 0.0 | 128 ms | 0 |
| Thu 13 | 0 | 0.0 | 110 ms | 0 |
| Thu 15 | 0 | 0.0 | 239 ms | 0 |
| Thu 17 | 0 | 0.0 | 286 ms | 0 |
| Thu 19 | 0 | 0.0 | 218 ms | 0 |
| Thu 21 | 0 | 0.0 | 177 ms | 0 |
| Thu 23 | 0 | 0.0 | 239 ms | 0 |
| Fri 01 | 0 | 0.0 | 285 ms | 0 |
| Fri 03 | 0 | 0.0 | 130 ms | 0 |
| Fri 05 | 0 | 0.0 | 70 ms | 0 |
| Fri 08 | 0 | 0.0 | 285 ms | 0 |
| Fri 10 | 0 | 0.0 | 296 ms | 0 |
| Fri 12 | 0 | 0.0 | 125 ms | 0 |
| Fri 14 | 0 | 0.0 | 281 ms | 0 |
| Fri 16 | 0 | 0.0 | 148 ms | 0 |
| Fri 17 | 0 | 0.0 | 247 ms | 0 |
| Fri 19 | 0 | 0.0 | 436 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 Alphabot 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 Alphabot goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Alphabot alerts to Slack, Discord or a webhook — free.
We track Alphabot (alphabot.app) as part of the Productivity group. Boost your project's efficiency and security with our highly-customizable, feature-rich raffle sy...
Alphabot publishes an official status page at status.alphabot.app; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 232 ms average, 70–436 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 Alphabot incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
232 ms on average over the last 24 hours (70–436 ms).
Yes, at https://status.alphabot.app.
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 Alphabot here at once, the problem is on Alphabot'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 Alphabot. 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.