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 59 min ago. Last stored result reached it in 360 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 126 ms | 0 |
| Mon 15 | 0 | 0.0 | 161 ms | 0 |
| Mon 17 | 0 | 0.0 | 165 ms | 0 |
| Mon 19 | 0 | 0.0 | 157 ms | 0 |
| Mon 21 | 0 | 0.0 | 212 ms | 0 |
| Tue 00 | 0 | 0.0 | 99 ms | 0 |
| Tue 02 | 0 | 0.0 | 253 ms | 0 |
| Tue 04 | 0 | 0.0 | 242 ms | 0 |
| Tue 06 | 0 | 0.0 | 220 ms | 0 |
| Tue 08 | 0 | 0.0 | 107 ms | 0 |
| Tue 10 | 0 | 0.0 | 199 ms | 0 |
| Tue 12 | 0 | 0.0 | 92 ms | 0 |
| Tue 14 | 0 | 0.0 | 183 ms | 0 |
| Tue 17 | 0 | 0.0 | 133 ms | 0 |
| Tue 19 | 0 | 0.0 | 127 ms | 0 |
| Tue 21 | 0 | 0.0 | 280 ms | 0 |
| Tue 23 | 0 | 0.0 | 90 ms | 0 |
| Wed 02 | 0 | 0.0 | 179 ms | 0 |
| Wed 04 | 0 | 0.0 | 131 ms | 0 |
| Wed 06 | 0 | 0.0 | 185 ms | 0 |
| Wed 08 | 0 | 0.0 | 95 ms | 0 |
| Wed 11 | 0 | 0.0 | 206 ms | 0 |
| Wed 13 | 0 | 0.0 | 218 ms | 0 |
| Wed 15 | 0 | 0.0 | 190 ms | 0 |
| Wed 17 | 0 | 0.0 | 141 ms | 0 |
| Wed 19 | 0 | 0.0 | 230 ms | 0 |
| Wed 21 | 0 | 0.0 | 220 ms | 0 |
| Wed 23 | 0 | 0.0 | 159 ms | 0 |
| Thu 02 | 0 | 0.0 | 194 ms | 0 |
| Thu 04 | 0 | 0.0 | 195 ms | 0 |
| Thu 06 | 0 | 0.0 | 210 ms | 0 |
| Thu 08 | 0 | 0.0 | 106 ms | 0 |
| Thu 10 | 0 | 0.0 | 194 ms | 0 |
| Thu 12 | 0 | 0.0 | 86 ms | 0 |
| Thu 14 | 0 | 0.0 | 187 ms | 0 |
| Thu 16 | 0 | 0.0 | 220 ms | 0 |
| Thu 18 | 0 | 0.0 | 320 ms | 0 |
| Thu 20 | 0 | 0.0 | 92 ms | 0 |
| Thu 22 | 0 | 0.0 | 187 ms | 0 |
| Fri 00 | 0 | 0.0 | 202 ms | 0 |
| Fri 02 | 0 | 0.0 | 144 ms | 0 |
| Fri 04 | 0 | 0.0 | 98 ms | 0 |
| Fri 06 | 0 | 0.0 | 169 ms | 0 |
| Fri 09 | 0 | 0.0 | 167 ms | 0 |
| Fri 11 | 0 | 0.0 | 88 ms | 0 |
| Fri 12 | 0 | 0.0 | 189 ms | 0 |
| Fri 14 | 0 | 0.0 | 132 ms | 0 |
| Fri 16 | 0 | 0.0 | 360 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 Archbee 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 Archbee goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Archbee alerts to Slack, Discord or a webhook — free.
We track Archbee (archbee.com) as part of the Productivity group. Build beautiful knowledge portals that are easy to navigate, search, share and contribute to.
Archbee publishes an official status page at status.archbee.com; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 179 ms average, 88–360 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Archbee incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
179 ms on average over the last 24 hours (88–360 ms).
Yes, at https://status.archbee.com.
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 Archbee here at once, the problem is on Archbee'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 Archbee. 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.