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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: Network or DNS. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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

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

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.

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.

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.

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

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

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

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

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

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.

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

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

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.

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

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

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

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.

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

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.

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.

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

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.

1. resolved 2026-03-20 19:22 UTC

   This incident has been resolved.

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

1. resolved 2026-03-17 14:37 UTC

   We can now confirm that everything is working as expected now and executed necessary data recovery protocols. Users should not be facing any further issues to this end.

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

1. resolved 2026-03-16 10:46 UTC

   Our team has successfully reactivated the vast majority of affected integrations; approximately 97% have been restored automatically. Import of any missed inbound messages during the disruption is currently in progress and may take some time to complete. A small minority of...

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

1. resolved 2026-03-09 18:40 UTC

   This incident has been resolved.

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

1. resolved 2026-03-09 20:34 UTC

   This incident has been resolved.

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

1. resolved 2026-03-09 13:32 UTC

   The issue regarding analytics has been resolved

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

1. resolved 2026-03-09 12:05 UTC

   This incident has been resolved.

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

1. resolved 2026-03-02 14:23 UTC

   This incident has been resolved.

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

1. resolved 2026-03-02 11:07 UTC

   This incident has been resolved. The recent tickets will start showing correctly inside the Knowledge Hub shortly.

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

1. resolved 2026-03-02 10:57 UTC

   This incident has been resolved. There was no data loss, statistics are now up-to-date

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

1. resolved 2026-02-28 17:59 UTC

   This incident has been resolved.

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

1. resolved 2026-02-03 09:09 UTC

   There is a delay in processing ticket data for the views and the data might not be up-to-date. We are working to fix the issue.

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

Names an upstream provider: Cloudflare.

1. resolved 2026-01-28 13:20 UTC

   This incident has been resolved.

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

1. resolved 2026-01-14 16:01 UTC

   We can now confirm that users should no longer face any further impact to this end. Apologies for the inconvenience caused.

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

1. resolved 2025-12-19 14:13 UTC

   We've identified the issue as being caused by third-party browser extensions. If you experience slowness, please try disabling your browser extensions, then close the affected tab and reopen the app. Simply refreshing the tab may not fully resolve the issue.

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

1. resolved 2025-12-17 16:19 UTC

   After monitoring the situation for some time, we can confirm that this incident has been resolved.

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

1. resolved 2025-12-15 21:53 UTC

   The issue affecting real-time updates delivered via our real-time infrastructure has been mitigated. Our team has scheduled upcoming work to improve the stability and performance of real-time updates across web and mobile clients.

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

1. resolved 2025-12-09 23:34 UTC

   This incident has been resolved.

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

1. resolved 2025-12-09 16:47 UTC

   This incident has been resolved.

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

1. resolved 2025-12-05 10:52 UTC

   After looking into it, we haven't noticed any meaningful impact on our Shopify customers, and we can now confirm full resolution of this incident. In the event that you encounter a sync issue between Shopify and Gorgias platforms, please be aware that it will be automatically...

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

1. resolved 2025-12-02 20:08 UTC

   The Incident was resolved.

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

1. resolved 2025-12-02 11:30 UTC

   Incident was resolved.

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

1. resolved 2025-12-01 08:06 UTC

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

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

1. resolved 2025-11-28 22:44 UTC

   The incident as been resolved since 17:00 ET and all systems are functional.

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

1. resolved 2025-11-27 10:16 UTC

   The third-party service has now fully recovered, and we are no longer experiencing any impact. AI agent systems are operating normally.

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

1. resolved 2025-11-20 16:17 UTC

   The issue affecting Instagram comments and mentions has been resolved. All data is now syncing normally. Thanks for your patience while we monitored the situation.

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

Names an upstream provider: Cloudflare.

1. resolved 2025-11-19 00:58 UTC

   This incident has been resolved.

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

1. resolved 2025-11-14 13:29 UTC

   This incident has been resolved.

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

1. resolved 2025-11-14 02:44 UTC

   No more on-going issues.

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

1. resolved 2025-11-13 15:01 UTC

   Issue has been resolved and latest statistical data should be visible.

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

1. resolved 2025-11-11 19:37 UTC

   This incident has been resolved.

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

1. resolved 2025-11-11 16:05 UTC

   We issue has been resolved.

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

1. resolved 2025-11-04 07:37 UTC

   We can now confirm that users are once again able to see and receive notifications on the platform and the incident has been resolved. We appreciate your patience and apologize for the inconvenience caused.

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

1. resolved 2025-11-03 09:00 UTC

   the endpoint POST /phrase/prediction has a high error rate on production caused by the redis db going OOM. A surge in requests exceeded the memory capacity.

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

1. resolved 2025-10-27 17:20 UTC

   This incident has been resolved.

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

1. resolved 2025-10-21 11:56 UTC

   All the systems are now fully operational.

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

1. resolved 2025-10-21 11:57 UTC

   All the systems are now fully operational.

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

1. resolved 2025-10-21 00:34 UTC

   This incident has been resolved.

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

1. resolved 2025-10-20 17:41 UTC

   The third party outage is now over and the situation is back to normal.

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

1. resolved 2025-10-21 08:09 UTC

   One of our partner is encountering issues which impact the fetch of the billing information for some of our customers. Billing status page may not be responding. Incident is on the way to be mitigated, we are still encountering some slowness and errors

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

1. resolved 2025-10-21 08:35 UTC

   All voice and SMS functionalities have been fully restored and are operating normally.

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

1. resolved 2025-10-15 16:48 UTC

   This incident has been resolved. All help center websites are back to normal.

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

1. resolved 2025-10-13 05:54 UTC

   All delayed data has been processed and the system is now stable.

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

1. resolved 2025-09-30 22:05 UTC

   We managed to identify and resolve the incident, all systems should now be operational

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

1. resolved 2025-09-29 13:03 UTC

   The incident has been fully resolved. Customer impact: New incoming emails via forwarding have been consistently ingested since the fix was deployed. Our team has completed the replay of previously affected emails, and all missed messages are now available in Gorgias. No further...

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

1. resolved 2025-09-28 21:57 UTC

   This incident has been resolved.

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

1. resolved 2025-09-26 20:02 UTC

   This incident has been resolved.

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

1. resolved 2025-09-25 22:32 UTC

   This incident has been resolved.

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

1. resolved 2025-09-25 16:39 UTC

   This incident has been resolved.

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

1. resolved 2025-09-24 12:54 UTC

   This incident has been resolved.

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

1. resolved 2025-09-24 01:48 UTC

   This incident has been resolved.

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

1. resolved 2025-09-22 18:45 UTC

   This incident has been resolved.

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

1. resolved 2025-09-18 20:42 UTC

   The issue is now solved. All the data is now in place and the Helpdesk is not impacted anymore.

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

1. resolved 2025-09-14 22:04 UTC

   We can now confirmed that users are no longer affected by this issue and as such the incident is now resolved. The incident would have affected most core aspects of the ticket pipeline on the cluster including: processing of rules, responses from AI Agent, as well as outbound...

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

1. resolved 2025-09-09 19:41 UTC

   Fix has been deployed to all clusters. Users are able to export ticket metrics drilldowns again.

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

1. resolved 2025-09-02 19:00 UTC

   This incident has been resolved.

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

1. resolved 2025-08-29 16:01 UTC

   We can confirm that the error rate has now dropped on this cluster and users should not be facing any issues here.

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

1. resolved 2025-08-29 11:58 UTC

   This incident has been resolved.

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

1. resolved 2025-08-27 09:50 UTC

   issue has been resolved

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

1. resolved 2025-08-21 09:55 UTC

   This incident has been resolved. All help center websites are back to normal.

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

1. resolved 2025-08-14 11:33 UTC

   This incident has been resolved.

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

1. resolved 2025-08-07 08:53 UTC

   This incident has been resolved. Pending postmortem analysis

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

1. resolved 2025-07-31 19:17 UTC

   This incident has been resolved.

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

1. resolved 2025-07-24 19:03 UTC

   The third party incident has been resolved, we're back to normal since for the past 30 minutes.

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

1. resolved 2025-07-23 10:08 UTC

   This incident has been resolved.

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

1. resolved 2025-07-18 18:29 UTC

   The third party incident has been resolved, and Gorgias services are back to normal since 17:00 UTC (10:00 PDT / 13:00 EDT / 19:00 CEST).

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

1. resolved 2025-07-21 07:52 UTC

   This incident has been resolved.

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

1. resolved 2025-07-17 10:33 UTC

   This incident has been resolved. All reporting dashboards are now working fine again.

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

1. resolved 2025-07-15 19:09 UTC

   The issue has been fully resolved. Message and ecommerce data processing is back to normal, and all previously delayed messages have been delivered to your helpdesk. Thank you for your patience!

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

1. resolved 2025-07-03 16:58 UTC

   We are pleased to inform you that the incident affecting AI Agent has been resolved. The issue was caused by a third-party outage, which resulted in a high handover rate. The third-party has since resolved the outage, and all services are now functioning normally. We appreciate...

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

1. resolved 2025-06-25 19:09 UTC

   We've identified and fixed the issue causing blank help center pages All help center pages should now be working normally Thank you for your patience while we resolved this issue.

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

1. resolved 2025-06-25 16:39 UTC

   A fix has been deployed, and normal functionality has been restored. To ensure everything works smoothly, please refresh your page.

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

1. resolved 2025-06-12 23:59 UTC

   This incident has been resolved.

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

1. resolved 2025-06-09 20:50 UTC

   This incident has been resolved.

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

1. resolved 2025-06-06 00:30 UTC

   Unfortunately because of an internal change we introduced a bug where we started importing new customers from Instagram DMs and Facebook Messenger with a placeholder name instead of their real name. The bug was identified and fixed, and we backfilled all the customers with their...

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

1. resolved 2025-06-04 15:34 UTC

   Help Center related issue has been resolved.

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

1. resolved 2025-05-31 05:17 UTC

   This incident has been resolved.

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

1. resolved 2025-05-28 07:20 UTC

   This incident has been resolved.

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

1. resolved 2025-05-27 17:49 UTC

   This incident has been resolved.

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

1. resolved 2025-05-27 16:52 UTC

   This incident has been resolved.

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

1. resolved 2025-05-28 10:47 UTC

   We are pleased to announce that the mitigation measures applied to address the recent connectivity issues impacting our AI Agent have been successful. Since implementing these changes, we have not observed any further occurrences of these issues. We will continue to monitor the...

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

1. resolved 2025-05-22 08:04 UTC

   The maintenance event that caused a database node to restart has been addressed. Our maintenance exclusion workaround is in place and is preventing other clusters from restarting unexpectedly. Everything is stable at this time. We will take the necessary steps to ensure this...

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

1. resolved 2025-05-20 19:42 UTC

   Between 5:00 PM and 6:00 PM UTC, a faulty deployment caused a failure in the rules responsible for auto-tagging tickets. As a result, some tickets may not have been auto-tagged as expected. We reverted the deployment to restore normal functionality. We apologize for any...

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

1. resolved 2025-05-17 14:19 UTC

   This incident has been resolved.

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

1. resolved 2025-05-12 11:02 UTC

   This incident has been resolved.

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

1. resolved 2025-05-12 08:00 UTC

   Between May 12 and May 14, 2025, a subset of Gorgias customers experienced an issue where Gorgias did not deliver emails sent or forwarded to specific email addresses to their helpdesks. A configuration change we made disabled our ability to receive emails from certain...

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

1. resolved 2025-05-01 20:14 UTC

   This incident has been resolved.

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

1. resolved 2025-04-15 10:00 UTC

   The issue with the billing process for Automate products has been resolved. The redeployment has been completed, and the system has successfully reprocessed all data to accurately calculate usage.

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

1. resolved 2025-04-08 20:15 UTC

   We sincerely apologize for the recent interruption you experienced with our Recommender service. Our team identified and addressed the high error rate that occurred earlier today. As of now, the service is fully operational. Thank you for your understanding and patience. We...

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

1. resolved 2025-04-07 21:43 UTC

   This incident has been resolved.

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

1. resolved 2025-04-01 19:59 UTC

   This incident has been resolved.

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

1. resolved 2025-03-31 17:31 UTC

   Our Phone provider has resolved this incident and we will continue to monitor status.

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

1. resolved 2025-03-29 10:36 UTC

   This incident has been resolved.

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

1. resolved 2025-03-28 18:31 UTC

   Standard voice integration settings page are operational again.

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

1. resolved 2025-03-14 22:15 UTC

   During the incident, we experienced increased latency in one of our internal services, leading to higher-than-usual AI Agent handovers. The issue has since been mitigated, and all services are back to normal.

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

1. resolved 2025-03-14 02:30 UTC

   The fix has been applied. All Auto QA scores are processed without any issues. We are still monitoring service.

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

1. resolved 2025-03-11 10:29 UTC

   This incident has been resolved.

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

1. resolved 2025-03-10 17:41 UTC

   This incident has been resolved.

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

1. resolved 2025-03-05 16:20 UTC

   This incident has been resolved.

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

1. resolved 2025-03-04 03:49 UTC

   This incident has been resolved.

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

1. resolved 2025-02-28 17:14 UTC

   We fixed the configuration issue. Everything is back to normal

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

1. resolved 2025-02-27 03:32 UTC

   This incident has been resolved.

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

1. resolved 2025-02-24 19:05 UTC

   This incident has been resolved.

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

1. resolved 2025-02-20 14:17 UTC

   This incident has been resolved.

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

1. resolved 2025-02-19 23:02 UTC

   This incident has been resolved.

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

1. resolved 2025-02-12 06:19 UTC

   This incident has been resolved, and all search features are functioning normally.

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

1. resolved 2025-02-08 07:12 UTC

   All data has been processed and statistics are now up-to-date

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

1. resolved 2025-02-07 16:08 UTC

   This incident has been resolved.

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

1. resolved 2025-01-29 23:31 UTC

   This incident has been resolved.

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

1. resolved 2025-02-03 10:19 UTC

   The incident now appears to be related only to Recharge’s analytics and not to updates, installations, or the API, so it should no longer affect Gorgias. We will continue to monitor the situation closely to ensure no issues arise on our side. For further updates on Recharge...

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

1. resolved 2025-01-22 21:08 UTC

   Incident Resolution Time: January 22, 2025, 5:52 PM UTC We are pleased to inform you that the incident affecting our email processing and automated features has been resolved. All delayed events have been successfully processed, and systems are now operating normally. We...

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

1. resolved 2025-01-13 13:20 UTC

   This incident has been resolved. We have discontinued directing sign-ups to https://www.gorgias.com/signup-2 due to issues. All users are now redirected to https://www.gorgias.com/signup, which is functioning correctly.

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

1. resolved 2025-01-08 16:31 UTC

   The fix that we applied is effective, the spike of events is gone, and all the systems are back to normal. The incident is now resolved.

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

1. resolved 2025-01-03 19:36 UTC

   This incident has been resolved.

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

1. resolved 2025-01-02 18:22 UTC

   This incident has been resolved.

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

1. resolved 2024-12-19 05:32 UTC

   This incident has been resolved. Customer search results are up- to-date

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

1. resolved 2024-12-17 07:19 UTC

   Meta resolved the incident on their end. Messages sent and received for Instagram DMs are now properly formatted.

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

1. resolved 2024-12-18 03:46 UTC

   This incident has been resolved.

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

Names an upstream provider: OpenAI.

1. resolved 2024-12-12 00:51 UTC

   This incident has been resolved.

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

1. resolved 2024-12-12 01:15 UTC

   Meta solved all incidents on their end and the traffic received in Gorgias indicates normal operations.

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

1. resolved 2024-11-28 14:00 UTC

   The AI Agent stopped processing tickets due to an internal system issue. The issue was resolved quickly, but reactivating the AI Agent on all accounts took some additional time.

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

1. resolved 2024-11-27 09:07 UTC

   This incident has been resolved.

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

1. resolved 2024-11-14 17:47 UTC

   This incident has been resolved.

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

1. resolved 2024-11-01 15:32 UTC

   This incident has been resolved.

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

1. resolved 2024-11-05 17:05 UTC

   This incident has been resolved.

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