This incident has been resolved.
Learn more about here https://composio.dev/blog/composio-may-2026-security-incident
Slack triggers should now be back up again! We're now seeing near full recovery for slack triggers as slack systems come back online: https://slack-status.com/2026-05/fe557ca05fdb64fa
Slack's systems are still degraded (https://slack-status.com/2026-05/fe557ca05fdb64fa). But, we are seeing some early signs of recovery on slack's end, the ingress volume is still unstable and fluctuating rapidly. Webhook deliveries may be delayed or missed. We are closely monitoring the situation.
We have confirmed that our systems are operational, but we are experiencing issues on slack events ingress due to an ongoing slack outage: https://slack-status.com/2026-05/fe557ca05fdb64fa. We are closely monitoring the situation and will update as things progress on slack's end.
We are currently investigating an incident impacting slack triggers on the platform
X suspended Composio's app on February 9, 2026, due to platform policy enforcement. Users should use their own X developer credentials going forward.
Full incident report and root cause analysis: https://composio.dev/blog/incident-report-february-9-2026
X (Twitter) has suspended our composio managed X credentials
We are in touch with support to resolve this issue but the lead time is not clear, we highly recommend using your own credentials to continue without disruption
We are currently investigating this incident.
You can use your own custom credentials
This incident has been resolved. Functionality at our cloud provider has been restored. We sincerely thank you for your patience and we continue to actively monitor the situation.
We have noticed a significant decrease in 5xx errors. We will continue to monitor the situation.
We're experiencing 5xx elevated error rate due to AWS us-east-1 outage.
https://health.aws.amazon.com/health/status
> Oct 20 10:03 AM PDT 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. We will provide an update by 10:45 AM PDT.
This incident has been resolved. All systems are functional. Thank you for your patience.
We've an update from AWS. Systems are working as expected. We're monitoring.
We've identified Operational issues with our hosting provider (AWS). We're monitoring the progress of their status page.
https://health.aws.amazon.com/health/status
We're currently investigating why production is not responding
This incident has been resolved. All services from Google are now working as expected.
Google has temporarily restricted our default auth config. We're actively working with their team to resolve this issue.
What's Available Now
We've deployed new credentials for our google default apps so if you make new auth configs you can continue building, we know this is limiting but this is a first solution. These temporary credentials have some limitations, they don't support google's sensitive scopes which include actions like
- Deleting emails
- Accessing other contacts
- Google Drive search
We're collaborating with Google to restore sensitive scope support as quickly as possible.
Additionally, we are actively working on a solution to allow users to continue working without any disruption.
For production environments, we strongly recommend using custom auth configurations. Users with custom auth are not experiencing any issues and have full scope access.
Learn more: https://docs.composio.dev/docs/custom-auth-configs
We are currently investigating an outage with a 3rd party dependency that is causing Composio to be down.
The underlying incident from our service providers in AWS, and CF has been resolved
While we continue to monitor ongoing incidents, we request our customers to use tentative Composio backend url, for continued usage of actions: https://apollo-composio.vercel.app/
We are closely monitoring ongoing incident across Cloudflare and other critical third party services Composio depends on. We'll keep you posted.