Hermes BorderGuru incident

Service Outage - Tracking Data and Preadvice Provisioning

Major Resolved View vendor source →

Hermes BorderGuru experienced a major incident on February 21, 2020 affecting Preadvice Provisioning and Trackingdata Provisioning and 1 more component, lasting 2h 34m. The incident has been resolved; the full update timeline is below.

Started
Feb 21, 2020, 06:18 AM UTC
Resolved
Feb 21, 2020, 08:53 AM UTC
Duration
2h 34m
Detected by Pingoru
Feb 21, 2020, 06:18 AM UTC

Affected components

Preadvice ProvisioningTrackingdata ProvisioningPUDO Data Provisioning

Update timeline

  1. investigating Feb 21, 2020, 06:18 AM UTC

    We are investigating an incident which relates to the availability of the Tracking Data Provisioning. Impact: Since 21.02.2020 around 02:00 am the Tracking Data and Preadvice Provisioning experienced an outage, thus currently tracking data and preadvices will not be provisioned. Incident resolution and root cause analysis are ongoing. We will provide updates either every 60 minutes or event triggered.

  2. monitoring Feb 21, 2020, 07:20 AM UTC

    The root cause has been identified and eliminated. System is now back up and running, but a bit slow since dealing with the huge amount of queued files currently. So far it seems no data is lost but we will monitor and provide an update in latest 60 minutes.

  3. monitoring Feb 21, 2020, 08:40 AM UTC

    Please find below the status update which relates to the Tracking Data and Preadvice Provisioning incident from 21.02.20 - 02:00 am. Current Sutuation: System is still in an unstable mode. There is still a delay in data provisioning. Incident resolution and root cause analysis are still ongoing. We will provide the next update in 60 minutes or event triggered whichever applies.

  4. resolved Feb 21, 2020, 08:53 AM UTC

    Please be informed that the "Tracking Data and Preadvice Provisioning" incident from 21.02.2020 - 02:00 am was resolved. All queued data has been sent out. No data was lost. Regular communication related to this incident will be discontinued. The root cause analysis is still ongoing. A final message with the root cause will be published here as soon as available.