Gorgias

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-10-19 20:48 UTC

   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.

2. resolved 2026-10-19 21:34 UTC

   Loop Returns has resolved their incident, and workflow actions that use Loop Returns are working normally again.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Aircall Aircall Apps

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-07 08:57 UTC

   We have identified an issue in the Aircall V2 integration which is managed by Aircall itself. Please follow the status updates from Aircall for more info: https://status.aircall.com/incidents/8v8s2hp1pj66

2. monitoring 2026-10-08 12:21 UTC

   Aircall has made a fix on their side and resolved the incident. See status page update here: https://status.aircall.com/incidents/8v8s2hp1pj66. We are monitoring the Aircall V2 integration traffic on our end to confirm the fix.

3. resolved 2026-10-08 12:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: us-central1-c433

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-05 14:45 UTC

   We are currently investigating this issue.

2. identified 2026-10-05 15:12 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2026-10-05 15:15 UTC

   A fix has been implemented and we are monitoring the results, the situation is coming back to normal progressively.

4. resolved 2026-10-05 16:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: AI Agent

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-09-30 17:21 UTC

   We’re monitoring the situation. The issue appears to be on the LLM provider’s side, and we’ll share updates as they become available

2. identified 2026-09-30 17:23 UTC

   External LLM providers are facing high latency, affecting the time the AI Agent takes to respond.

3. resolved 2026-09-30 20:59 UTC

   External LLM providers are facing high latency, affecting the time the AI Agent takes to respond.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Web App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-16 12:51 UTC

   We are currently investigating this issue.

2. identified 2026-09-16 13:12 UTC

   We identified the issue and currently actively working on the resolution.

3. resolved 2026-09-16 14:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Web App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-15 10:42 UTC

   We are currently investigating this issue.

2. monitoring 2026-09-15 11:06 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-15 11:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Web App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-14 18:37 UTC

   We are currently investigating this issue.

2. identified 2026-09-14 19:06 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2026-09-14 19:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Web App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-08 15:36 UTC

   We are investigating an issue that may prevent new Gorgias accounts to create Help Centers

2. resolved 2026-09-08 16:12 UTC

   Incident has been resolved

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Instagram Direct Messages

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-02 14:49 UTC

   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.

2. monitoring 2026-09-02 18:03 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-02 19:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-09-01 17:05 UTC

   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...

2. resolved 2026-09-01 18:00 UTC

   The incident affecting our upstream telephony provider, Twilio, has been resolved. Voice call functionality in Gorgias has returned to normal, including call test results.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: REST API, Google Cloud Platform Google Cloud Networking, Live Chat

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-01 15:19 UTC

   We are currently investigating this issue.

2. investigating 2026-09-01 15:21 UTC

   We are currently investigating this issue.

3. monitoring 2026-09-01 16:24 UTC

   We are seeing signs of recovery, we are continuing to monitor our services

4. resolved 2026-09-01 18:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Web App, us-east1-c94b

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-27 16:22 UTC

   We are currently investigating this issue.

2. identified 2026-08-27 16:30 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2026-08-27 16:43 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-08-27 17:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: WhatsApp

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-11 14:31 UTC

   Between 4:30 PM and 8:00 PM UTC on August 10th, some customers using the WhatsApp integration saw unexpected ticket behavior. New tickets were created with older messages, and some previously closed tickets reopened with older messages added to them, which in some cases produced...

2. resolved 2026-08-12 10:59 UTC

   The WhatsApp ticket issue that occurred on August 10th between 4:30 PM and 8:00 PM UTC is now fully resolved. **What happened:** A replay of WhatsApp webhooks caused older messages to be imported, which resulted in closed tickets reopening and, in some cases, duplicate tickets...

3. postmortem 2026-08-13 09:52 UTC

   On August 10, 2026, between approximately 4:30 and 8:00 PM UTC, some WhatsApp tickets unexpectedly reopened or duplicated. We understand how disruptive that is when you're trying to stay on top of customer conversations, and we'd like to walk you through what happened and how to...

Excerpts are shortened. Read the full incident on Gorgias's status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-11 11:36 UTC

   We are currently investigating this issue. Some users may experience issues during signup

2. resolved 2026-08-11 13:16 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Gmail

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-27 22:30 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-27 23:01 UTC

   Gmail integrations have resumed syncing normally and new emails are creating tickets as expected. Notifications delivery from Gmail stopped and then resumed on its own, without any change on our side. We found no issue with our systems, which suggests the cause was external....

3. resolved 2026-07-27 23:13 UTC

   The traffic of Gmail notifications for our app is back at normal levels.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-22 12:35 UTC

   One of our databases became temporarily unavailable. As a result, some e-commerce data was not available through our service. We are currently investigating the issue and working to restore full functionality as quickly as possible.

2. monitoring 2026-07-22 12:51 UTC

   One of our databases became temporarily unavailable. As a result, some e-commerce data was not available through our service. We are currently investigating the issue and working to restore full functionality as quickly as possible. The issue lasted from 10:56 to 11:28 UTC. The...

3. resolved 2026-07-22 13:13 UTC

   A transient network issue has been resolved, and all queued requests have been processed. All services are now operational.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: us-central1-d8ff

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-17 18:10 UTC

   We are currently investigating this issue. There might be lag on realtime updates on us-central1-df88

2. identified 2026-07-17 18:37 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2026-07-17 18:45 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-07-17 18:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-07-17 01:43 UTC

   What happened: Between 01:43 and 02:25 UTC, some customers experienced slow or failed Helpdesk responses and intermittent login issues. Impact was limited to a single infrastructure cluster (us-east1-2607). Cause: A temporary fault in our cloud provider's storage layer, isolated...

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: AI Agent

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-16 13:56 UTC

   We have identified the cause of elevated error rates on the AI Agent API. During this period, some AI Agent requests may fail or be delayed, and automated responses on affected tickets may not be sent. Our team is actively working on a fix to restore full service.

2. resolved 2026-07-16 14:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: AI Agent

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-07-15 16:42 UTC

   Between 08:00 and 18:30 UTC on July 14, an infrastructure issue at one of our third-party ML providers caused intermittent failures in the AI Agent’s knowledge retrieval. During this window, the AI Agent did not always pick up knowledge sources (Help Center articles and...

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Web App

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-15 10:18 UTC

   Syncing content from the Store website and URLs sources in Knowledge is failing for many stores. We are investigating the issue. Existing content is not affected.

2. identified 2026-07-16 11:13 UTC

   Syncing content from the Store website and URLs sources in Knowledge is failing for many stores. We are investigating the issue. Existing content is not affected.

3. monitoring 2026-07-17 12:01 UTC

   We deployed a fix to solve the Store website sync issues. We are monitoring the situation.

4. resolved 2026-07-17 13:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: REST API, Mobile Apps, us-central1-c433

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-07 16:01 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-07 18:20 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-07-07 20:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Web App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-03 10:14 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-03 10:33 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-07-03 11:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-01 11:25 UTC

   We are currently investigating this issue.

2. identified 2026-07-01 12:37 UTC

   We're working on deploying a fix

3. resolved 2026-07-01 13:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-29 16:03 UTC

   Due to a traffic spike, some customers might experience long loading times for analytics. We have identified the root cause and pushed a fix. If you still experience issues, you should try reloading the application in the browser.

2. monitoring 2026-06-29 16:32 UTC

   The root cause was addressed and we are currently monitoring the services.

3. resolved 2026-06-29 16:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: us-central1-d8ff

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-29 07:53 UTC

   We identified an issue affecting ticket search. Since approximately 9:19 AM CEST, search results may not include the most recent tickets or reflect the latest updates to existing tickets. Tickets themselves are not affected — they are being received and processed normally, and...

2. resolved 2026-06-29 08:47 UTC

   Ticket search is now up to date. Between 9:19 AM and 10:34 AM CEST, recently created or updated tickets may not have appeared in search results due to an infrastructure issue on one cluster. This has been fixed and all pending updates have processed. Tickets themselves were...

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Web App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-25 08:26 UTC

   Customers in the europe-west3 cluster may experience stale data in their views — including incorrect or missing ticket counts. Other regions are not impacted. Our team is actively working on a fix and will provide an update once resolved.

2. investigating 2026-06-25 08:44 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-06-25 09:02 UTC

   We have mitigated the issue affecting views in the europe-west3 cluster. Ticket counts and view data should now be updating, however performance is still degraded and updates may take longer than usual. We are monitoring the situation and will deploy a definitive fix to fully...

4. resolved 2026-06-25 16:40 UTC

   This incident is resolved. As of 12:57 CEST (10:57 UTC), views and ticket counts in the europe-west3 cluster are fully operational and updating normally again. We deployed changes to improve data ingestion reliability and confirmed that view data and ticket counts are accurate...

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Shopify integration

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-24 11:43 UTC

   We identified that the Shopify API is experiencing some degraded performance. That means some of our customers may experience some issues in regards to the Shopify actions. That includes the manual actions and the actions that are performed by the AI agent on Shopify, but also...

2. identified 2026-06-24 11:46 UTC

   We are continuing to monitor this issue.

3. resolved 2026-06-24 12:09 UTC

   This incident has been resolved. Shopify fixed the outage on their side.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Live Chat

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-22 14:50 UTC

   We are currently investigating this issue.

2. monitoring 2026-06-22 14:55 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-06-22 15:22 UTC

   A fix has been implemented and the chat is stable.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Facebook Messenger, Instagram Direct Messages, WhatsApp

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-12 14:27 UTC

   We are experiencing an outage on Meta side that affects outbound messages on Facebook, WhatsApp and Instagram.

2. identified 2026-06-12 14:28 UTC

   We are experiencing an outage on Meta side that affects outbound messages on Facebook, WhatsApp and Instagram.

3. monitoring 2026-06-12 14:58 UTC

   We are experiencing an outage on Meta side that affects outbound messages on Facebook, WhatsApp and Instagram.

4. resolved 2026-06-12 18:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-11 21:44 UTC

   We are continuing to work on a fix for this issue.

2. monitoring 2026-06-11 22:14 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-06-11 22:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-07 06:03 UTC

   We are currently investigating elevated latency in ecommerce data processing affecting customers in the **Australia Southeast** region. Starting around 04:00 UTC on June 7, an unexpected surge in ecommerce events caused a backlog in our internal processing pipeline. As a result,...

2. investigating 2026-06-07 06:10 UTC

   We are continuing to investigate this issue.

3. resolved 2026-06-07 06:39 UTC

   Resolved — Between 04:00 and 06:37 UTC on June 7, some customers may have experienced delays in ecommerce data updates within Gorgias. The issue has been fully resolved and all systems are operating normally. We apologize for any inconvenience caused.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-06-05 13:50 UTC

   We are receiving a surge of data which is causing the customer consumer data lag of about 1h. We are monitoring the data and will send another update in the next 2h.

2. resolved 2026-06-05 14:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Email, Chargebee Accounting Services

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-04 16:06 UTC

   We're investigating delays in receiving and processing new incoming messages across channels. No messages are being lost, and all affected messages will be processed once the issue is resolved. Sending messages and handling of existing conversations remain unaffected.

2. monitoring 2026-06-04 16:51 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2026-06-04 16:52 UTC

   We've identified the issue. Incoming messages and conversations were not affected and continued to work normally throughout the incident. The issue was limited to a background billing process, which briefly delayed some subscription and invoice updates. No data was lost, and the...

4. identified 2026-06-04 20:37 UTC

   The issue has been resolved, and the service is operating normally again. We are currently reprocessing historical events to fully complete the incident resolution.

5. monitoring 2026-06-04 20:37 UTC

   The issue has been resolved, and the service is operating normally again. We are currently reprocessing historical events to fully complete the incident resolution.

6. monitoring 2026-06-04 20:43 UTC

   The issue has been resolved, and the service is operating normally again. We are currently reprocessing historical events to fully complete the incident resolution.

7. resolved 2026-06-05 11:25 UTC

   This incident has been resolved. All events have been recovered

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: AI Agent

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-27 15:28 UTC

   Due to third party LLM provider outage, we are experiencing degraded performance, higher latency for AI Agent and Ticket Translation

2. monitoring 2026-05-27 16:52 UTC

   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

3. resolved 2026-05-28 06:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: AI Agent

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. investigating 2026-05-27 14:20 UTC

   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.

2. investigating 2026-05-27 14:25 UTC

   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.

3. identified 2026-05-27 14:34 UTC

   We've confirmed that some of the AI Agent's conversations are handed over due to a partial degradation of the OpenAI's API.

4. resolved 2026-05-27 18:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Shopify integration

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-21 14:24 UTC

   We are currently investigating this issue.

2. identified 2026-05-21 14:40 UTC

   We found the root cause, redeploying a previous version of the Helpdesk as a fix. No data was lost.

3. resolved 2026-05-21 16:03 UTC

   Incident is resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: europe-west4-e7f4

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-21 07:21 UTC

   We are currently investigating this issue.

2. monitoring 2026-05-21 08:12 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-21 08:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-18 02:47 UTC

   Ticket view count are not updating correctly for some accounts. We are currently investigating this issue.

2. identified 2026-05-18 03:46 UTC

   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.

3. resolved 2026-05-18 05:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Web App, aus-southeast1-fcb9

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-07 02:24 UTC

   We are currently investigating this issue.

2. identified 2026-05-07 02:43 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2026-05-07 03:53 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-05-07 04:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Web App, europe-west4-e7f4

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-06 06:34 UTC

   We are currently investigating this issue causing delayed ticket search results.

2. monitoring 2026-05-06 07:00 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-06 07:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-24 14:58 UTC

   We are currently investigating this issue.

2. monitoring 2026-04-24 15:24 UTC

   A fix has been deployed, we are monitoring to ensure continuation of service

3. resolved 2026-04-24 15:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: us-east1-635c

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-17 07:07 UTC

   New messages are not processed in real time; delayed message routing for channel and ecommerce integrations We are currently investigating this issue.

2. investigating 2026-04-17 07:45 UTC

   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.

3. investigating 2026-04-17 10:18 UTC

   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.

4. monitoring 2026-04-17 10:47 UTC

   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...

5. resolved 2026-04-17 11:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: Web App, Mobile Apps

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-04-09 17:18 UTC

   We are continuing to work on a fix for this issue.

2. resolved 2026-04-09 18:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: us-east1-c94b

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-09 12:19 UTC

   Following today's migration, some customers (impact scope is 10%) may experience delayed ticket and order updates or missing data. We are currently investigating this issue.

2. identified 2026-04-09 15:53 UTC

   We had an incident on Helpdesk today that impacted visibility of tickets and updates during a specific time period, for a subset of our customers in the US region. The system is currently operational. **What happened** Between 9:18 AM–12:15 PM UTC incoming tickets and messages...

3. monitoring 2026-04-09 20:43 UTC

   Update: We have completed initial recovery efforts of affected inbound tickets and interactions as of April 9th, 16:51 UTC. We are continuing to monitor for residual effects and will provide additional updates as they become available.

4. resolved 2026-04-10 08:44 UTC

   This incident has been resolved. We’re sorry for the inconvenience. Outbound messages and replies sent between 9:18 AM–12:15 PM UTC on April 9th will not be visible in Gorgias. Systems are currently fully operational, and we're working on addressing the factors that lead to this...

Excerpts are shortened. Read the full incident on Gorgias's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-09 10:42 UTC

   We are currently investigating this issue.

2. resolved 2026-04-09 11:24 UTC

   We experienced an issue affecting some Europe-hosted Helpdesks that prevented live updates from appearing in the interface. No data was lost, as the problem only impacted UI refresh. This incident has now been resolved. We’re sorry for the inconvenience.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: us-central1-d8ff

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-06 22:42 UTC

   We are currently experiencing an issue where customer search results in the Helpdesk may not reflect the most up-to-date information. Our team is actively investigating the problem and working on a fix. In the meantime, some recently created or updated customer records may not...

2. identified 2026-04-07 01:47 UTC

   We are currently experiencing an issue where customer search results in the Helpdesk may not reflect the most up-to-date information. Our team is actively investigating the problem and working on a fix. In the meantime, some recently created or updated customer records may not...

3. monitoring 2026-04-07 02:56 UTC

   We’ve mitigated for the issue and we’re continuing to monitor closely and will share any further updates if needed.

4. resolved 2026-04-07 04:32 UTC

   The issue is now resolved. We identified a specific payload that was blocking the search index update and addressed it. Everything is operating normally, and we’ll continue to keep an eye on things to ensure stability.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-04-03 12:46 UTC

   We are continuing to work on a fix for this issue.

2. monitoring 2026-04-03 12:52 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-04-03 16:25 UTC

   A fix has been implemented and we are monitoring the results.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-03-27 10:49 UTC

   The incident has been resolved and duplicate billing events are no longer being generated. We are now assessing the customer billing impact and will take the appropriate corrective actions where needed.

Excerpts are shortened. Read the full incident on Gorgias's status page.

Affected: AI Agent

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-26 16:00 UTC

   We are investigating an issue where the AI Agent is not picking up incoming email tickets. Affected tickets are remaining open and unassigned rather than being automatically triaged and handled by the AI Agent. Our team is actively working to identify the root cause and restore...

2. identified 2026-03-26 16:25 UTC

   We have identified the problem and are continuing to work on a fix for this issue.

3. resolved 2026-03-26 16:38 UTC

   The problem has been fixed. AI Agent has resumed processing email tickets. The incident has been resolved.

Excerpts are shortened. Read the full incident on Gorgias's status page.