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 52 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 165 ms | 0 |
| Tue 01 | 0 | 0.0 | 83 ms | 0 |
| Tue 03 | 0 | 0.0 | 51 ms | 0 |
| Tue 05 | 0 | 0.0 | 58 ms | 0 |
| Tue 07 | 0 | 0.0 | 44 ms | 0 |
| Tue 09 | 0 | 0.0 | 112 ms | 0 |
| Tue 11 | 0 | 0.0 | 47 ms | 0 |
| Tue 14 | 0 | 0.0 | 159 ms | 0 |
| Tue 16 | 0 | 0.0 | 63 ms | 0 |
| Tue 18 | 0 | 0.0 | 146 ms | 0 |
| Tue 20 | 0 | 0.0 | 130 ms | 0 |
| Tue 23 | 0 | 0.0 | 128 ms | 0 |
| Wed 01 | 0 | 0.0 | 155 ms | 0 |
| Wed 03 | 0 | 0.0 | 175 ms | 0 |
| Wed 05 | 0 | 0.0 | 58 ms | 0 |
| Wed 08 | 0 | 0.0 | 75 ms | 0 |
| Wed 10 | 0 | 0.0 | 48 ms | 0 |
| Wed 12 | 0 | 0.0 | 123 ms | 0 |
| Wed 14 | 0 | 0.0 | 57 ms | 0 |
| Wed 16 | 0 | 0.0 | 84 ms | 0 |
| Wed 18 | 0 | 0.0 | 73 ms | 0 |
| Wed 21 | 0 | 0.0 | 121 ms | 0 |
| Wed 23 | 0 | 0.0 | 232 ms | 0 |
| Thu 01 | 0 | 0.0 | 163 ms | 0 |
| Thu 03 | 0 | 0.0 | 362 ms | 0 |
| Thu 05 | 0 | 0.0 | 102 ms | 0 |
| Thu 07 | 0 | 0.0 | 155 ms | 0 |
| Thu 09 | 0 | 0.0 | 150 ms | 0 |
| Thu 11 | 0 | 0.0 | 68 ms | 0 |
| Thu 13 | 0 | 0.0 | 110 ms | 0 |
| Thu 15 | 0 | 0.0 | 149 ms | 0 |
| Thu 17 | 0 | 0.0 | 42 ms | 0 |
| Thu 19 | 0 | 0.0 | 45 ms | 0 |
| Thu 22 | 0 | 0.0 | 131 ms | 0 |
| Fri 00 | 0 | 0.0 | 53 ms | 0 |
| Fri 02 | 0 | 0.0 | 59 ms | 0 |
| Fri 04 | 0 | 0.0 | 107 ms | 0 |
| Fri 06 | 0 | 0.0 | 129 ms | 0 |
| Fri 08 | 0 | 0.0 | 94 ms | 0 |
| Fri 10 | 0 | 0.0 | 123 ms | 0 |
| Fri 11 | 0 | 0.0 | 41 ms | 0 |
| Fri 13 | 0 | 0.0 | 121 ms | 0 |
| Fri 15 | 0 | 0.0 | 51 ms | 0 |
| Fri 17 | 0 | 0.0 | 56 ms | 0 |
| Fri 18 | 0 | 0.0 | 113 ms | 0 |
| Fri 19 | 0 | 0.0 | 127 ms | 0 |
| Fri 20 | 0 | 0.0 | 236 ms | 0 |
| Fri 22 | 0 | 0.0 | 52 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 Geckoboard 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 Geckoboard goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Geckoboard alerts to Slack, Discord or a webhook — free.
We track Geckoboard (geckoboard.com) as part of the Productivity group. Geckoboard turns live data from HubSpot, Zendesk, Salesforce and 90+ tools into real-time KPI dashboards your whole team can see on TVs, Slack, Microsoft Teams, email and mobile. Free 14-day trial.
Geckoboard publishes an official status page at status.geckoboard.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 100 ms average, 41–236 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Geckoboard incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
100 ms on average over the last 24 hours (41–236 ms).
Yes, at https://status.geckoboard.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 Geckoboard here at once, the problem is on Geckoboard'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 Geckoboard. 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.