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 43 min ago. Last stored result reached it in 86 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 11 | 0 | 0.0 | 126 ms | 0 |
| Mon 13 | 0 | 0.0 | 80 ms | 0 |
| Mon 15 | 0 | 0.0 | 98 ms | 0 |
| Mon 18 | 0 | 0.0 | 245 ms | 0 |
| Mon 20 | 0 | 0.0 | 94 ms | 0 |
| Mon 22 | 0 | 0.0 | 75 ms | 0 |
| Tue 00 | 0 | 0.0 | 183 ms | 0 |
| Tue 02 | 0 | 0.0 | 181 ms | 0 |
| Tue 04 | 0 | 0.0 | 493 ms | 0 |
| Tue 06 | 0 | 0.0 | 130 ms | 0 |
| Tue 08 | 0 | 0.0 | 156 ms | 0 |
| Tue 10 | 0 | 0.0 | 28 ms | 0 |
| Tue 13 | 0 | 0.0 | 133 ms | 0 |
| Tue 15 | 0 | 0.0 | 247 ms | 0 |
| Tue 17 | 0 | 0.0 | 122 ms | 0 |
| Tue 19 | 0 | 0.0 | 68 ms | 0 |
| Tue 22 | 0 | 0.0 | 131 ms | 0 |
| Wed 00 | 0 | 0.0 | 31 ms | 0 |
| Wed 02 | 0 | 0.0 | 194 ms | 0 |
| Wed 04 | 0 | 0.0 | 146 ms | 0 |
| Wed 06 | 0 | 0.0 | 133 ms | 0 |
| Wed 08 | 0 | 0.0 | 84 ms | 0 |
| Wed 11 | 0 | 0.0 | 204 ms | 0 |
| Wed 13 | 0 | 0.0 | 94 ms | 0 |
| Wed 15 | 0 | 0.0 | 191 ms | 0 |
| Wed 17 | 0 | 0.0 | 192 ms | 0 |
| Wed 19 | 0 | 0.0 | 81 ms | 0 |
| Wed 21 | 0 | 0.0 | 60 ms | 0 |
| Wed 23 | 0 | 0.0 | 192 ms | 0 |
| Thu 01 | 0 | 0.0 | 232 ms | 0 |
| Thu 03 | 0 | 0.0 | 188 ms | 0 |
| Thu 05 | 0 | 0.0 | 187 ms | 0 |
| Thu 07 | 0 | 0.0 | 100 ms | 0 |
| Thu 09 | 0 | 0.0 | 193 ms | 0 |
| Thu 11 | 0 | 0.0 | 169 ms | 0 |
| Thu 13 | 0 | 0.0 | 136 ms | 0 |
| Thu 16 | 0 | 0.0 | 181 ms | 0 |
| Thu 18 | 0 | 0.0 | 67 ms | 0 |
| Thu 20 | 0 | 0.0 | 31 ms | 0 |
| Thu 22 | 0 | 0.0 | 153 ms | 0 |
| Fri 00 | 0 | 0.0 | 92 ms | 0 |
| Fri 02 | 0 | 0.0 | 141 ms | 0 |
| Fri 04 | 0 | 0.0 | 91 ms | 0 |
| Fri 06 | 0 | 0.0 | 129 ms | 0 |
| Fri 08 | 0 | 0.0 | 37 ms | 0 |
| Fri 11 | 0 | 0.0 | 161 ms | 0 |
| Fri 13 | 0 | 0.0 | 178 ms | 0 |
| Fri 15 | 0 | 0.0 | 86 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 SweetHawk 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 SweetHawk goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send SweetHawk alerts to Slack, Discord or a webhook — free.
We track SweetHawk (sweethawk.com) as part of the Productivity group. SweetHawk apps give IT and HR service the structure it needs inside Zendesk: approvals and escalations, change management, onboarding and scheduled work.
SweetHawk publishes an official status page at status.sweethawk.com; 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: 109 ms average, 31–191 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public SweetHawk incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
109 ms on average over the last 24 hours (31–191 ms).
Yes, at https://status.sweethawk.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 SweetHawk here at once, the problem is on SweetHawk'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 SweetHawk. 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.