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 19 min ago. Last stored result reached it in 405 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 902 ms | 0 |
| Mon 19 | 0 | 0.0 | 393 ms | 0 |
| Mon 21 | 0 | 0.0 | 270 ms | 0 |
| Tue 00 | 0 | 0.0 | 1018 ms | 0 |
| Tue 02 | 0 | 0.0 | 822 ms | 0 |
| Tue 04 | 0 | 0.0 | 853 ms | 0 |
| Tue 06 | 0 | 0.0 | 832 ms | 0 |
| Tue 08 | 0 | 0.0 | 922 ms | 0 |
| Tue 10 | 0 | 0.0 | 237 ms | 0 |
| Tue 12 | 0 | 0.0 | 250 ms | 0 |
| Tue 14 | 0 | 0.0 | 245 ms | 0 |
| Tue 17 | 0 | 0.0 | 383 ms | 0 |
| Tue 19 | 0 | 0.0 | 726 ms | 0 |
| Tue 21 | 0 | 0.0 | 828 ms | 0 |
| Tue 23 | 0 | 0.0 | 872 ms | 0 |
| Wed 02 | 0 | 0.0 | 695 ms | 0 |
| Wed 04 | 0 | 0.0 | 821 ms | 0 |
| Wed 06 | 0 | 0.0 | 898 ms | 0 |
| Wed 08 | 0 | 0.0 | 884 ms | 0 |
| Wed 11 | 0 | 0.0 | 397 ms | 0 |
| Wed 13 | 0 | 0.0 | 384 ms | 0 |
| Wed 15 | 0 | 0.0 | 1320 ms | 0 |
| Wed 17 | 0 | 0.0 | 777 ms | 0 |
| Wed 19 | 0 | 0.0 | 1039 ms | 0 |
| Wed 21 | 0 | 0.0 | 281 ms | 0 |
| Thu 00 | 0 | 0.0 | 931 ms | 0 |
| Thu 02 | 0 | 0.0 | 778 ms | 0 |
| Thu 04 | 0 | 0.0 | 272 ms | 0 |
| Thu 06 | 0 | 0.0 | 869 ms | 0 |
| Thu 08 | 0 | 0.0 | 843 ms | 0 |
| Thu 10 | 0 | 0.0 | 1348 ms | 0 |
| Thu 12 | 0 | 0.0 | 375 ms | 0 |
| Thu 14 | 0 | 0.0 | 905 ms | 0 |
| Thu 16 | 0 | 0.0 | 229 ms | 0 |
| Thu 18 | 0 | 0.0 | 825 ms | 0 |
| Thu 20 | 0 | 0.0 | 982 ms | 0 |
| Thu 22 | 0 | 0.0 | 249 ms | 0 |
| Fri 00 | 0 | 0.0 | 247 ms | 0 |
| Fri 02 | 0 | 0.0 | 817 ms | 0 |
| Fri 05 | 0 | 0.0 | 327 ms | 0 |
| Fri 07 | 0 | 0.0 | 457 ms | 0 |
| Fri 09 | 0 | 0.0 | 191 ms | 0 |
| Fri 11 | 0 | 0.0 | 202 ms | 0 |
| Fri 13 | 0 | 0.0 | 225 ms | 0 |
| Fri 15 | 0 | 0.0 | 1289 ms | 0 |
| Fri 17 | 0 | 0.0 | 543 ms | 0 |
| Fri 19 | 0 | 0.0 | 858 ms | 0 |
| Fri 21 | 0 | 0.0 | 405 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 Go1 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 Go1 goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Go1 alerts to Slack, Discord or a webhook — free.
Go1 is listed in our Productivity category and checked at go1.com. Simplify employee training with one subscription that delivers essential learning from 250+ providers, integrated seamlessly into your HR tech stack.
Go1 publishes an official status page at status.go1.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 535 ms average, 191–1289 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Go1 incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
535 ms on average over the last 24 hours (191–1289 ms).
Yes, at https://status.go1.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 Go1 here at once, the problem is on Go1'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 Go1. 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.