Sifflet - Notice history

100% - uptime

eu-west-1-a - Web application - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026

eu-west-1-b - Web application - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026

eu-west-1-c - Web application - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026

us-east-1-a - Web application - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026
99% - uptime

eu-west-1-a - Integrations - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026

eu-west-1-b - Integrations - Operational

97% - uptime
Jan 2026 · 92.51%Feb · 100.0%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026

eu-west-1-c - Integrations - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 99.99%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026

us-east-1-a - Integrations - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026
100% - uptime

eu-west-1-a - Datasource monitoring - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026

eu-west-1-b - Datasource monitoring - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026

eu-west-1-c - Datasource monitoring - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 99.66%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026

us-east-1-a- Datasource monitoring - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026
100% - uptime

eu-west-1-a - API - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026

eu-west-1-b - API - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026

eu-west-1-c - API - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026

us-east-1-a - API - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2026
Feb 2026
Mar 2026

Notice history

Mar 2026

No notices reported this month

Feb 2026

Scheduled monitor orchestration disruption
  • Resolved
    Resolved

    This incident has been resolved.

    As previously stated, the current incident was an aftermath of the incident that occurred on the 17th of February (and that was resolved on that day). The detection of this residual impact was delayed by the low volume of impacted monitors compared with the total volume of monitors orchestrated by our platform. We've implemented corrective measures on our alerting systems to improve our detection of such events.

  • Monitoring
    Monitoring

    We deployed a fix of the issue, and are monitoring that the 7 monitors are now running according to their schedules.

  • Identified
    Identified

    We identified the cause of the issue, caused by a failure in the behavior of our orchestration framework that happens in some very specific situations, created by the incident that occurred on the 17th of February: https://siffletdata-status.com/cmlqprxwm01clmg0v51e5vj9h.

    The fix for this issue will be deployed in production on Thursday 26th of February.

    We've also clarified the impact of the incident: only one of the tenants of the cell is impacted, and only 7 scheduled monitors of this tenant are impacted (meaning they are no longer running according to their schedules). The customer associated with this tenant has already been contacted by our team.

  • Investigating
    Investigating

    We’re currently experiencing an issue with the orchestration of some scheduled monitors on the eu-west-1-c cell. Some of them might no longer be running according to their configured schedules (for instance "hourly", "daily" or "weekly").

    Manual runs of monitors through the UI or the API is not impacted and works as expected.

    Our team is currently investigating the issue. We’ll provide updates here as the situation progresses.

Jan 2026

Jan 2026 to Mar 2026

Next