Sigma Squared Outage History

Sigma Squared is up right now

Pingoru has recorded 3 incidents for Sigma Squared: 1 in the last 12 months and 0 in the last 90 days.

Source: sigmasquared.statuspage.io

3incidents recorded
1last 12 months
0last 90 days
–typical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Sigma Squared in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 123 (0%)

Incidents, newest first

Notice February 17, 2026 Misreported downtime for API – API

Started Feb 17, 2026, 02:09 PM UTC· resolved Feb 17, 2026, 02:09 PM UTC

  1. resolved Feb 17, 2026, 02:09 PM UTC

    During a deployment on Feb 16th a reconfiguration of the API unintentionally led to a misreporting of downtime when the services were operating normally.

Read the full incident report →

Minor June 6, 2025 System test change lead to false report of API downtime –

Started Jun 06, 2025, 07:00 PM UTC· resolved Jun 06, 2025, 07:00 PM UTC

  1. resolved Jun 06, 2025, 07:00 PM UTC

    During a deployment to production, a new system test was added for API alias domains. This caused the status of the API to appear unhealthy while the first region of nodes were able to establish their first stable reading.

Read the full incident report →

Major April 8, 2025 Dashboard is unavailable 38m

Started Apr 08, 2025, 08:42 PM UTC· resolved Apr 08, 2025, 09:20 PM UTC

  1. resolved Apr 08, 2025, 09:30 PM UTC

    Beginning 4:42PM, a misconfiguration caused the dashboard to be briefly unavailable, and all requests to the Sigma Squared platform resulted in an error page. Engineering was alerted to the issue at 4:48PM, and the underlying problem was identified and resolved by 5:20PM. This misconfiguration affected the loading of the dashboard frontend only. The security and integrity of customer data was not degraded.

Read the full incident report →