LexisNexis Cirium Outage History

Started Dec 05, 2025, 05:56 PM UTC· resolved Dec 05, 2025, 08:49 PM UTC

1. investigating Dec 05, 2025, 05:56 PM UTC

   We’ve received reports from some Alerts API customers experiencing issues with alert callbacks due to WAF (Web Application Firewall) rules. This incident may have started at approximately 2025-12-05 16:39 UTC. Our team is actively investigating and working to resolve the problem. Our next update will be 21:26 UTC on 2025-12-05.

2. identified Dec 05, 2025, 06:54 PM UTC

   We have identified the cause of a current Alerts API disruption and are actively working on a fix to restore full functionality. Further updates will be posted here as progress continues. Thank you for your patience and understanding.

3. resolved Dec 05, 2025, 08:49 PM UTC

   We’ve applied a fix to our alerting service and engineering will continue to monitor system performance to ensure stability. As part of this update, we have temporarily disabled a specific validation check to prevent further disruptions. Please contact our Help Desk if you have any questions.

Read the full incident report →

Started Dec 04, 2025, 05:10 PM UTC· resolved Dec 05, 2025, 11:23 AM UTC

1. investigating Dec 04, 2025, 01:56 PM UTC

   We are currently investigating an issue impacting the Dashboard Networks tab and Airport Profiles Routes, Airlines and Aircraft tabs; all of which are not displaying any December 2025 scheduled routes. This issue is not affecting the Airline Profiles Routes tab. We will post a further update shortly.

2. monitoring Dec 04, 2025, 05:10 PM UTC

   We have identified the issue and fixed the underlying data. The fix will be released to production as part of the daily database refresh at approximately 06:00 UTC, 5th December 2025.

3. investigating Dec 05, 2025, 09:24 AM UTC

   Unfortunately the overnight database update has not resolved the issue. We are continuing to investigate and will post a further update shortly.

4. resolved Dec 05, 2025, 11:23 AM UTC

   We have successfully reinstated the missing Networks / Routes data. Please accept our apologies for any disruption caused and contact our Helpdesk if you require further assistance.

Read the full incident report →

Started Dec 02, 2025, 08:17 AM UTC· resolved Dec 02, 2025, 10:26 AM UTC

1. investigating Dec 02, 2025, 08:17 AM UTC

   A subset of customers have reported Trips Import failures. Our engineers are investigating. We will post a further update on or before 11:28 UTC.

2. resolved Dec 02, 2025, 10:26 AM UTC

   This incident has been resolved. Trips are being successfully imported with no retries. Please accept our apologies for any disruption caused and contact our Helpdesk if you require further assistance.

Read the full incident report →

Started Dec 01, 2025, 06:00 AM UTC· resolved Dec 01, 2025, 06:00 AM UTC

1. resolved Dec 01, 2025, 07:01 AM UTC

   Our engineering team have identified an issue with our Alerts API where alerts are either missed or being delayed. This was due to queue size for the Alerts API have increased. The issue has been resolved, and the alerts queue is now processing normally. Some alerts may have been missed during this period.

Read the full incident report →

Started Nov 25, 2025, 09:52 AM UTC· resolved Nov 25, 2025, 03:12 PM UTC

1. investigating Nov 25, 2025, 09:52 AM UTC

   We are currently investigating an issue that is causing duplication of sub-leased aircraft in Fleets Analyzer. Please be aware that aircraft counts may be overstated (depending on filter selections). We will post a further update shortly.

2. resolved Nov 25, 2025, 03:12 PM UTC

   This issue has been resolved. The aircraft duplication was caused by the release of estimated lease end dates yesterday. We have rolled-back the release and will schedule it for a later date once the data has been fixed. Please accept our apologies for any disruption caused.

Read the full incident report →

Started Nov 24, 2025, 12:26 PM UTC· resolved Nov 24, 2025, 03:39 PM UTC

1. investigating Nov 24, 2025, 12:26 PM UTC

   A subset of users have reported blank screens when attempting to access the Cirium Dashboard and Fleets Analyzer. Our engineers are investigating. We will post a further update on or before 20:00 UTC.

2. resolved Nov 24, 2025, 03:39 PM UTC

   This incident has been resolved. Please accept our apologies if you were affected and contact our Helpdesk should you require further assistance.

Read the full incident report →

Started Nov 24, 2025, 03:33 AM UTC· resolved Nov 24, 2025, 09:30 AM UTC

1. investigating Nov 24, 2025, 03:33 AM UTC

   We are currently investigating an issue where users may encounter a 500 error when generating reports in Diio/SRS. Our engineering team has been engaged and is actively working to identify the root cause. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding.

2. investigating Nov 24, 2025, 05:49 AM UTC

   We are currently monitoring the application to find the root cause of the issue. We will provide another update in the next 2-3 hours.

3. investigating Nov 24, 2025, 07:34 AM UTC

   The issue where users were encountering a 500 error when generating reports in Diio/SRS has been resolved. Our engineering team identified and addressed the root cause, and normal functionality has been restored.

4. resolved Nov 24, 2025, 09:30 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 19, 2025, 10:22 AM UTC· resolved Nov 19, 2025, 10:47 AM UTC

1. investigating Nov 19, 2025, 10:22 AM UTC

   The Sky Stream Positional feed was down on the 19/11/2025 from 09:17 AM to 09:27 AM GMT. Our engineers have identified the cause and resolved the issue

2. resolved Nov 19, 2025, 10:47 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 13, 2025, 11:26 PM UTC· resolved Nov 14, 2025, 05:32 AM UTC

1. investigating Nov 13, 2025, 11:26 PM UTC

   We have identified potential intermittent issues affecting alert delivery with our Alerts API. Our engineering team is investigating. We will provide the next update by 2025-11-14 at 06:14 UTC. Thank you for your patience as we work to resolve this.

2. resolved Nov 14, 2025, 05:32 AM UTC

   Our Engineering Team has confirmed the fix for the Alerts API, and it is performing as expected. This incident has been resolved.

Read the full incident report →

Started Nov 13, 2025, 05:31 PM UTC· resolved Nov 13, 2025, 09:40 PM UTC

1. investigating Nov 13, 2025, 05:31 PM UTC

   We are currently investigating reports of degraded performance affecting the Alerts API. Users may experience slower response times or intermittent issues when interacting with this service. Our engineering team is actively working to identify the root cause and restore normal performance. We will provide an update 8 hours from now (11/14/2025 - 01:30 UTC).

2. resolved Nov 13, 2025, 09:40 PM UTC

   We've identified intermittent connection issues in the Alerts delivery system and implemented a fix on 2025-11-12 at 19:50 UTC. Since then, alert delivery rates have improved, and monitoring confirms that volumes have returned to normal levels. We apologize for any inconvenience this may have caused and appreciate your patience. Please contact our Help Desk if you have any questions.

Read the full incident report →

Started Nov 11, 2025, 12:08 PM UTC· resolved Nov 11, 2025, 07:09 PM UTC

1. investigating Nov 11, 2025, 12:00 PM UTC

   Cirium APIs (Laminar Data Hub) are currently unavailable and returning a 503 – Service Temporarily Unavailable error. Our team is actively investigating the issue. We will keep you posted once we have new updates.

2. investigating Nov 11, 2025, 12:08 PM UTC

   We are continuing to investigate this issue. We will provide the next update no later than 16:00 UTC.

3. investigating Nov 11, 2025, 01:06 PM UTC

   This incident is also affecting the Cirium Sky Stream NOTAMS, with no updates to the feed since 12:32 UTC. We are continuing to investigate the cause and working to restore the affected services as soon as possible. A further update will be posted no later than 16:00 UTC.

4. investigating Nov 11, 2025, 04:03 PM UTC

   Our engineers are currently working with a third party infrastructure provider to address this issue. We appreciate your continued patience and understanding. A further update will be posted on or before 20:00 UTC.

5. identified Nov 11, 2025, 06:31 PM UTC

   The application is showing signs of stability, and several APIs are functioning as expected. We are actively increasing node capacity and closely monitoring performance. Full stability is still pending. We will provide another update at 19:00 UTC.

6. resolved Nov 11, 2025, 07:09 PM UTC

   The services impacting Cirium Sky Stream NOTAMS and Cirium SKY Laminar APIs are now fully stable, and all APIs are performing as expected. Our team will continue to monitor our system closely to ensure ongoing reliability. Thank you for your continued patience. Please contact our Help Desk with any questions.

Read the full incident report →

Started Nov 06, 2025, 08:12 AM UTC· resolved Nov 11, 2025, 06:31 AM UTC

1. investigating Nov 06, 2025, 12:32 AM UTC

   A subset of Alerts API customers are currently experiencing degraded performance with our Alerting service. Our engineering team is actively investigating the issue and will provide updates as soon as more information becomes available. We will provide the next update on 2025-11-06 at 07:54 UTC. Thank you for your patience and understanding.

2. investigating Nov 06, 2025, 08:12 AM UTC

   Our Engineering Team has identified that the Alert APIs are affecting one specific airline. They are actively investigating the root cause of the issue. Thank you for your patience and understanding.

3. investigating Nov 06, 2025, 03:55 PM UTC

   We have identified an event processing timeout issue that is preventing one airline's flights from triggering Alerts API callbacks. Our engineers are continuing to investigate the cause of these timeouts. A further update will be provided no later than 2025-11-06 23:54 UTC.

4. investigating Nov 06, 2025, 10:39 PM UTC

   The issue was initially limited to some Alerts API and FlightStats.com customers but is now affecting our alerting service for other airlines. Previous mitigation efforts have not resolved the problem. Our development team will continue working on a fix to restore normal service and we will provide the next update at 2025-11-07 06:45 UTC.

5. investigating Nov 06, 2025, 10:50 PM UTC

   We are continuing to investigate this issue.

6. investigating Nov 07, 2025, 05:01 AM UTC

   We’d like to provide you with an update on this case. As per our engineering team, the system has shown stable connectivity over the past six hours, and we continue to monitor its performance closely. The next update will be provided by 13:00 UTC on 2025-11-07, or sooner if there are any further developments.

7. monitoring Nov 07, 2025, 08:13 AM UTC

   The queue size has returned to normal, and alert delivery to customers is operating as usual. The connection timeout issue is stable, and the team is monitoring it. The original issue of missing alerts for several Rule IDs affecting some customers has been resolved, alerts will now be delivered as expected. We will continue to monitor the system and provide updates.

8. investigating Nov 07, 2025, 12:38 PM UTC

   We are continuing to experience latency issues during the processing of flight events. Our engineers are investigating. We will provide a further update no later than 2025-11-07 20:37 UTC. Thank you for your continued patience and understanding.

9. identified Nov 07, 2025, 05:17 PM UTC

   Our engineering team has identified the cause of the latency and are working to clear the alerts queue. We will provide a further update on or before 2025-11-08 01:17 UTC.

10. identified Nov 07, 2025, 08:31 PM UTC

    We are continuing the recovery process here, still no major breakthrough. Database is bloated with huge volume and less memory available. Database Backup recovery is running for a while and we are waiting for the process to complete. We will provide a further update no later than 2025-11-08 5:00 UTC. Thank you for your continued patience and understanding.

11. identified Nov 08, 2025, 01:21 PM UTC

    We are continuing to work on a fix for this issue.

12. monitoring Nov 08, 2025, 07:05 PM UTC

    The database is performing better, but the main delay is due to the large volume of stale data that must be manually cleaned up before normal operations can resume. They are actively working on the cleanup now and anticipate that services will resume in the next update 9th November 1:00 UTC.

13. monitoring Nov 08, 2025, 08:17 PM UTC

    The Flight Alerts API service have been restored and all the operations have been working. Alerts are getting delivered. We are continuously monitoring the system for performance. There could be some latency which is expected due to the heavy backlog. Next update, 2025-11-09 6:30 UTC.

14. monitoring Nov 10, 2025, 12:26 AM UTC

    The performance of the Flight Alerts API looks good and the requests are getting processed. We will continue monitoring the system and the cleanup the backlog and stale data. Next update - 2025-11-10 6:30 UTC

15. monitoring Nov 10, 2025, 06:40 AM UTC

    The performance seems stable now after a temporary spike from 5.30 UTC to 6.20 UTC. The alerts are getting delivered without delays. Next Actions: 1) We are checking why there is a temporary spike during this timeframe 2) Team is working on the Database cleanup to optimize the storage space Next update will be 2025-11-10 10:30 UTC.

16. monitoring Nov 10, 2025, 10:37 AM UTC

    System performance remains stable, with alerts being delivered promptly and no further issues detected. We are continuing to investigate the temporary spike, however have yet discovered the cause. The database clean up is ongoing, and we are monitoring the system closely. A further update will be provided no later than 2025-11-10 14:30 UTC.

17. monitoring Nov 10, 2025, 02:52 PM UTC

    All systems are stable with no further performance issues detected. Root cause investigation is underway. A further update will be provided no later than 2025-11-11 06:30 UTC.

18. monitoring Nov 11, 2025, 06:31 AM UTC

    Alerts performance has been stable over the past 24 hours, with no issues reported for the Alerts API. The root cause was identified as increased database data from sweepers running, which led to SQL query delays. We addressed this by vertically scaling the database and are currently working to clear stale data.

19. resolved Nov 11, 2025, 06:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Started Oct 30, 2025, 10:25 AM UTC· resolved Oct 30, 2025, 02:24 PM UTC

1. identified Oct 30, 2025, 10:25 AM UTC

   We suffered an outage of an upstream system from 8:09 to 9:33 UTC today, 29th October, affecting the processing of flight data. This outage has impacted flight status feeds, updates and flight alerts. The underlying issue has been resolved and we are working to restore all affected services. We will provide a further update no later than 14:00 UTC. For any questions or assistance, please contact our Help Desk.

2. monitoring Oct 30, 2025, 11:44 AM UTC

   Our services are recovering, with flight alerts being delivered normally. We are continuing to monitor performance closely and will provide further updates as required.

3. resolved Oct 30, 2025, 02:24 PM UTC

   This incident has been resolved. All Cirium products and systems affected by the earlier flight data outage are operational, with no data degradation. Thank you for your patience and understanding during the outage. Please contact our Help Desk if you have any ongoing issues or follow-up questions.

Read the full incident report →

Started Oct 29, 2025, 11:35 PM UTC· resolved Oct 29, 2025, 11:59 PM UTC

1. investigating Oct 29, 2025, 11:35 PM UTC

   We have identified an issue with Fleets Analyzer causing slow query performance and preventing some queries from loading. Additionally, exports are stuck in the queue. We will share the next update by 2025-10-30 at 6:23 UTC. Thank you for your patience as we work to restore normal service. For any questions or assistance, please contact our Help Desk.

2. resolved Oct 29, 2025, 11:59 PM UTC

   The issue with Fleets Analyzer causing incomplete queries and stuck exports has been resolved. All services are now operating normally. We will continue to closely monitor performance to ensure service is stable. Thank you for your patience during this incident.

Read the full incident report →