ShipHawk incident

Service disruption on instance

Minor Resolved View vendor source →

ShipHawk experienced a minor incident on April 17, 2024 affecting Shipping APIs and sh-default and 1 more component, lasting 2h 58m. The incident has been resolved; the full update timeline is below.

Started
Apr 17, 2024, 08:26 PM UTC
Resolved
Apr 17, 2024, 11:25 PM UTC
Duration
2h 58m
Detected by Pingoru
Apr 17, 2024, 08:26 PM UTC

Affected components

Shipping APIssh-defaultTMS

Update timeline

  1. investigating Apr 17, 2024, 08:26 PM UTC

    We are currently experiencing a service disruption on sh-default environment. Our DevOps team is working to identify the root cause and implement a solution. Further details will be provided shortly. Customer Impact: Some customers are reporting that they are unable to open the WebPortal.

  2. monitoring Apr 17, 2024, 08:38 PM UTC

    The system is back to normal after restarting ElasticSearch data nodes which spiked in CPU usage. We're monitoring the situation and are investigating the root cause.

  3. resolved Apr 17, 2024, 11:25 PM UTC

    This incident has been resolved.