Gorgias Outage History

Gorgias is up right now

Gorgias had 59 outages in the last 2 years totaling 98h 26m of downtime — averaging 2.4 incidents per month.

There were 59 Gorgias outages since October 15, 2025 totaling 98h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.gorgias.io

Major June 12, 2026

WhatsApp, Instagram and Facebook messages might be delayed

Detected by Pingoru
Jun 12, 2026, 02:27 PM UTC
Resolved
Jun 12, 2026, 06:29 PM UTC
Duration
4h 2m
Affected: Facebook MessengerInstagram Direct MessagesWhatsApp
Timeline · 4 updates
  1. identified Jun 12, 2026, 02:27 PM UTC

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

  2. identified Jun 12, 2026, 02:28 PM UTC

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

  3. monitoring Jun 12, 2026, 02:58 PM UTC

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

  4. resolved Jun 12, 2026, 06:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 11, 2026

Delays in HTTP integrations for some accounts

Detected by Pingoru
Jun 11, 2026, 09:44 PM UTC
Resolved
Jun 11, 2026, 10:18 PM UTC
Duration
34m
Timeline · 3 updates
  1. identified Jun 11, 2026, 09:44 PM UTC

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

  2. monitoring Jun 11, 2026, 10:14 PM UTC

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

  3. resolved Jun 11, 2026, 10:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 7, 2026

Elevated latency in ecommerce data processing on the Australian region

Detected by Pingoru
Jun 07, 2026, 06:03 AM UTC
Resolved
Jun 07, 2026, 06:39 AM UTC
Duration
36m
Affected: aus-southeast1-fcb9
Timeline · 3 updates
  1. investigating Jun 07, 2026, 06:03 AM 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, ecommerce data (orders, customer events, and related updates) may be delayed by up to ~1 hour compared to real-time for affected customers. No data loss is expected — messages are queued and being processed. The backlog is actively draining and we are monitoring the situation closely. We will provide an update once processing has returned to normal. We apologize for the inconvenience.

  2. investigating Jun 07, 2026, 06:10 AM UTC

    We are continuing to investigate this issue.

  3. resolved Jun 07, 2026, 06:39 AM 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.

Read the full incident report →

Minor June 5, 2026

Customer data in cluster us-east4-5f09 has lag

Detected by Pingoru
Jun 05, 2026, 01:50 PM UTC
Resolved
Jun 05, 2026, 02:20 PM UTC
Duration
30m
Timeline · 2 updates
  1. monitoring Jun 05, 2026, 01:50 PM 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 Jun 05, 2026, 02:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 4, 2026

brief delay in subscription & invoice updates

Detected by Pingoru
Jun 04, 2026, 04:06 PM UTC
Resolved
Jun 05, 2026, 11:25 AM UTC
Duration
19h 19m
Affected: EmailChargebee Accounting Services
Timeline · 7 updates
  1. identified Jun 04, 2026, 04:06 PM 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 Jun 04, 2026, 04:51 PM UTC

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

  3. monitoring Jun 04, 2026, 04:52 PM 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 delayed updates are being processed automatically. A fix is currently rolling out, and we're monitoring the system until the issue is fully resolved.

  4. identified Jun 04, 2026, 08:37 PM 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 Jun 04, 2026, 08:37 PM 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 Jun 04, 2026, 08:43 PM 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 Jun 05, 2026, 11:25 AM UTC

    This incident has been resolved. All events have been recovered

Read the full incident report →

Major May 27, 2026

AI Agent degraded performance

Detected by Pingoru
May 27, 2026, 03:28 PM UTC
Resolved
May 28, 2026, 06:07 AM UTC
Duration
14h 38m
Affected: AI Agent
Timeline · 3 updates
  1. identified May 27, 2026, 03:28 PM UTC

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

  2. monitoring May 27, 2026, 04:52 PM 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 May 28, 2026, 06:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 27, 2026

AI Agent - Too many handovers

Detected by Pingoru
May 27, 2026, 02:20 PM UTC
Resolved
May 27, 2026, 06:02 PM UTC
Duration
3h 41m
Affected: AI Agent
Timeline · 4 updates
  1. investigating May 27, 2026, 02:20 PM 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 May 27, 2026, 02:25 PM 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 May 27, 2026, 02:34 PM 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 May 27, 2026, 06:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 21, 2026

Some merchands are reporting orders missing from the widgets / search

Detected by Pingoru
May 21, 2026, 02:24 PM UTC
Resolved
May 21, 2026, 04:03 PM UTC
Duration
1h 39m
Affected: Shopify integration
Timeline · 3 updates
  1. investigating May 21, 2026, 02:24 PM UTC

    We are currently investigating this issue.

  2. identified May 21, 2026, 02:40 PM UTC

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

  3. resolved May 21, 2026, 04:03 PM UTC

    Incident is resolved.

Read the full incident report →

Major May 21, 2026

Ticket Search is delaying on one of the helpdesk cluster

Detected by Pingoru
May 21, 2026, 07:21 AM UTC
Resolved
May 21, 2026, 08:41 AM UTC
Duration
1h 19m
Affected: europe-west4-e7f4
Timeline · 3 updates
  1. investigating May 21, 2026, 07:21 AM UTC

    We are currently investigating this issue.

  2. monitoring May 21, 2026, 08:12 AM UTC

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

  3. resolved May 21, 2026, 08:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 18, 2026

Ticket view count is not updating on some accounts.

Detected by Pingoru
May 18, 2026, 02:47 AM UTC
Resolved
May 18, 2026, 05:32 AM UTC
Duration
2h 45m
Timeline · 3 updates
  1. investigating May 18, 2026, 02:47 AM UTC

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

  2. identified May 18, 2026, 03:46 AM 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 May 18, 2026, 05:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 7, 2026

Delayed or missing view counts

Detected by Pingoru
May 07, 2026, 02:24 AM UTC
Resolved
May 07, 2026, 04:01 AM UTC
Duration
1h 36m
Affected: Web Appaus-southeast1-fcb9
Timeline · 4 updates
  1. investigating May 07, 2026, 02:24 AM UTC

    We are currently investigating this issue.

  2. identified May 07, 2026, 02:43 AM UTC

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

  3. monitoring May 07, 2026, 03:53 AM UTC

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

  4. resolved May 07, 2026, 04:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 6, 2026

Delayed ticket search results

Detected by Pingoru
May 06, 2026, 06:34 AM UTC
Resolved
May 06, 2026, 07:22 AM UTC
Duration
47m
Affected: Web Appeurope-west4-e7f4
Timeline · 3 updates
  1. investigating May 06, 2026, 06:34 AM UTC

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

  2. monitoring May 06, 2026, 07:00 AM UTC

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

  3. resolved May 06, 2026, 07:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 24, 2026

Account signup form reports errors

Detected by Pingoru
Apr 24, 2026, 02:58 PM UTC
Resolved
Apr 24, 2026, 03:50 PM UTC
Duration
51m
Timeline · 3 updates
  1. investigating Apr 24, 2026, 02:58 PM UTC

    We are currently investigating this issue.

  2. monitoring Apr 24, 2026, 03:24 PM UTC

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

  3. resolved Apr 24, 2026, 03:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 17, 2026

Message processing has been restored across all affected services

Detected by Pingoru
Apr 17, 2026, 07:07 AM UTC
Resolved
Apr 17, 2026, 11:15 AM UTC
Duration
4h 8m
Affected: us-east1-635c
Timeline · 5 updates
  1. investigating Apr 17, 2026, 07:07 AM 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 Apr 17, 2026, 07:45 AM 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 Apr 17, 2026, 10:18 AM 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 Apr 17, 2026, 10:47 AM 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 once e-commerce data is fully up to date. Thank you for your patience.

  5. resolved Apr 17, 2026, 11:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 9, 2026

No live updates on some Helpdesks hosted in Europe

Detected by Pingoru
Apr 09, 2026, 10:42 AM UTC
Resolved
Apr 09, 2026, 11:24 AM UTC
Duration
41m
Timeline · 2 updates
  1. investigating Apr 09, 2026, 10:42 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 09, 2026, 11:24 AM 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.

Read the full incident report →

Major April 6, 2026

Customers' search not up to date

Detected by Pingoru
Apr 06, 2026, 10:42 PM UTC
Resolved
Apr 07, 2026, 04:32 AM UTC
Duration
5h 49m
Affected: us-central1-d8ff
Timeline · 4 updates
  1. investigating Apr 06, 2026, 10:42 PM 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 appear correctly in search results. We will provide an update as soon as more information is available. Thank you for your patience.

  2. identified Apr 07, 2026, 01:47 AM 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 appear correctly in search results. We will provide an update as soon as more information is available. Thank you for your patience.

  3. monitoring Apr 07, 2026, 02:56 AM UTC

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

  4. resolved Apr 07, 2026, 04:32 AM 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.

Read the full incident report →

Major April 3, 2026

Automation Rules Not Triggering

Detected by Pingoru
Apr 03, 2026, 12:46 PM UTC
Resolved
Apr 03, 2026, 04:25 PM UTC
Duration
3h 39m
Timeline · 3 updates
  1. identified Apr 03, 2026, 12:46 PM UTC

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

  2. monitoring Apr 03, 2026, 12:52 PM UTC

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

  3. resolved Apr 03, 2026, 04:25 PM UTC

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

Read the full incident report →

Major March 26, 2026

AI Agent not processing email tickets

Detected by Pingoru
Mar 26, 2026, 04:00 PM UTC
Resolved
Mar 26, 2026, 04:38 PM UTC
Duration
38m
Affected: AI Agent
Timeline · 3 updates
  1. investigating Mar 26, 2026, 04:00 PM 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 normal automation. In the meantime, agents may need to manually triage and assign impacted tickets. We will post updates as we have more information.

  2. identified Mar 26, 2026, 04:25 PM UTC

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

  3. resolved Mar 26, 2026, 04:38 PM UTC

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

Read the full incident report →

Major March 20, 2026

AI Agent and Automation analytics are delayed

Detected by Pingoru
Mar 20, 2026, 03:55 PM UTC
Resolved
Mar 20, 2026, 07:22 PM UTC
Duration
3h 26m
Affected: AI Agent
Timeline · 3 updates
  1. investigating Mar 20, 2026, 03:55 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 20, 2026, 05:47 PM UTC

    We are currently investigating this issue.

  3. resolved Mar 20, 2026, 07:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 17, 2026

Issues with Rule Execution and delivery of messages on europe-west4-e7f4

Detected by Pingoru
Mar 17, 2026, 12:31 PM UTC
Resolved
Mar 17, 2026, 02:37 PM UTC
Duration
2h 5m
Affected: europe-west4-e7f4
Timeline · 5 updates
  1. investigating Mar 17, 2026, 12:31 PM UTC

    We are currently investigating a disruption affecting our ticketing workflow. This issue is causing delays in the ticket pipeline for the "europe-west4-e7f4" cluster and is preventing outbound customer messages from being delivered, and rules from being executed for some users. Our engineering team is actively investigating and monitoring the system.

  2. investigating Mar 17, 2026, 01:01 PM UTC

    We're continuing to investigate the issue and can confirm that the impact also extends towards the synchronisation of data across our integrations (including messaging channels such as gmail). We apologize for the inconvenience caused and are actively looking towards resolving the behavior.

  3. identified Mar 17, 2026, 01:35 PM UTC

    Our team was able to identify the issue as being associated to the freezing our asynchronous message broker that was leading to us being unable to process any incoming traffic from our integrations as well as execute actions on the ticket pipeline. We've now unblocked the processing of the queues and are actively monitoring the progress of the recovery.

  4. monitoring Mar 17, 2026, 01:48 PM UTC

    We can confirm that our systems are now running as expected. Our team is continuing to monitor the issue and also analyzing any eventual loss to initiate the appropriate recovery protocols.

  5. resolved Mar 17, 2026, 02:37 PM 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.

Read the full incident report →

Major March 9, 2026

The chat application is unavailable

Detected by Pingoru
Mar 09, 2026, 06:07 PM UTC
Resolved
Mar 09, 2026, 06:40 PM UTC
Duration
32m
Affected: Live Chat
Timeline · 3 updates
  1. investigating Mar 09, 2026, 06:07 PM UTC

    The chat application is currently unavailable for most shoppers. The team is looking into the issue.

  2. monitoring Mar 09, 2026, 06:14 PM UTC

    The issue has been resolved, and the chat is functioning normally again. We will continue to monitor the situation.

  3. resolved Mar 09, 2026, 06:40 PM UTC

    This incident has been resolved.

Read the full incident report →