Resolved -
A transient network issue has been resolved, and all queued requests have been processed. All services are now operational.
Jul 22, 13:13 UTC
Monitoring -
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 database is now operational, and the service has been restored.
Jul 22, 12:51 UTC
Investigating -
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.
Jul 22, 12:35 UTC
Resolved -
This incident has been resolved.
Jul 17, 13:27 UTC
Monitoring -
We deployed a fix to solve the Store website sync issues. We are monitoring the situation.
Jul 17, 12:01 UTC
Identified -
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.
Jul 16, 11:13 UTC
Investigating -
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.
Jul 15, 10:18 UTC
Resolved -
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 to one data-center zone. This was an underlying infrastructure issue, not a Gorgias application problem or a change on our side.
Resolution: Our systems recovered automatically via built-in failover. No data was lost and no manual intervention was needed.
Next steps: We'll be reviewing the incident with our cloud provider and evaluating measures to further strengthen resilience against this class of issue.
We apologize for the disruption, you can reach out to your support contact with any questions.
Jul 17, 01:43 UTC
Resolved -
This incident has been resolved.
Jul 16, 14:26 UTC
Investigating -
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.
Jul 16, 13:56 UTC
Resolved -
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 guidance) when composing answers, and could respond based on conversation context alone. Some intent-based automations (rules and routing) were also intermittently affected.
Jul 15, 16:42 UTC