Looking for an update now? Check the current status, or follow Gorgias for future changes.
71.4%of 56 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
82.8%
29
5
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Actions that use Loop Returns may be delayed or fail because of an ongoing incident at Loop. Other actions are not affected. We'll share updates as Loop recovers.
A fix has been implemented and we are monitoring the results.
identified
We're aware of an issue that may cause delays in receiving Instagram direct messages in Gorgias. Messages are not lost — they will arrive, just later than usual.
Our team is investigating and working to restore normal delivery times.
Voice/SMS functionality degraded due to a Twilio incident
Our upstream telephony provider Twilio is currently experiencing an incident affecting Voice services (status.twilio.com). As a result, some customers may experience degraded or failed voice call functionality in Gorgias — including failed or delayed calls and inaccurate call test results.SMS and all other Gorgias features (email, chat, helpdesk) are unaffected.Twilio's engineering team has identified the cause and is deploying a fix.
We are monitoring the situation and will update this pa...
Cloud service provider network incident may affect a subset of Gorgias Customers
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
investigating
We are currently investigating this issue.
Legacy Incident Archive
38 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
May 2026
AI Agent degraded performance
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We changed the LLM service provider and we are monitoring the situation, we are seeing gradual improvement.
The default one is still having an open incident
identified
Due to third party LLM provider outage, we are experiencing degraded performance, higher latency for AI Agent and Ticket Translation
AI Agent - Too many handovers
majorSource not attested
Last archived state: resolved
View archived record details
identified
We've confirmed that some of the AI Agent's conversations are handed over due to a partial degradation of the OpenAI's API.
investigating
We are currently investigating this issue. It's most likely related to an outage on the OpenAI API, despite they haven't communicated about it yet.
investigating
We are currently investigating this issue. It's most likely related to an outage on the OpenAI API, despite they haven't about it on their status page.
Some merchands are reporting orders missing from the widgets / search
Source not attested
Last archived state: resolved
View archived record details
identified
We found the root cause, redeploying a previous version of the Helpdesk as a fix. No data was lost.
investigating
We are currently investigating this issue.
Ticket Search is delaying on one of the helpdesk cluster
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are currently investigating this issue.
Ticket view count is not updating on some accounts.
Source not attested
Last archived state: resolved
View archived record details
identified
We're still working on a fix for this issue. In the meantime, a hard refresh — Cmd + Shift + R on Mac, or Ctrl + Shift + R on Windows — should clear it up.
Sorry for the inconvenience.
investigating
Ticket view count are not updating correctly for some accounts. We are currently investigating this issue.
Delayed or missing view counts
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
investigating
We are currently investigating this issue.
Delayed ticket search results
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are currently investigating this issue causing delayed ticket search results.
April 2026
Account signup form reports errors
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been deployed, we are monitoring to ensure continuation of service
investigating
We are currently investigating this issue.
Message processing has been restored across all affected services
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Channels integrations are fully operational — all queued messages have been processed and are up to date.
E-commerce data processing is back to nominal throughput. All queued messages are being processed; full catch-up is expected within ~30 minutes.
We will post a final update once e-commerce data is fully up to date. Thank you for your patience.
investigating
Our team has investigated and attempted several mitigations, however the issue is still ongoing.
We are continuing to actively investigate and will provide an update as soon as we have more information.
We apologize for the inconvenience.
investigating
Since 07:02 CEST, customers on cluster us-east1-635c are experiencing delays in incoming messages and ecommerce events not appearing in real-time. This is caused by an internal messaging broker failure on the affected cluster.
investigating
New messages are not processed in real time; delayed message routing for channel and ecommerce integrations
We are currently investigating this issue.
