SchemeServe Outage History

SchemeServe is up right now

SchemeServe had 6 outages in the last 2 years totaling 47h 21m of downtime — averaging 0.2 incidents per month.

There were 6 SchemeServe outages since October 10, 2025 totaling 47h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.schemeserve.com

Major April 21, 2026

Report performance issues

Detected by Pingoru
Apr 21, 2026, 10:53 AM UTC
Resolved
Apr 21, 2026, 11:56 AM UTC
Duration
1h 2m
Affected: 📈 Reports
Timeline · 2 updates
  1. investigating Apr 21, 2026, 10:53 AM UTC

    We are investigating an issue where certain reports are failing to generate correctly. We are looking into this at our highest priority to resolve this as soon as possible.

  2. resolved Apr 21, 2026, 11:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 18, 2025

Intermittent Service Disruptions - Cloudflare

Detected by Pingoru
Nov 18, 2025, 11:43 AM UTC
Resolved
Nov 18, 2025, 03:02 PM UTC
Duration
3h 18m
Affected: 🎩 SchemeServe
Timeline · 5 updates
  1. investigating Nov 18, 2025, 11:43 AM UTC

    We’re currently experiencing intermittent service disruptions due to Cloudflare issues. Our team is monitoring closely and will update as soon as possible

  2. investigating Nov 18, 2025, 11:54 AM UTC

    Cloudflare are currently experiencing global network issues, which are affecting services across the internet. This may cause intermittent disruption. We’re monitoring the situation and will provide updates as Cloudflare restores normal service.

  3. monitoring Nov 18, 2025, 02:19 PM UTC

    Unfortunately, Cloudflare continue to experience global network issues, affecting significant parts of the internet and including services such as AWS, PayPal, Visa, BT & Sage. Thank you for your patience - whilst this issue is unfortunately beyond SchemeServe's control, we will keep you informed as we are monitoring the situation closely.

  4. resolved Nov 18, 2025, 03:02 PM UTC

    Cloudflare have resolved the global network issue. Services are now fully restored and operating normally. Thank you for your patience.

  5. postmortem Nov 19, 2025, 01:31 PM UTC

    On 18 November 2025, a global network incident at Cloudflare caused a service outage across multiple platforms, including SchemeServe. The root cause was a permissions-related configuration change that triggered propagation of an oversized data file, leading to widespread HTTP 5xx errors. We sincerely apologise for the disruption. Normal service has now been fully restored, and Cloudflare has published a full incident report at: [Cloudflare blog](https://blog.cloudflare.com/18-november-2025-outage/?utm_source=chatgpt.com). We are reviewing our continuity and monitoring measures to minimise the risk of similar external-dependency issues in future.

Read the full incident report →

Minor October 20, 2025

AWS outage leading to sporadic email and SMS issues

Detected by Pingoru
Oct 20, 2025, 10:09 AM UTC
Resolved
Oct 21, 2025, 08:13 AM UTC
Duration
22h 3m
Affected: 🎩 SchemeServe
Timeline · 2 updates
  1. investigating Oct 20, 2025, 10:09 AM UTC

    Some users may experience issues with email and SMS deliverability. This is due to an outage of AWS, and we are continuing to monitor the situation.

  2. resolved Oct 21, 2025, 08:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 10, 2025

Policy view issue

Detected by Pingoru
Oct 10, 2025, 03:18 PM UTC
Resolved
Oct 10, 2025, 03:36 PM UTC
Duration
18m
Affected: 🎩 SchemeServe
Timeline · 3 updates
  1. investigating Oct 10, 2025, 03:18 PM UTC

    We are currently investigating an issue where some policies are unable to be viewed. We are working on this with the utmost urgency, and will resolve this as soon as possible.

  2. resolved Oct 10, 2025, 03:36 PM UTC

    This incident has been resolved.

  3. postmortem Oct 10, 2025, 04:30 PM UTC

    On Friday between 16:09 and 16:30 BST, some users briefly experienced issues accessing policy answers data. The cause was a search index update that didn’t complete as expected. This update had recently been moved to a scheduled process to improve predictability and stability. Our team identified and resolved the issue quickly, restoring full access within 20 minutes. The process has since been reviewed and refined to further strengthen resilience. This update was low-risk and had been fully tested in non-production environments with no adverse effects. Services are now operating normally.

Read the full incident report →