ShipHawk Outage History

ShipHawk is up right now

ShipHawk had 5 outages in the last 2 years totaling 49h 9m of downtime — averaging 0.2 incidents per month.

There were 5 ShipHawk outages since June 20, 2025 totaling 49h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://shiphawk.statuspage.io

Minor February 23, 2026

FedEx Web Services degraded performance

Detected by Pingoru
Feb 23, 2026, 08:12 PM UTC
Resolved
Feb 24, 2026, 10:52 PM UTC
Duration
1d 2h
Affected: FedEx Web Services
Timeline · 2 updates
  1. identified Feb 23, 2026, 08:12 PM UTC

    We are seeing a degraded performance with FedEx web services, some customers reported issues with booking shipments. FedEx has acknowledged an issue on their end. We are actively monitoring the situation and will provide updates as soon as more information becomes available or the issue is resolved.

  2. resolved Feb 24, 2026, 10:52 PM UTC

    Resolved by FedEx.

Read the full incident report →

Notice October 20, 2025

Major AWS service outage

Detected by Pingoru
Oct 20, 2025, 08:37 PM UTC
Resolved
Oct 20, 2025, 11:28 PM UTC
Duration
2h 51m
Timeline · 3 updates
  1. investigating Oct 20, 2025, 08:37 PM UTC

    Amazon Web Services had a major outage today that effected a large number software services across the internet, including ShipHawk. While ShipHawk's software did not go down, the outage has led to intermittent reliability for many parcel and LTL carriers regarding rating and label generation. We are working with AWS to resolve these issues as soon as possible. https://health.aws.amazon.com/health/status

  2. monitoring Oct 20, 2025, 08:56 PM UTC

    Amazon Web Services had a major outage today that effected a large number software services across the internet, including ShipHawk. While ShipHawk's software did not go down, the outage has intermittently affected some carriers regarding rating and label generation. Everything is working currently and we are working with AWS to ensure system responsiveness. https://health.aws.amazon.com/health/status

  3. resolved Oct 20, 2025, 11:28 PM UTC

    The AWS issue affecting carriers has been resolved.

Read the full incident report →

Notice October 10, 2025

Partial USPS Endicia Web Services outage

Detected by Pingoru
Oct 10, 2025, 05:51 PM UTC
Resolved
Oct 10, 2025, 06:18 PM UTC
Duration
26m
Affected: USPS via Endicia
Timeline · 2 updates
  1. investigating Oct 10, 2025, 05:51 PM UTC

    We are seeing a degraded performance with USPS Endicia web services. We will continue to monitor as USPS Endicia works to resolve this. https://status.endicia.com

  2. resolved Oct 10, 2025, 06:18 PM UTC

    Resolved by USPS Endicia

Read the full incident report →

Notice September 29, 2025

WWEX / SpeedShip services outage

Detected by Pingoru
Sep 29, 2025, 06:05 PM UTC
Resolved
Sep 29, 2025, 10:40 PM UTC
Duration
4h 34m
Timeline · 2 updates
  1. identified Sep 29, 2025, 06:05 PM UTC

    Customers using WWEX / SpeedShip integrations may experience issues with rating and booking shipments due to an outage of the WWEX / SpeedShip API. The provider has notified us that they are actively working on a resolution. We will continue monitoring and provide updates as they become available.

  2. resolved Sep 29, 2025, 10:40 PM UTC

    Confirmed as resolved by WWEX.

Read the full incident report →

Minor June 20, 2025

Degraded performance with PrintNode

Detected by Pingoru
Jun 20, 2025, 01:30 PM UTC
Resolved
Jun 21, 2025, 04:07 AM UTC
Duration
14h 37m
Affected: WMSTMS
Timeline · 4 updates
  1. identified Jun 20, 2025, 01:30 PM UTC

    PrintNode is currently experiencing connectivity issues. Some regions may be experiencing degraded performance when attempting to print. See https://www.printnode.com/en/status for details.

  2. identified Jun 20, 2025, 01:42 PM UTC

    Connectivity was restored to normal approximately 7 minutes ago; we are monitoring the situation and will post further information if and when it becomes available.

  3. monitoring Jun 20, 2025, 05:21 PM UTC

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

  4. resolved Jun 21, 2025, 04:07 AM UTC

    This incident has been resolved.

Read the full incident report →