Scrutinizer Outage History

Scrutinizer is up right now

Scrutinizer had 6 outages in the last 2 years totaling 81h 46m of downtime — averaging 0.2 incidents per month.

There were 6 Scrutinizer outages since June 5, 2024 totaling 81h 46m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.scrutinizer-ci.com

Major May 7, 2026

Increased error rates

Detected by Pingoru
May 07, 2026, 11:09 AM UTC
Resolved
May 07, 2026, 12:59 PM UTC
Duration
1h 49m
Affected: Workers
Timeline · 4 updates
  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

Detected by Pingoru
Aug 25, 2025, 07:45 PM UTC
Resolved
Aug 26, 2025, 01:20 PM UTC
Duration
17h 35m
Affected: Web
Timeline · 6 updates
  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

Detected by Pingoru
Mar 04, 2025, 08:59 AM UTC
Resolved
Mar 04, 2025, 11:08 AM UTC
Duration
2h 9m
Affected: Workers
Timeline · 3 updates
  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 →

Critical October 11, 2024

Inavailability of Shared Filesystem

Detected by Pingoru
Oct 11, 2024, 10:06 AM UTC
Resolved
Oct 13, 2024, 10:42 AM UTC
Duration
2d
Affected: WebWorkers
Timeline · 4 updates
  1. investigating Oct 11, 2024, 10:06 AM UTC

    We are currently investigating this issue.

  2. monitoring Oct 11, 2024, 10:20 AM UTC

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

  3. monitoring Oct 11, 2024, 10:29 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Oct 13, 2024, 10:42 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 27, 2024

Backlog in task processing

Detected by Pingoru
Aug 27, 2024, 01:51 PM UTC
Resolved
Aug 27, 2024, 09:26 PM UTC
Duration
7h 35m
Affected: Workers
Timeline · 2 updates
  1. investigating Aug 27, 2024, 01:51 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 27, 2024, 09:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 5, 2024

Result Processing Error Rate

Detected by Pingoru
Jun 05, 2024, 08:44 AM UTC
Resolved
Jun 05, 2024, 12:44 PM UTC
Duration
4h
Affected: Workers
Timeline · 4 updates
  1. investigating Jun 05, 2024, 08:44 AM UTC

    We are currently investigating this issue.

  2. identified Jun 05, 2024, 09:19 AM UTC

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

  3. monitoring Jun 05, 2024, 09:49 AM UTC

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

  4. resolved Jun 05, 2024, 12:44 PM UTC

    This incident has been resolved.

Read the full incident report →