Resolved after 15 hours 46 minutes, affecting Cirium Sky™ APIs, on April 1, 2026.
We’re pleased to confirm that this issue has now been resolved. Our engineering team identified and removed a number of invalid alert rule IDs, and the system is now operating as expected. We’ll continue to monitor performance closely to ensure ongoing stability. If you have any questions or notice anything unexpected, please don’t hesitate to contact our Help Desk.
Affected components
Update timeline
- investigating Apr 01, 2026, 05:22 PM UTC
We are currently investigating reports of missing alerts from the Alerts API and will provide updates as available.
- identified Apr 01, 2026, 09:11 PM UTC
We have identified the root cause of the issue and are actively working on a resolution. We will provide another update by 01:11 UTC on 2026-04-02. Thank you for your ongoing patience.
- identified Apr 02, 2026, 01:08 AM UTC
We have identified the root cause of the issue and are actively working on a resolution. We will provide another update by 05:11 UTC on 2026-04-02. Thank you for your ongoing patience.
- identified Apr 02, 2026, 05:10 AM UTC
We have identified the root cause of the issue and are actively working on a resolution. We will provide another update by 09:11 UTC on 2026-04-02. Thank you for your ongoing patience.
- resolved Apr 02, 2026, 09:09 AM UTC
We’re pleased to confirm that this issue has now been resolved. Our engineering team identified and removed a number of invalid alert rule IDs, and the system is now operating as expected. We’ll continue to monitor performance closely to ensure ongoing stability. If you have any questions or notice anything unexpected, please don’t hesitate to contact our Help Desk.
Your product runs on more than LexisNexis Cirium
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services