Monitoring - 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 duplicates.
Current status:
The underlying issue is resolved and normal WhatsApp message processing has resumed. We are investigating the billing impact for affected accounts.
Impact:
- Closed WhatsApp tickets reopened unexpectedly, with older messages added to them.
- Some accounts may have had new or duplicate tickets created during the affected window.
- Ticket counts during that period may have been inflated, which could affect billing. We are reviewing this.
What to know:
We did not close or merge affected tickets ourselves. Deciding which ticket to keep depends on your workflow, and we can't make that call for you. Some merchants have also already cleaned up the data on their end, so running an automated cleanup risked overwriting changes you'd made or leaving you with a state you didn't want.
Use the filters below to find the duplicated and newly created tickets, then bulk-close them as appropriate.
How to identify affected (duplicated/created) tickets:
Apply these filters in your helpdesk. All times are UTC, so convert to your helpdesk timezone:
- Channel: WhatsApp
- Created before: August 10, 2026 at 20:30 UTC
- Created after: August 10, 2026 at 16:00 UTC
- Last shopper message received: between July 23, 2026 at 17:00 UTC and August 10, 2026 at 18:00 UTC
- Status: Open (or other status filters relevant to your workflow)
Billing:
We are working to remove the tickets created by this incident from your billing. We will follow up once this is complete.
Aug 11, 2026 - 14:31 UTC
Current status:
The underlying issue is resolved and normal WhatsApp message processing has resumed. We are investigating the billing impact for affected accounts.
Impact:
- Closed WhatsApp tickets reopened unexpectedly, with older messages added to them.
- Some accounts may have had new or duplicate tickets created during the affected window.
- Ticket counts during that period may have been inflated, which could affect billing. We are reviewing this.
What to know:
We did not close or merge affected tickets ourselves. Deciding which ticket to keep depends on your workflow, and we can't make that call for you. Some merchants have also already cleaned up the data on their end, so running an automated cleanup risked overwriting changes you'd made or leaving you with a state you didn't want.
Use the filters below to find the duplicated and newly created tickets, then bulk-close them as appropriate.
How to identify affected (duplicated/created) tickets:
Apply these filters in your helpdesk. All times are UTC, so convert to your helpdesk timezone:
- Channel: WhatsApp
- Created before: August 10, 2026 at 20:30 UTC
- Created after: August 10, 2026 at 16:00 UTC
- Last shopper message received: between July 23, 2026 at 17:00 UTC and August 10, 2026 at 18:00 UTC
- Status: Open (or other status filters relevant to your workflow)
Billing:
We are working to remove the tickets created by this incident from your billing. We will follow up once this is complete.
Aug 11, 2026 - 14:31 UTC
About This Site
Below are Gorgias basic performance stats of our main services + incident reports. Feel free to subscribe to get updates.
Automate
Operational
AI Agent
Operational
Flows
Operational
Order Management
Operational
Helpdesk
Operational
REST API
Operational
Web App
Operational
Mobile Apps
Operational
Helpdesk Integrations
Operational
Email
Operational
Mailgun SMTP
Operational
Mailgun inbound email
Operational
Mailgun outbound email
Operational
Mailgun API
Operational
Gmail
Operational
Outlook
Operational
Live Chat
Operational
Smooch Core API
Operational
Facebook Posts & Comments
Operational
Instagram comments
Operational
Shopify integration
Operational
Shopify API & Mobile
Operational
Aircall Public API
Operational
Aircall Aircall Apps
Operational
Stripe API
Operational
Facebook Messenger
Operational
ReCharge integration
Operational
Native Phone
Operational
Instagram Direct Messages
Operational
Yotpo
Operational
SMS
Operational
Twitter
Operational
WhatsApp
Operational
Helpdesk Clusters
Operational
us-east1-635c
Operational
us-east4-65cd
Operational
us-east1-2607
Operational
aus-southeast1-fcb9
Operational
europe-west3-86c1
Operational
us-central1-d8ff
Operational
us-east4-5f09
Operational
europe-west1-c511
Operational
us-central1-c433
Operational
us-east1-c94b
Operational
europe-west4-e7f4
Operational
Help Center
Operational
REST API
Operational
Customer Help Center website
Operational
Custom Domains
Operational
Infrastructure & Cloud
Operational
Google Cloud Platform Google Container Engine
Operational
Google Cloud Platform Google Cloud Storage
Operational
Google Cloud Platform Google Kubernetes Engine
Operational
Google Cloud Platform Google Compute Engine
Operational
Google Cloud Platform Google Cloud Networking
Operational
Google Cloud Platform Google Cloud Pub/Sub
Operational
Google Cloud Platform Google Cloud DNS
Operational
Google Cloud Platform Google Cloud SQL
Operational
Website
Operational
Convert
Operational
Campaigns
Operational
Chargebee API (US)
Operational
Chargebee API (EU)
Operational
Chargebee API (AU)
Operational
Chargebee Admin Console (US)
Operational
Chargebee Admin Console (EU)
Operational
Chargebee Admin Console (AU)
Operational
Chargebee Accounting Services
Operational
Chargebee Reporting and Analytics
Operational
Chargebee RevRec Portal
Operational
Chargebee Anrok
Operational
Chargebee Webhooks (US)
Operational
Chargebee Webhooks (EU)
Operational
Chargebee Webhooks (AU)
Operational
Chargebee Email Notifications (US)
Operational
Chargebee Email Notifications (EU)
Operational
Chargebee Email Notifications (AU)
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.