Scrutinizer Outage History

Scrutinizer is up right now

Pingoru has recorded 65 incidents for Scrutinizer: 1 in the last 12 months and 0 in the last 90 days.

Source: status.scrutinizer-ci.com

65incidents recorded
1last 12 months
0last 90 days
110 minutestypical duration
Incidents per month
012MayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%MayJunJulAugSepOct0%
Pingoru began tracking Scrutinizer in May 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
May 202612 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 517 (0%)

Incidents, newest first

Major May 7, 2026 Increased error rates 1h 49m Workers

Started May 07, 2026, 11:09 AM UTC· resolved May 07, 2026, 12:59 PM UTC

  1. investigating May 07, 2026, 11:09 AM UTC

    We are currently investigating this issue.

  2. monitoring May 07, 2026, 12:19 PM UTC

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

  3. monitoring May 07, 2026, 12:59 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved May 07, 2026, 12:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 25, 2025 Website Unavailable 17h 35m Web

Started Aug 25, 2025, 07:45 PM UTC· resolved Aug 26, 2025, 01:20 PM UTC

  1. identified Aug 25, 2025, 07:45 PM UTC

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

  2. monitoring Aug 25, 2025, 09:33 PM UTC

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

  3. monitoring Aug 25, 2025, 09:33 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Aug 26, 2025, 06:40 AM UTC

    We are still affected by database performance issues. We are currently working on migrating to a newer set-up. The new replica should be ready within the next one to two hours.

  5. monitoring Aug 26, 2025, 09:39 AM UTC

    Database migration has been completed and performance should be back to normal. We keep monitoring the situation.

  6. resolved Aug 26, 2025, 01:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 4, 2025 Worker Processing 2h 9m Workers

Started Mar 04, 2025, 08:59 AM UTC· resolved Mar 04, 2025, 11:08 AM UTC

  1. identified Mar 04, 2025, 08:59 AM UTC

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

  2. monitoring Mar 04, 2025, 09:49 AM UTC

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

  3. resolved Mar 04, 2025, 11:08 AM UTC

    This incident has been resolved.

Read the full incident report →