User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is Gatsby down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → gatsby.events—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 346 ms.
Official status
All clear
All systems operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 07 | 0 | 0.0 | 114 ms | 0 |
| Tue 09 | 0 | 0.0 | 308 ms | 0 |
| Tue 11 | 0 | 0.0 | 257 ms | 0 |
| Tue 13 | 0 | 0.0 | 81 ms | 0 |
| Tue 15 | 0 | 0.0 | 113 ms | 0 |
| Tue 18 | 0 | 0.0 | 114 ms | 0 |
| Tue 20 | 0 | 0.0 | 200 ms | 0 |
| Tue 22 | 0 | 0.0 | 74 ms | 0 |
| Wed 00 | 0 | 0.0 | 465 ms | 0 |
| Wed 03 | 0 | 0.0 | 144 ms | 0 |
| Wed 05 | 0 | 0.0 | 551 ms | 0 |
| Wed 07 | 0 | 0.0 | 253 ms | 0 |
| Wed 09 | 0 | 0.0 | 231 ms | 0 |
| Wed 12 | 0 | 0.0 | 117 ms | 0 |
| Wed 14 | 0 | 0.0 | 133 ms | 0 |
| Wed 16 | 0 | 0.0 | 202 ms | 0 |
| Wed 18 | 0 | 0.0 | 283 ms | 0 |
| Wed 20 | 0 | 0.0 | 157 ms | 0 |
| Wed 22 | 0 | 0.0 | 200 ms | 0 |
| Thu 01 | 0 | 0.0 | 159 ms | 0 |
| Thu 03 | 0 | 0.0 | 267 ms | 0 |
| Thu 05 | 0 | 0.0 | 176 ms | 0 |
| Thu 07 | 0 | 0.0 | 428 ms | 0 |
| Thu 09 | 0 | 0.0 | 103 ms | 0 |
| Thu 11 | 0 | 0.0 | 35 ms | 0 |
| Thu 13 | 0 | 0.0 | 233 ms | 0 |
| Thu 15 | 0 | 0.0 | 160 ms | 0 |
| Thu 17 | 0 | 0.0 | 240 ms | 0 |
| Thu 19 | 0 | 0.0 | 282 ms | 0 |
| Thu 21 | 0 | 0.0 | 236 ms | 0 |
| Thu 23 | 0 | 0.0 | 109 ms | 0 |
| Fri 01 | 0 | 0.0 | 178 ms | 0 |
| Fri 03 | 0 | 0.0 | 55 ms | 0 |
| Fri 05 | 0 | 0.0 | 153 ms | 0 |
| Fri 07 | 0 | 0.0 | 286 ms | 0 |
| Fri 09 | 0 | 0.0 | 200 ms | 0 |
| Fri 10 | 0 | 0.0 | 55 ms | 0 |
| Fri 12 | 0 | 0.0 | 194 ms | 0 |
| Fri 14 | 0 | 0.0 | 197 ms | 0 |
| Fri 16 | 0 | 0.0 | 295 ms | 0 |
| Fri 18 | 0 | 0.0 | 217 ms | 0 |
| Fri 19 | 0 | 0.0 | 136 ms | 0 |
| Fri 21 | 0 | 0.0 | 37 ms | 0 |
| Fri 23 | 0 | 0.0 | 74 ms | 0 |
| Sat 01 | 0 | 0.0 | 319 ms | 0 |
| Sat 03 | 0 | 0.0 | 226 ms | 0 |
| Sat 06 | 0 | 0.0 | 77 ms | 0 |
| Sat 08 | 0 | 0.0 | 346 ms | 0 |
Reliability
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.
Embed this status: free live Gatsby badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Gatsby yet. Outages of 10 minutes or more get their own page here.
Having trouble with Gatsby?
One report per service every 10 minutes from this network. No account.
Follow Gatsby
Get an email when Gatsby goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Gatsby alerts to Slack, Discord or a webhook — free.
About Gatsby
We track Gatsby (gatsby.events) as part of the Productivity group. Invitations from your team's real inboxes. Branded RSVP pages. Seating charts, check-in, and guest profiles that carry forward across every event. Syncs to your CRM.
Gatsby publishes an official status page at status.gatsby.events; 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: 182 ms average, 37–346 ms range across 15 successful checks.
Questions
Is Gatsby down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Gatsby last down?
We have not recorded a public Gatsby incident since monitoring began 8 days ago.
What is Gatsby's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Gatsby respond?
182 ms on average over the last 24 hours (37–346 ms).
Does Gatsby have an official status page?
Yes, at https://status.gatsby.events.
Gatsby not working for me but the status is fine. What now?
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 Gatsby here at once, the problem is on Gatsby'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 Gatsby. 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.