LexisNexis Cirium incident

Trip Alerts Delivery Interruption

Major Resolved View vendor source →
Started
Apr 16, 2026, 11:17 PM UTC
Resolved
Apr 17, 2026, 09:46 AM UTC
Duration
10h 28m
Detected by Pingoru
Apr 16, 2026, 11:17 PM UTC

Affected components

Proactive & Traveler Services

Update timeline

  1. investigating Apr 16, 2026, 11:17 PM UTC

    We are currently experiencing an issue impacting the delivery of Trip alerts. The issue started at approx. 19:18 UTC today on 16 April 2026 and has been escalated to our engineering team. We will provide a further update by 02:48 UTC on 17 April 2026.

  2. investigating Apr 17, 2026, 02:48 AM UTC

    Our engineering team continues to investigate the issue impacting Trip alert delivery We will provide another update by 06:48 UTC on 17th April 2026.

  3. identified Apr 17, 2026, 05:40 AM UTC

    Our engineering team has identified the root cause, and they are currently addressing the issue. We will provide another update by 09:40UTC on 17th April 2026.

  4. resolved Apr 17, 2026, 09:46 AM UTC

    The incident affecting Trip alert deliveries has been resolved. Alerts are being delivered successfully and we are continuing to monitor performance closely. Please accept our apologies for any her disruption caused and contact the Help Desk if you have any questions.

Looking to track LexisNexis Cirium downtime and outages?

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

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

5 free monitors · No credit card required