Customer.ioIssue with downloading exports from our App API
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We have identified an issue with delays in email delivery. The emails are in our queues and not lost. We have fixed the issue. There is still some backed up email that we are delivering as quickly as possible.
Resolved
We have deployed a fix for the issue affecting recurring policy evaluations for EPM early-access customers. All delayed or missed evaluations have completed successfully.
Resolved
This incident is resolved. Our upstream AI provider has recovered and Content Agent and Canvas error rates have returned to normal.
Resolved
We understand how important this functionality is to your hiring workflows, and our team moved quickly to investigate and address the issue. We can confirm this issue has been fully resolved, and our team has taken steps to ensure system stability moving forward. ## Customer Impact * On January 6th, 2026, between 15:07 and 18:20 \(UTC\), users were **unable to upload resumes or documents** in Lever ATS. * Upload attempts failed with an authorization-related error. * Any new uploads during the incident window may result in references to non-existent files within the ATS. Unfortunately, these files are not recoverable. * Other areas of the application continued to function normally. ## Root Cause The incident was caused by an updated **configuration in Amazon S3 access policies** following a security-related infrastructure change. As part of a security initiative, an existing IAM policy condition was updated in accordance with an AWS-recommended best practice. While this change was intended to improve security, the revised policy **did not behave as expected in our environment**, resulting in S3 denying permission for file uploads. Because file uploads rely on this S3 permission, customers encountered authorization errors when uploading resumes and documents. ## Resolution Once the issue was identified, the infrastructure team **reverted the policy change** to the previously functioning configuration. After the rollback: * File uploads resumed successfully * Error rates returned to normal levels * Customer impact was fully resolved The system was verified as restored by confirming: * Successful resume uploads from the application * Elimination of S3 authorization errors in logs and dashboards Invalid file reference cleanup * Our Engineering teams are in the process of removing any invalid references to files that were not successfully uploaded during this time ## Preventative Actions To reduce the likelihood of similar issues in the future, we are implementing the following improvements: 1. **Post-Deployment Monitoring** * Enhanced monitoring after infrastructure and security-related changes in production 2. **Automated Alerts** * Alerts for elevated file-upload failures and S3 authorization errors to reduce detection time 3. **Change Validation** * Additional validation and testing of IAM policy changes, especially those involving AWS-recommended updates 4. **Documentation & Review** * Improved documentation and cross-team review for security-driven infrastructure changes These steps will help detect issues sooner and minimize customer impact in the event of future changes.
Resolved
This issue has been resolved
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
After monitoring the fix, we can confirm our team has resolved the disruption. We appreciate your patience and understanding with our team today as we worked to address this.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Between 3:14PM UTC to 3:28AM UTC, Notion's automations were not triggering as expected but this is now resolved.
Resolved
Apple has resolved their outage and builds are succeeding again.
Resolved
On January 15th, between 14:18 UTC and 15:26 UTC, customers experienced delays in status updates for workflow runs and checks. Status updates were delayed by up to 20 minutes, with a median delay of 11 minutes.<br /><br />The issue stemmed from an infrastructure upgrade to our database cluster. The new version introduced resource contention under production load, causing slow query times. We mitigated this by rolling back to the previous stable version. We are working to strengthen our upgrade validation process to catch issues that only manifest under high load. We are also adding new monitors to reduce detection time for similar issues in the future.
Resolved
This incident has been resolved.
Resolved
We see that the issue within our cloud provider’s infrastructure has been mitigated, and we can confirm that the infrastructure is healthy, and we are not seeing further errors. Throughout the degradation, our platform was able to maintain service continuity. We appreciate your patience and understanding while we coordinated our efforts with the cloud provider’s engineers to address the issue.
Resolved
The issue has been resolved. Foundational flows are now operating correctly as a GA feature. More details are available in https://gitlab.com/gitlab-org/gitlab/-/work_items/586912
Resolved
Error rates have stabilized. We are continuing to enhance LLM fallback coverage to improve system resilience and reduce the risk of single points of failure.
Resolved
We’ve resoled the issue affecting Core API and things are back to normal.
Resolved
On January 20, 2026, some customers may have experienced performance degradation of Assets. The issue has now been resolved, and the service is operating normally for all affected customers.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue within our cloud provider’s infrastructure has been mitigated, and we can confirm that all affected resources have been fully restored. Our platform has remained available throughout, thanks to built-in redundancy and failover across multiple locations. While parts of the underlying infrastructure were experiencing problems, we continued to serve traffic and deliver the service without a full outage. Thank you for your patience and understanding while we coordinated our efforts with cloud provider’s engineers to address the issue.
Resolved
The issue with 500 errors for some users accessing the 'candidates' tab has been resolved. The incident occurred from 8 am Pacific time until 9 am Pacific time. No further action will be required from impacted users to have restored functionality. There should be no further impact at this time, but please reach out to us at Support if any additional assistance is needed: https://help.lever.co/hc/en-us/requests/new
Resolved
We have started to receive messages with attachments/media from WhatsApp again. New inbound messages containing media, such as images, audio, or attachments, will be delivered successfully to the Helpdesk. Any messages that failed to deliver attachments previously will need to be sent again. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
We have started to receive messages with attachments/media from WhatsApp again. New inbound messages containing media, such as images, audio, or attachments, will be delivered successfully to the Helpdesk. Any messages that failed to deliver attachments previously will need to be sent again. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
We have started to receive messages with attachments/media from WhatsApp again. New inbound messages containing media, such as images, audio, or attachments, will be delivered successfully to the Helpdesk. Any messages that failed to deliver attachments previously will need to be sent again. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
Between 11:47 AM (UTC -05:00) and 01:05 PM (UTC -05:00), customers in all regions experienced issues loading app cards and UI extensions in HubSpot. This was caused by a load balancer misconfiguration. As of 01:05 PM (UTC -05:00), our app cards and UI extensions are working properly and the incident has been fully resolved. No data was lost. HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability. The information on this page reflects our understanding of the incident and impact at the time of the update.
Resolved
This incident is resolved. Our upstream AI provider has recovered, and Content Agent and Canvas error rates have returned to normal.
Resolved
The incident has been fully resolved
Resolved
For the past 40min, we observed elevated rates of 403 errors across Langfuse Cloud APIs, mainly the prompt API route. As a follow-up to previous CloudFlare incidents (https://status.langfuse.com/incidents/01KAGW71ZPD2WTXCFZQBGV7EHH) we moved away from CloudFlare and route messages directly to our Application LoadBalancers. As a measure to enhance loading times, we've added a CloudFront distribution in front of our LoadBalancer. The CloudFront distributions went live around 4pm UTC and initially, we saw now unexpected rise in 5xx errors which we were actively monitoring. Once customer complaints about elevated 403 rates, we reverted the change and restored service for all of them. The root cause is a behaviour in CloudFront that automatically rejects all GET requests with a non-empty request body with a 403 Forbidden code. Parts of the auto-generated clients in our SDKs add `{}` as a request_body if request_options, e.g. a timeout is configured. We're currently investigating alternative options to improve first-time load speeds globally for Langfuse Cloud. We apologize for any inconvenience caused.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Communication is fully restored now.
Resolved
We are glad to inform you that the fix has been implemented and the incident resolved. The incident occurred today between 2:46 PM and 3:44 PM GMT+1. We will run a problem investigation to understand what happened and how to prevent it from happening again. Thanks for your understanding & sorry for any inconvenience this has caused.
Resolved