SchemeServe Outage History

SchemeServe is up right now

There were 2 SchemeServe outages since March 31, 2026 totaling 1h 40m 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 →

Minor March 31, 2026

Additional modules temporarily inaccessible

Detected by Pingoru
Mar 31, 2026, 02:10 PM UTC
Resolved
Mar 31, 2026, 02:48 PM UTC
Duration
37m
Affected: 🎩 SchemeServe
Timeline · 3 updates
  1. investigating Mar 31, 2026, 02:10 PM UTC

    Some of our additional modules are experiencing issues, and may be inaccessible. We are investigating this as a highest priority.

  2. resolved Mar 31, 2026, 02:48 PM UTC

    This incident has been resolved.

  3. postmortem Apr 01, 2026, 08:48 AM UTC

    ## Incident Report: Partial Frontend Outage on March 31, 2026 ## Issue The automatic renewal of an internal SSL certificate failed, causing our feature flag service to go down. As a result, newer interfaces—QSE and Digit—did not load correctly when the frontend attempted to retrieve feature flags from the service. ## Summary On March 31, 2026, a subset of users experienced issues loading the new frontends \(QSE and Digit\). When the frontend requested an update to feature flags, only the frontend was affected—no other services or processes were impacted. We know how disruptive this was and sincerely regret the inconvenience. ## Timeline * ~12:16: Internal SSL certificate failed to renew automatically. * ~15:00: First reported instance of QSE failing to load. * 15:11: Root cause identified. * 15:46: Service restored. ## Impact * Affected: New frontend screens—QSE, Digit, Translations, Email Logs, Machine Keys. * Duration: Approximately 3.5 hours. ## Root Cause Analysis The internal SSL certificate between Cloudflare and our feature flag service failed to automatically renew as expected. This caused the service to become unreachable, resulting in the frontend either displaying a “white screen of death” or reverting to older UI versions when making network requests to the feature flag API service. ## Resolution Steps * Removed the automated renewal process. * Created a long-lived SSL certificate for this service. ## Preventative Actions * Implemented longer-lived SSL certificates: * Eliminates automated renewal dependence, reducing the risk of unexpected outages. * Enhanced alerting on the uptime state of the feature flag service: * Ensures faster detection and response to potential downtime. ## Apology We sincerely apologize for any disruption this may have caused your business. We are deeply committed to preventing similar incidents in the future. Thank you for your understanding and patience.

Read the full incident report →

Looking to track SchemeServe downtime and outages?

Pingoru polls SchemeServe's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when SchemeServe reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track SchemeServe alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring SchemeServe for free

5 free monitors · No credit card required