Gorgias is down: what we know so far
This page is live and updates as StatusBird re-checks Gorgias, every 2 minutes. First non-operational reading 20:40 UTC on October 30, 2026.
StatusBird recorded its first non-operational reading for Gorgias at 20:40 UTC on 30 October 2026, and the worst state observed was major. Polling every two minutes, StatusBird logged 30 non-operational readings covering one hour. The service had not returned to normal when this note was written. Gorgias posted an incident on its own status page at 20:07 UTC, titled "Mobile app authentication".
Incident at a glance
| Service | Gorgias |
|---|---|
| Date | October 30, 2026 |
| StatusBird first saw it | 20:40 UTC |
| Vendor posted an incident | 20:07 UTC |
| Recovery observed | Not yet |
| Duration | 3 hours 28 minutes and counting |
| Worst status observed | major |
| Non-operational readings | 104 |
All times UTC. StatusBird polls Gorgias every 2 minutes from its own infrastructure, so the true start and end sit within 2 minutes of the times above.
Was Gorgias down on October 30, 2026?
Yes. StatusBird recorded Gorgias as major from 20:40 UTC, and it was still non-operational 3 hours 28 minutes later at the most recent reading. 104 consecutive checks came back non-operational.
Customer support tools are partially down.
What caused the Gorgias outage?
The vendor has published no root cause statement that StatusBird can read, so the cause is not known. The incident title on the Gorgias status page refers to mobile app authentication, but a title is not an explanation, and StatusBird will not guess at what sat behind it. If Gorgias publishes a cause later, that will be the source to rely on.
Gorgias published an incident titled "Mobile app authentication" at 20:07 UTC. A root cause has not yet been published by the vendor, so nothing on this page attributes one.
How long was Gorgias down?
3 hours 28 minutes so far, measured from the first non-operational reading at 20:40 UTC to the most recent reading, which was still non-operational. StatusBird counts a service down from the first reading it fails, not from the moment the vendor admits it, which is why this number can be larger than the one on the vendor's own incident report.
Timeline, in UTC
| Time (UTC) | Event |
|---|---|
| 20:07 UTC | The vendor posts an incident on its own status page |
| 20:40 UTC | StatusBird records its first non-operational reading |
| 20:43 UTC | A second consecutive non-operational reading confirms the outage, alerts go out and this page is published |
| 00:08 UTC | Still non-operational at the last reading |
Who and what was affected
This hits stores that run customer support through Gorgias, where support tools are partially down. Agents may not be able to open tickets, reply to customer emails or chats, or pick up conversations on the mobile app, so queues build up while shoppers wait. Order questions, refund requests and delivery chasing all stall, and your response time commitments slip while the service is degraded.
How StatusBird detected it
StatusBird recorded its first non-operational reading for Gorgias at 20:40 UTC, and Gorgias's own status page confirms the incident, posted at 20:07 UTC. StatusBird polls every 2 minutes from its own infrastructure, so these are two independent records of the same window.
Method: StatusBird reads Gorgias's published status endpoint every 2 minutes and records every reading. Availability figures count major and critical only. The full method is at statusbird.io/methodology.
Lessons for merchants
- Keep a fallback support inbox outside Gorgias, and know how to point your contact form and auto-replies at it within minutes.
- Subscribe to the Gorgias status page directly, since it posted at 20:07 UTC, before external monitoring flagged the problem at 20:40 UTC.
- Write a holding message for shoppers in advance that admits delays without promising a fix time you cannot control.
- Log ticket backlog and response times during an outage, so you can work the queue down in order once service returns.
The longer version, with the checks specific to this service, is in the Gorgias outage playbook.
Frequently asked questions
Was Gorgias down on October 30, 2026?
Yes. StatusBird recorded Gorgias as major from 20:40 UTC on October 30, 2026. The incident was still running 3 hours 28 minutes later when this page last updated.
How long was Gorgias down?
3 hours 28 minutes, measured from the first non-operational reading at 20:40 UTC to the most recent reading, which was still non-operational. Readings are taken every 2 minutes, so the true start and end sit within 2 minutes of those times.
What caused the Gorgias outage?
Gorgias published an incident titled "Mobile app authentication" at 20:07 UTC. A root cause has not yet been published by the vendor, so nothing on this page attributes one.
How was this Gorgias outage detected?
StatusBird recorded its first non-operational reading for Gorgias at 20:40 UTC, and Gorgias's own status page confirms the incident, posted at 20:07 UTC. StatusBird polls every 2 minutes from its own infrastructure, so these are two independent records of the same window.
Was my store affected?
If your store calls Gorgias during checkout or fulfillment, the requests to check are the ones made between 20:40 UTC and now on October 30, 2026. Customer support tools are partially down.
Monitor Gorgias with StatusBird
This page exists because StatusBird was already watching. It checks Gorgias and the rest of the stack an online store runs on every 2 minutes and sends an SMS, email, Slack, Teams or Discord alert the moment a reading goes non-operational, which on this incident was 20:40 UTC.
Start monitoring free Live Gorgias status All Gorgias outages