Unbabel Site - Operational
Unbabel Site
Unbabel Portal - Operational
Unbabel Portal
Projects - Operational
Projects
Client Review - Operational
Client Review
Salesforce KB - Operational
Zendesk Guide - Operational
Zendesk Support/Agent Workspace - Operational
Zendesk Support/Agent Workspace
Freshdesk - Operational
Salesforce Service Cloud - Operational
Unbabel Interface Tickets - Operational
Wix Answers - Operational
Kustomer - Operational
Helpshift Emails - Operational
Helpshift Emails
Ticket API - Operational
Ticket API
Zendesk Chat - Operational
Intercom - Operational
Salesforce Messaging - Operational
Salesforce Messaging
Unbabel Interface Chat - Operational
Kustomer - Operational
Kustomer
Helpshift Chat - Operational
Helpshift Chat
Chat API - Operational
Chat API
Editor Dashboard - Operational
Editor Dashboard
Polyglot - Operational
Polyglot
Notice history
View current statusNov 2025
- Resolved · UTC
We're operating as usual and you can now resume using the customer.happiness@unbabel.com email address to reach out to us. Thank you for bearing with us
- Identified · UTC
We are currently experiencing issues with customer.happiness@unbabel.com email, please reach out to us via support@cxunbabel.zendesk.com or submit a ticket here: https://customer-happiness.unbabel.com/hc/en-us/requests/new
Oct 2025
- Resolved · UTCThis incident has been resolved.
- Monitoring · UTC
With the recovery of AWS systems, Unbabel is restoring its capacity. Currently most systems are operational, with some delays still taking place for messages lost in the process and that may need recovering.
AWS Update: Oct 20 12:15 PM PDT We continue to observe recovery across all AWS services, and instance launches are succeeding across multiple Availability Zones in the US-EAST-1 Regions. For Lambda, customers may face intermittent function errors for functions making network requests to other services or systems as we work to address residual network connectivity issues. To recover Lambda’s invocation errors, we slowed down the rate of SQS polling via Lambda Event Source Mappings. We are now increasing the rate of SQS polling as we experience more successful invocations and reduced function errors. We will provide another update by 1:00 PM PDT.
- Update · UTC
AWS update - "We continue to apply mitigation steps for network load balancer health and recovering connectivity for most AWS services. Lambda is experiencing function invocation errors because an internal subsystem was impacted by the network load balancer health checks. We are taking steps to recover this internal Lambda system. For EC2 launch instance failures, we are in the process of validating a fix and will deploy to the first AZ as soon as we have confidence we can do so safely." - https://health.aws.amazon.com/health/status
- Identified · UTC
We are currently working to restore the service.
- Resolved · UTC
Our services are fully recovered. We will keep monitoring for the next few hours.
- Monitoring · UTC
AWS is recovering and we are seeing significant signs of improvement.
- Identified · UTC
We are being impacted by this AWS incident - https://health.aws.amazon.com/health/status
The team is trying to recover the services as soon as possible.
- Investigating · UTC
We are currently investigating this incident.

