Is there an Gorgias outage?
Gorgias status: Systems Active
Last checked: 3 minutes ago
Get notified about any outages, downtime or incidents for Gorgias and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 3 minutes ago
Get notified about any outages, downtime or incidents for Gorgias and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Gorgias.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Website | Active |
| Automate | Active |
| AI Agent | Active |
| Flows | Active |
| Order Management | Active |
| Convert | Active |
| Campaigns | Active |
| Help Center | Active |
| Custom Domains | Active |
| Customer Help Center website | Active |
| REST API | Active |
| Helpdesk | Active |
| Mobile Apps | Active |
| REST API | Active |
| Web App | Active |
| Helpdesk Clusters | Active |
| aus-southeast1-fcb9 | Active |
| europe-west1-c511 | Active |
| europe-west3-86c1 | Active |
| us-central1-c433 | Active |
| us-central1-d8ff | Active |
| us-east1-2607 | Active |
| us-east1-635c | Active |
| us-east1-c94b | Active |
| us-east4-5f09 | Active |
| us-east4-65cd | Active |
| Helpdesk Integrations | Active |
| Aircall Aircall Apps | Active |
| Aircall Public API | Active |
| Active | |
| Facebook Messenger | Active |
| Facebook Posts & Comments | Active |
| Gmail | Active |
| Instagram comments | Active |
| Instagram Direct Messages | Active |
| Live Chat | Active |
| Mailgun API | Active |
| Mailgun inbound email | Active |
| Mailgun outbound email | Active |
| Mailgun SMTP | Active |
| Native Phone | Active |
| Outlook | Active |
| ReCharge integration | Active |
| Shopify API & Mobile | Active |
| Shopify integration | Active |
| Smooch Core API | Active |
| SMS | Active |
| Stripe API | Active |
| Active | |
| Active | |
| Yotpo | Active |
| Infrastructure & Cloud | Active |
| Google Cloud Platform Google Cloud DNS | Active |
| Google Cloud Platform Google Cloud Networking | Active |
| Google Cloud Platform Google Cloud Pub/Sub | Active |
| Google Cloud Platform Google Cloud SQL | Active |
| Google Cloud Platform Google Cloud Storage | Active |
| Google Cloud Platform Google Compute Engine | Active |
| Google Cloud Platform Google Container Engine | Active |
| Google Cloud Platform Google Kubernetes Engine | Active |
View the latest incidents for Gorgias and check for official updates:
Description: The system is still impacted and we are still trying to resolve the issue with Meta technical support. We will have another update in the morning.
Status: Investigating
Impact: Major | Started At: Aug. 31, 2024, 4:07 p.m.
Description: **Incident Summary: WhatsApp Integration Outage \(August 30 - September 4, 2024\)** **Incident Timeline:** * **Start:** August 30, 2024, 16:56 UTC * **Resolution:** September 4, 2024, 10:42 UTC **What Happened:** On August 30, 2024, at 16:56 UTC, our systems stopped receiving notifications for new WhatsApp messages, meaning inbound WhatsApp messages for integrated phone numbers would no longer flow into Gorgias. At the same time, our customers began encountering errors when trying to reply in WhatsApp tickets, receiving a message that read: "\(#200\) You do not have permission to access this field". The first customer reports started arriving around August 30, 17:30 UTC, and our engineering team began investigating the issue after an alert was triggered at 19:14 UTC because of the missing notifications. Initial checks confirmed that the issue was affecting all customers, leading to a complete outage of our WhatsApp integration. We immediately reached out to Meta’s support team to understand what was causing the problem while continuing our internal investigation. **Investigation and Challenges:** The error message suggesting that we lacked permission to create messages indicated that something might have gone wrong with our app's permissions in Meta’s systems. We checked all available resources, including Meta’s changelogs, status pages, and developer community posts, but found no changes or incidents that could explain the issue. We even posted on Meta’s developer forums to see if other developers were experiencing similar issues. Our attempts to investigate the problem via Meta’s developer and business platforms yielded no results—there were no warnings, notifications, or indicators suggesting something was wrong with our app or business account. At 22:08 UTC on August 30, after exhausting initial troubleshooting options, we paused the investigation for the day, waiting for a response from Meta’s support team while continuing to monitor the situation. Over the weekend, we maintained communication with Meta and provided any information requested in an attempt to escalate the issue, but the responses we received did not help us resolve the problem. Note: during this time, we continued to provide regular updates on our status page. However, due to an issue with our internal tooling, the incident was accidentally duplicated. When we deleted the duplicate on September 2, all messages posted during that period were removed as well. This is why there is a “hole” in the history of updates during that time. **Discovering the Cause:** By September 2, having received no relevant updates from Meta, we revisited our investigation and discovered a potential cause: our app was missing the advanced whatsapp\_business\_messaging permission, which [Meta’s documentation](https://developers.facebook.com/docs/whatsapp/embedded-signup/app-review/) states is required for Cloud Solution Partners. This was the first indication that this permission might be related to the issue, although the consequences of missing it were not clearly explained. We had never had this advanced permission in the past, only standard access, and our app had worked without issue up until August 30. Despite the uncertainty about whether this was the cause, we submitted a request for the advanced permission on September 2 at 11:04 UTC. Unfortunately, our request was rejected a few hours later. Since there was no confirmation that this permission was the root cause of the issue, we temporarily set aside the request while continuing our dialogue with Meta. **Escalation and Resolution:** On September 3, at 19:13 UTC, we submitted another request for the advanced whatsapp\_business\_messaging permission, but this was rejected as well. By September 4, at 08:37 UTC, we submitted yet another request with the additional information Meta required. This time, the request was approved at 10:42 UTC on September 4, and immediately after, inbound notifications resumed, and the errors our customers were experiencing stopped. **Ongoing Efforts:** Following the resolution, we continued to communicate with Meta to understand why the absence of this advanced permission, suddenly caused a complete outage. We also asked Meta if it would be possible to recover the messages that were missed during the outage by replaying the related notifications, or if there were any other options for the recovery. Meta initially responded that this was not possible. We followed up with another request, asking for further details as to why Meta’s systems seem to lack the ability to replay these notifications, but we have not yet received a response. As of September 12, 2024, we are waiting for further clarification from Meta. **Impact on Customers:** * From August 30, 16:56 UTC to September 4, 10:42 UTC, customers were unable to receive or send WhatsApp messages through Gorgias. * This impacted all customers using our WhatsApp integration, and new messages were not processed by our system during this period. * As of our current knowledge, it is not possible to recover the messages that were missed during the time of the incident. **Actions Taken:** * We immediately investigated the issue and reached out to Meta’s support team. * We attempted multiple escalations with Meta to get the issue resolved but were ultimately left to discover the root cause independently. * After identifying that the whatsapp\_business\_messaging permission might be required, we requested and gained approval for the permission, which restored full functionality. **Next Steps:** We are continuing to engage with Meta to understand why this permission became necessary unexpectedly and why there were no clear warnings in Meta’s systems about its importance. We are also investigating ways to prevent similar incidents in the future by improving our monitoring systems and ensuring quicker escalation paths. Additionally, we will continue seeking ways to recover the missed WhatsApp messages. We apologize for the inconvenience this incident has caused and appreciate your patience as we worked to resolve the issue. We are committed to preventing similar disruptions moving forward.
Status: Postmortem
Impact: Major | Started At: Aug. 30, 2024, 8:05 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Aug. 16, 2024, 8:02 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Aug. 16, 2024, 12:48 a.m.
Description: We experienced a short outage that affected 5 different regions(us-east4-65cd, aus-southeast1-fcb9, europe-west1-c511, us-central1-c433 and us-central1-d8ff), resulting in Helpdesk downtime in corresponding clusters. After investigating, our team identified that this was caused by an unannounced change from one of our infrastructure providers. The incident has been resolved and we are in communication with the provider to prevent future occurrences.
Status: Resolved
Impact: Major | Started At: Aug. 6, 2024, 4:30 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
