LexisNexis Cirium Outage History

Started Apr 08, 2026, 03:04 PM UTC· resolved May 27, 2026, 10:51 PM UTC

1. identified Apr 08, 2026, 03:04 PM UTC

   Due to a security concern, we have temporarily deactivated the Alerts API SMTP (email) delivery option that is available for testing and evaluation purposes only. To continue testing the Alerts API on either the Flightstats or Sky platforms, please configure delivery to an HTTPS endpoint that accepts POST requests, as per https://developer.cirium.com/apis/cirium-sky-api/flight-alerts. We apologise for any inconvenience and will provide an update as soon as there is progress to report.

2. resolved May 27, 2026, 10:51 PM UTC

   This has been resolved and the SMTP (email) delivery option has been re-enabled in the Alerts API.

Read the full incident report →

Started Apr 08, 2026, 09:09 AM UTC· resolved Apr 09, 2026, 07:57 AM UTC

1. investigating Apr 08, 2026, 09:09 AM UTC

   We are currently investigating a Fleets Analyzer issue that has affected the March 2026 tracked utilisation and optional emissions data updates. The affected data is currently available up to and including February 2026. We apologise for any inconvenience caused and will post a further update no later than 09:00 UTC, 9th April.

2. resolved Apr 09, 2026, 07:57 AM UTC

   March 2026 tracked utilisation and emissions data has been uploaded to Fleets Analyzer. Thank you for your patience.

Read the full incident report →

Started Apr 08, 2026, 04:41 AM UTC· resolved Apr 08, 2026, 06:55 AM UTC

1. investigating Apr 08, 2026, 04:41 AM UTC

   We are investigating an issue with Developer Flightstats - Flight Track APIs. We are currently experiencing no response from server. We apologies for any inconvenience caused and will post a further update no later than 8th April 2026, 08:37 UTC.

2. resolved Apr 08, 2026, 06:55 AM UTC

   The issue was identified and fixed. This incident has been resolved.

Read the full incident report →

Started Apr 01, 2026, 05:22 PM UTC· resolved Apr 02, 2026, 09:09 AM UTC

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

Read the full incident report →

Started Mar 30, 2026, 10:01 AM UTC· resolved Mar 30, 2026, 10:27 AM UTC

1. investigating Mar 30, 2026, 10:01 AM UTC

   We’re currently experiencing degraded performance issues with Fleets and Values Analyzer. A subset of users are reporting blank or partially rendered screens. Our team is currently working to restore normal performance levels. We apologize for any inconvenience. We will post a further updated on or before 18:00 UTC.

2. resolved Mar 30, 2026, 10:27 AM UTC

   This incident has been resolved. Fleets and Values Analyzer pages are loading as expected.

Read the full incident report →

Started Mar 26, 2026, 04:55 PM UTC· resolved Apr 07, 2026, 08:06 AM UTC

1. investigating Mar 26, 2026, 04:55 PM UTC

   We are investigating an issue with Fleets Analyzer - Aircraft - Summary returning overstated aircraft counts. The Detail and Trend tabs are unaffected. We apologise for any inconvenience caused and will post a further update no later than 27th March, 01:00 UTC.

2. investigating Mar 27, 2026, 01:06 AM UTC

   We are continuing to investigate the issue causing overstated aircraft counts in Fleets Analyzer under Aircraft Summary. Detail and Trend tabs remain unaffected. A further update will be provided no later than 27th March at 09:00 UTC. Please contact our Help Desk with any questions.

3. identified Mar 27, 2026, 07:38 AM UTC

   We are currently addressing an issue on the Summary tab where some figures were overstated. A temporary fix has been applied to ensure the Summary now reflects the correct values. The team is working on a permanent resolution, which is targeted for completion by Wednesday end of day next week. Additionally, we have identified a related issue on the Summary page where the Total Indicative Market Value (US$M) is not being displayed in million‑dollar terms on the UI grid. This will also be addressed, with a targeted resolution planned for the following week. We will continue to provide updates as progress is made.

4. resolved Apr 07, 2026, 08:06 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 25, 2026, 06:49 PM UTC· resolved Mar 26, 2026, 09:52 AM UTC

1. investigating Mar 25, 2026, 06:49 PM UTC

   We are investigating intermittent server errors impacting the FlightStats Flight Status API, first observed around 12:30 AM UTC on 2026-03-25. A limited number of customers may be impacted. The next update will be provided by 02:00 AM UTC on 2026-03-26.

2. monitoring Mar 25, 2026, 08:09 PM UTC

   Engineering has identified intermittent database connection issues impacting the Flight Status API. A change has been applied and connections have stabilized. The team continues to monitor the service and analyze the issue, with further updates to follow as needed. Please contact our Help Desk if you encounter any errors.

3. monitoring Mar 26, 2026, 09:52 AM UTC

   Our engineering team has confirmed that the service is running as expected, with no issues or restarts observed. Monitoring shows normal operation across all components, and this issue has now been resolved. If you continue to experience any irregularities, please feel free to contact us so we can assist further. Thank you for your cooperation and patience while we worked to resolve this issue.

4. resolved Mar 26, 2026, 09:52 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 23, 2026, 10:32 AM UTC· resolved Mar 23, 2026, 11:27 AM UTC

1. investigating Mar 23, 2026, 10:32 AM UTC

   We are investigating a VPN issue that is affecting the ingestion of flight data from multiple airlines. The impact of this is stale flight status data in the Cirium Sky APIs, Stream and Data Warehouse, Trips and Flightstats.com. We apologise for the inconvenience caused and will post a further update no later than 14:30 UTC.

2. investigating Mar 23, 2026, 10:35 AM UTC

   We are continuing to investigate this issue.

3. investigating Mar 23, 2026, 10:54 AM UTC

   We are continuing to investigate this issue.

4. resolved Mar 23, 2026, 11:27 AM UTC

   The VPN connection has been restored and flight data is being received as expected from the affected upstream providers. Please accept our apologies for any disruption caused and contact the Help Desk for further assistance.

Read the full incident report →

Started Mar 23, 2026, 09:28 AM UTC· resolved Mar 30, 2026, 08:28 AM UTC

1. investigating Mar 23, 2026, 09:28 AM UTC

   We are investigating a server connectivity issue that is preventing the completion of PDS Fleets daily deliveries. We apologise for the inconvenience caused and will post a further update no later than 17:00 UTC. For clarification, this incident does not affect the Cirium Fleets API service.

2. investigating Mar 23, 2026, 05:08 PM UTC

   Our engineers are continuing to investigate the issue that is preventing the delivery of PDS Fleets data. A further update will be posted at or around 09:00 UTC tomorrow, 24th March. Thank you for your patience and understanding.

3. investigating Mar 24, 2026, 11:34 AM UTC

   Our engineers are continuing to investigate the issue that is preventing the delivery of PDS Fleets data. A further update will be posted at or around 17:00 UTC. Thank you for continued patience and understanding. Please reach out to the Help Desk if you require further assistance.

4. identified Mar 24, 2026, 04:44 PM UTC

   We have identified what we believe to be the underlying issue and are investigating next steps. In parallel, the PDS team are working to address the backlog of delayed deliveries, however this is a manual task and will take some time to complete. Your continued patience is highly appreciated. We will provide the next update, on or around 10:00 UTC tomorrow.

5. identified Mar 24, 2026, 11:23 PM UTC

   Our Professional Data Services team has now cleared the backlog of delayed deliveries, and processing is currently up to date. We continue to investigate a longer-term solution to address the underlying server issue and prevent recurrence. In the interim, files will be delivered manually, with a target of same-day delivery. Thank you for your continued patience while we work toward a permanent resolution. We will provide the next update, on or around 10:00 UTC on 2026-03-25.

6. identified Mar 25, 2026, 12:53 PM UTC

   Our engineers continue to work on a permanent solution to address the file delivery issue, however this may take several days. In the meantime we will continue with manual file deliveries. Thank you for your continued patience.

7. resolved Mar 30, 2026, 08:28 AM UTC

   We are happy to report that the issue affecting PDS Fleets deliveries has been resolved. The solution has been thoroughly tested and we have full confidence in its reliability and stability. Please accept our apologies for any disruption caused and contact the Help Desk for further assistance.

Read the full incident report →

Started Mar 17, 2026, 10:46 AM UTC· resolved Mar 17, 2026, 11:53 AM UTC

1. investigating Mar 17, 2026, 10:46 AM UTC

   We’re currently experiencing degraded performance issues with the Cirium Sky API platform, Flightstats.com and Trip Center. Users may observe a high number of server errors. Our team is currently working to restore normal performance levels. We apologize for any inconvenience. We will post a further update no later than 14:45 UTC.

2. investigating Mar 17, 2026, 11:14 AM UTC

   We are continuing to investigate this issue.

3. investigating Mar 17, 2026, 11:30 AM UTC

   We are continuing to investigate this issue.

4. monitoring Mar 17, 2026, 11:33 AM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Mar 17, 2026, 11:53 AM UTC

   This incident has been resolved. Please accept our apologies for any disruption caused and contact the Help Desk for further assistance.

Read the full incident report →

Started Mar 09, 2026, 05:46 PM UTC· resolved Mar 09, 2026, 08:14 PM UTC

1. identified Mar 09, 2026, 05:46 PM UTC

   Sky Warehouse, Sky API and Workbook customers should expect a delay in the latest release of our emissions history and emissions forecast data. We will provide another update on 2026-03-10 at 9:00 AM UTC. Please accept our apologies for the inconvenience. Should you have any questions, please contact our Help Desk.

2. resolved Mar 09, 2026, 08:14 PM UTC

   The delay impacting the latest release of emissions history and emissions forecast data has been resolved. Updated data will now be available across Cirium Sky Warehouse, Sky APIs, and Workbooks. Thank you for your patience while we worked to complete this release.

Read the full incident report →

Started Mar 08, 2026, 05:20 PM UTC· resolved Mar 08, 2026, 06:26 PM UTC

1. investigating Mar 08, 2026, 05:20 PM UTC

   Users of Fleets Analyzer, Values Analyzer, and Dashboard may experience outages or degraded performance. Our engineers are investigating and we will post a further update no later than 21:17 UTC. Please accept our apologies for any inconvenience this issue may cause and contact our Help Desk with any questions.

2. resolved Mar 08, 2026, 06:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 05, 2026, 11:34 AM UTC· resolved Mar 09, 2026, 09:15 AM UTC

1. investigating Mar 05, 2026, 11:34 AM UTC

   We are investigating issues with the Fleets Analyzer - Trend and Projection tabs. When applying Event Type filters (e.g. Deliveries, Purchased, Lease Start) in the Aircraft or Aircraft Event contexts, no data is returned in Trend or Projection. Data is returned in Detail and Summary, and in Trend and Projection when applying Event Detail Type filters (e.g. Scheduled delivery of ordered aircraft, Purchased off lease, Lease extended). We will post a further update within 24 hours. Please accept our apologies for any inconvenience this issue may cause and contact our Help Desk with any questions.

2. identified Mar 06, 2026, 09:39 AM UTC

   We have identified the issue affecting Trend and Projection searches when Event Type filters are applied. We are currently testing the fix and have schedule the live release for the morning of Monday 9th March.

3. resolved Mar 09, 2026, 09:15 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 02, 2026, 03:25 PM UTC· resolved Mar 02, 2026, 03:40 PM UTC

1. investigating Mar 02, 2026, 03:25 PM UTC

   We are currently investigating an issue affecting the Sky Stream NOTAM feed, preventing the receipt of data. We will post a further update within 4 hours. Please accept our apologies for any inconvenience this issue may cause and contact our Help Desk with any questions.

2. monitoring Mar 02, 2026, 03:30 PM UTC

   The feed has been restored after a temporary outage. We are monitoring performance closely.

3. resolved Mar 02, 2026, 03:40 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 26, 2026, 05:46 PM UTC· resolved Feb 27, 2026, 09:20 AM UTC

1. investigating Feb 26, 2026, 05:46 PM UTC

   We have identified an intermittent issue affecting all New Diio Schedule and Traffic reports, Market Alerts, Advance Bookings and Schedule Snapshot. Users may observe server errors when attempting to run reports. This issue does not affect SRS Analyzer or Diio Mi. We will post a further update within 24 hours. Please accept our apologies for any inconvenience this issue may cause and contact our Help Desk with any questions.

2. resolved Feb 27, 2026, 09:20 AM UTC

   This incident has been resolved. The performance issues are addressed and application is stable now. We will continue to closely monitor to ensure everything remains stable and will provide further updates if needed.

Read the full incident report →

Started Feb 26, 2026, 10:56 AM UTC· resolved Feb 26, 2026, 04:09 PM UTC

1. investigating Feb 26, 2026, 10:56 AM UTC

   Users of Fleets Analyzer and Values Analyzer may experience outages or degraded performance due to a load balancer issue . Our engineers are investigating and we will post a further update no later than 18:50 UTC. Please accept our apologies for any inconvenience this issue may cause and contact our Help Desk with any questions.

2. resolved Feb 26, 2026, 04:09 PM UTC

   The incident has been resolved and all services are performing as expected.

Read the full incident report →

Started Feb 24, 2026, 03:24 AM UTC· resolved Feb 26, 2026, 10:44 PM UTC

1. identified Feb 24, 2026, 03:24 AM UTC

   An issue has been identified within our values database that impacted certain valuations, causing Full‑Life values to be reported higher than intended. 1. Ran valuation on Values Analyzer between July 16th 2025-Feb 20th 2026. - Boeing 737 Max BBJ with LEAP 1B28C engines 2. Ran valuation on Values Analyzer between Jan 1st 2026 - Feb 20th 2026 - Learjet 75 with TFE 731 40-BR engines 3. Ran valuation on Values Analyzer between Jan 1st 2026 - Feb 20th 2026 - Boeing 767 with CF6-80C2B6F engines Our engineering team is currently working to correct this issue, with an estimated resolution time of approximately one week. Until the issue is fully resolved, values for this aircraft type will be temporarily unavailable in Values Analyzer. Once the fix is completed, we will post an update if you may rerun the valuation. If you require an accurate revised valuation urgently, please contact [email protected] or your Cirium account manager for assistance. Any Values Analyzer credits used during this period for the affected aircraft or engines will be automatically refunded to your account in due course. We sincerely apologize for this technical issue and any inconvenience it may have caused.

2. resolved Feb 26, 2026, 10:44 PM UTC

   We are pleased to inform you that our engineers have resolved the technical issue, and the values will be available again in the Values Analyzer starting tomorrow morning. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Feb 23, 2026, 05:12 PM UTC· resolved Feb 23, 2026, 11:19 PM UTC

1. investigating Feb 23, 2026, 05:12 PM UTC

   We are currently investigating an issue with today's flight schedule load that is affecting the Cirium Sky APIs, Warehouse and Stream, along with Schedule File deliveries. We will provide the next update no later than 2026-02-24 01:00 UTC. Please accept our apologies for any inconvenience this issue may cause and contact our Help Desk with any questions.

2. investigating Feb 23, 2026, 05:16 PM UTC

   We are continuing to investigate this issue.

3. resolved Feb 23, 2026, 11:19 PM UTC

   The underlying schedule data issue for flights operating today has been corrected and successfully deployed. Flight data processing has resumed as expected, and we are seeing normal behavior. We will continue to closely monitor to ensure everything remains stable and will provide further updates if needed.

Read the full incident report →

Started Jan 30, 2026, 11:28 PM UTC· resolved Feb 01, 2026, 01:35 AM UTC

1. investigating Jan 30, 2026, 11:28 PM UTC

   We are investigating an issue where the Connections API is returning no results for queries with departure dates on or after January 31, 2026. Queries for a departure date of today (January 30, 2026) are returning expected results. We will provide another update by 03:00 UTC on 2026-01-31.

2. investigating Jan 31, 2026, 02:34 AM UTC

   We have identified the issue and it is only affecting cargo type searches. We are investigating the cargo data pipeline and will provide updates as more information becomes available. We will provide another update by 03:00 UTC on February 1, 2026. Thank you for your patience and apologies for any inconvenience.

3. resolved Feb 01, 2026, 01:35 AM UTC

   The issue with Connections API has now been resolved. Departure dates on or after 1/31/2026 in Connections API - Cargo connections is now available for querying. Thank you for your continued patience and understanding.

Read the full incident report →

Started Jan 29, 2026, 11:19 AM UTC· resolved Jan 29, 2026, 04:38 PM UTC

1. investigating Jan 29, 2026, 11:19 AM UTC

   Our data processing infrastructure is running behind. Cirium Sky Schedule File customers will experience delays in receiving today's deliveries. Engineering is currently investigating and we will provide an update no later than 15:20 UTC. Please accept our apologies for any disruption caused.

2. investigating Jan 29, 2026, 03:31 PM UTC

   We are continuing to investigate the issue that is delaying today's Sky Schedule Files delivery. We will post a further update on or before 19:20 UTC. Apologies for ongoing disruption.

3. resolved Jan 29, 2026, 04:38 PM UTC

   The incident has been resolved and today's file deliveries are now in progress. Thank you for your continued patience and understanding.

Read the full incident report →

Started Jan 28, 2026, 11:07 AM UTC· resolved Jan 28, 2026, 11:43 AM UTC

1. identified Jan 28, 2026, 11:07 AM UTC

   We’re experiencing degraded performance with Cirium Sky Stream caused by maintenance activity on an upstream dataset. Users may notice the late arrival of status updates. We expect the service to restored by 12:00 UTC, however it might take a little longer for the systems to fully recover. Please accept our apologies for any disruption caused.

2. resolved Jan 28, 2026, 11:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 15, 2026, 06:55 AM UTC· resolved Jan 27, 2026, 04:57 PM UTC

1. investigating Jan 14, 2026, 10:40 PM UTC

   We’re currently experiencing degraded performance issues with the Advance Booking report. Advance Booking Compare functionality is currently unavailable. The rest of the Advance Booking functionality has not been impacted. Our team is currently working to restore normal performance levels. We apologize for any inconvenience. Advance Booking users may be affected.

2. investigating Jan 15, 2026, 06:55 AM UTC

   We are continuing to investigate the issue and will provide another update by 14:48 UTC on 2026-01-15. Our apologies again for the inconvenience. Please contact our Help Desk with any questions.

3. investigating Jan 15, 2026, 06:56 AM UTC

   We are continuing to investigate this issue.

4. investigating Jan 15, 2026, 02:56 PM UTC

   We are continuing to investigate the issue and will provide another update by 22:55 UTC on 2026-01-15. Our apologies for the continued disruption. Pease contact our Help Desk with any questions.

5. investigating Jan 15, 2026, 10:59 PM UTC

   We are continuing to investigate the issue and will provide the next update by 06:55 UTC on 2026-01-16. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk.

6. investigating Jan 16, 2026, 06:58 AM UTC

   We are continuing to investigate the issue and will provide the next update by 14:55 UTC on 2026-01-16. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk.

7. identified Jan 16, 2026, 03:36 PM UTC

   We have identified the issue and are actively working on a resolution. The next update will be provided by 22:55 UTC on 2026-01-16. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk. Thank you for your patience, and we’ll share further updates as soon as possible.

8. identified Jan 17, 2026, 07:12 AM UTC

   We have identified the issue and are actively working on a resolution. The next update will be provided by 14:55 UTC on 2026-01-17. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk. Thank you for your patience, and we’ll share further updates as soon as possible.

9. identified Jan 17, 2026, 02:57 PM UTC

   We have identified the issue and are actively working on a resolution. The next update will be provided by 22:55 UTC on 2026-01-17. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk. Thank you for your patience, and we’ll share further updates as soon as possible.

10. identified Jan 17, 2026, 10:56 PM UTC

    We have identified the issue and are actively working on a resolution. The next update will be provided by 06:55 UTC on 2026-01-18. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk. Thank you for your patience, and we’ll share further updates as soon as possible.

11. identified Jan 18, 2026, 06:55 AM UTC

    We have identified the issue and are actively working on a resolution. The next update will be provided by 14:55 UTC on 2026-01-18. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk. Thank you for your patience, and we’ll share further updates as soon as possible.

12. identified Jan 18, 2026, 02:56 PM UTC

    We have identified the issue and are actively working on a resolution. The next update will be provided by 22:55 UTC on 2026-01-18. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk. Thank you for your patience, and we’ll share further updates as soon as possible.

13. identified Jan 18, 2026, 11:12 PM UTC

    We have identified the issue and are actively working toward a resolution. Our next update will be provided by 06:55 UTC on 19 January 2026. We apologize for the continued disruption. If you have any questions, please contact our Help Desk. Thank you for your patience—we will share further updates as soon as they become available.

14. identified Jan 19, 2026, 07:23 AM UTC

    We have identified the issue and are actively working on a resolution. The next update will be provided by 14:55 UTC on 2026-01-19. We apologize for the ongoing disruption. If you have any questions, please contact our Help Desk. Thank you for your patience, and we’ll share further updates as soon as possible.

15. identified Jan 19, 2026, 01:06 PM UTC

    Our engineers are working on a fix for the missing Compare functionality, with live release expected by the end of this week. Please check back for further updates.

16. identified Jan 20, 2026, 07:01 AM UTC

    We have identified the issue causing the missing Compare functionality and are actively working on a resolution. Our engineers are implementing a fix, with a live release expected by the end of this week. We apologize for the ongoing disruption and appreciate your patience. If you have any questions, please contact our Help Desk.

17. identified Jan 20, 2026, 04:35 PM UTC

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

18. identified Jan 24, 2026, 02:31 AM UTC

    We are continuing to test a fix, with production deployment targeted for Tuesday, 27th January. We will provide another update once a fix is deployed. Thank you for your continued patience.

19. resolved Jan 27, 2026, 04:57 PM UTC

    This incident has been resolved. Users can now run comparisons for multiple airports, cities, countries, and continents.

Read the full incident report →

Started Jan 09, 2026, 12:06 PM UTC· resolved Jan 09, 2026, 11:57 PM UTC

1. investigating Jan 09, 2026, 12:06 PM UTC

   We are currently experiencing downtime on the Journey platform. Our team is actively working to resolve the issue by restarting all services and performing necessary checks. We will provide updates as soon as the system is restored. Thank you for your patience.

2. identified Jan 09, 2026, 04:26 PM UTC

   We have identified the issue and are conducting tests to ensure data integrity.

3. resolved Jan 09, 2026, 11:57 PM UTC

   The incident has been resolved and systems remain stable. We are continuing to run tests to ensure everything will continue to function as expected.

Read the full incident report →

Started Jan 08, 2026, 04:22 PM UTC· resolved Jan 08, 2026, 05:22 PM UTC

1. identified Jan 08, 2026, 04:22 PM UTC

   We are currently performing unscheduled maintenance on Advanced Bookings. Customers may experience degraded performance during this time. We will provide the next update by 20:20 UTC on 2026-01-08. Thank you for your patience and understanding.

2. resolved Jan 08, 2026, 05:22 PM UTC

   Our maintenance is now complete and the Advanced Bookings product is operating normally. If you experience any issues, please reach out to our Help Desk for assistance.

Read the full incident report →

Started Dec 24, 2025, 12:18 PM UTC· resolved Dec 24, 2025, 01:03 PM UTC

1. investigating Dec 24, 2025, 12:18 PM UTC

   We would like to inform that currently Journey production application is down due to Azure Open AI server internal error. We will update once the service is up and running in production. If you have any questions or need assistance, please reach out to our support team.

2. resolved Dec 24, 2025, 01:03 PM UTC

   This incident has been resolved.

Read the full incident report →