Calix Outage History

Calix is up right now

Calix had 4 outages in the last 2 years totaling 41h 1m of downtime — averaging 0.2 incidents per month.

There were 4 Calix outages since September 11, 2025 totaling 41h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://trust.calix.com

Critical September 24, 2025

Cloud Incident CI-24-35: Product Outage: Calix Cloud >> Cloud Access

Detected by Pingoru
Sep 24, 2025, 03:22 PM UTC
Resolved
Sep 24, 2025, 04:42 PM UTC
Duration
1h 19m
Affected: Calix Service CloudCalix Service Cloud APICalix Engagement CloudTraffic Usage APIEndpoint Mapping APICalix Operations CloudCalix Deployment Cloud
Timeline · 4 updates
  1. investigating Sep 24, 2025, 03:22 PM UTC

    We are currently investigating reports of issues with Calix Cloud. Additional details and regular status updates regarding this matter can be found on the Calix Community at the following link: https://community.calix.com/s/feed/0D5Pm00001IesSpKAJ

  2. identified Sep 24, 2025, 03:23 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Sep 24, 2025, 03:40 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Sep 24, 2025, 04:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 11, 2025

Product Disruption: Calix Service Cloud >> Subscriber Turn up and Troubleshooting (TR-069)

Detected by Pingoru
Sep 11, 2025, 03:45 PM UTC
Resolved
Sep 12, 2025, 12:00 AM UTC
Duration
8h 14m
Affected: Calix Service Cloud
Timeline · 3 updates
  1. investigating Sep 11, 2025, 03:45 PM UTC

    We are currently investigating reports of issues with Subscriber Turn up and Troubleshooting (TR-069) in Calix Service Cloud. Additional details and regular status updates regarding this matter can be found on the Calix Community at the following link: https://community.calix.com/s/feed/0D5Pm00001GfuLIKAZ

  2. monitoring Sep 11, 2025, 05:45 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 12, 2025, 12:00 AM UTC

    This incident has been resolved.

Read the full incident report →