Composio - Notice history

All systems operational

Webapp - Operational

100% - uptime
Oct 2025 · 99.64%Nov · 99.96%Dec · 100.0%

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

v1/v2 API - Operational

100% - uptime
Oct 2025 · 99.64%Nov · 99.97%Dec · 100.0%

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

v3 API - Operational

100% - uptime
Oct 2025 · 99.64%Nov · 99.97%Dec · 100.0%

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

Tool Execution - Operational

100% - uptime
Oct 2025 · 99.16%Nov · 99.97%Dec · 100.0%

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

MCP Server - Operational

100% - uptime
Oct 2025 · 99.64%Nov · 99.97%Dec · 100.0%

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

Triggers - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 99.85%Dec · 100.0%

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

Notice history

Dec 2025

No notices reported this month

Nov 2025

Logins with Google/Github are not working on production
  • Resolved
    Resolved

    This incident has been resolved. We're working on fixing the root cause and not repeat this error.

  • Monitoring
    Monitoring

    We've fixed the issue in production and monitoring it actively.

  • Investigating
    Investigating

    We are currently investigating this incident. This impacts only platform login with google/github. No impact on APIs. You can leverage magic link login while we work on this incident.

Triggers are down
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    We are currently investigating this incident.
Production outage on majority of issues
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    Platform and services are now back up. We are monitoring the services.

  • Identified
    Identified

    We have identified the root cause to be database resources. We are working on remidiations.

  • Investigating
    Investigating
    We are currently investigating this incident.

Oct 2025

Issues with Backend APIs
  • Resolved
    Resolved

    We're no longer observing the errors in our logs and internal dashboards. All services look great. Thank you for your patience.

  • Monitoring
    Monitoring

    We've identified issues with our SSL certificate. We've resolved the issue, and actively monitoring.

  • Investigating
    Investigating

    We are currently investigating this incident, impacting calls to our APIs

Elevated 5xx error rate in tool execution
  • Resolved
    Resolved

    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.

  • Monitoring
    Monitoring

    We have noticed a significant decrease in 5xx errors. We will continue to monitor the situation.

  • Investigating
    Investigating

    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.

Production down
  • Resolved
    Resolved

    This incident has been resolved. All systems are functional. Thank you for your patience.

  • Monitoring
    Monitoring

    We've an update from AWS. Systems are working as expected. We're monitoring.

  • Identified
    Identified

    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

  • Investigating
    Investigating

    We're currently investigating why production is not responding

Oct 2025 to Dec 2025

Next