shipcloud Outage History

shipcloud is up right now

shipcloud had 13 outages in the last 2 years totaling 64h 38m of downtime — averaging 0.5 incidents per month.

There were 13 shipcloud outages since June 17, 2024 totaling 64h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.shipcloud.io

Major June 2, 2026

DHL Returns partial outage

Detected by Pingoru
Jun 02, 2026, 11:37 AM UTC
Resolved
Jun 02, 2026, 12:26 PM UTC
Duration
49m
Affected: DHL
Timeline · 2 updates
  1. identified Jun 02, 2026, 11:37 AM UTC

    We are currently observing limited availability of DHL Returns functionality and are actively investigating.

  2. resolved Jun 02, 2026, 12:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 13, 2026

DPD: Disruption of service

Detected by Pingoru
May 13, 2026, 07:19 AM UTC
Resolved
May 13, 2026, 08:02 AM UTC
Duration
43m
Affected: DPD
Timeline · 2 updates
  1. monitoring May 13, 2026, 07:19 AM UTC

    The DPD webservices are currently running into timeouts. We're monitoring the situation.

  2. resolved May 13, 2026, 08:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 7, 2026

Outage of service

Detected by Pingoru
May 07, 2026, 06:34 AM UTC
Resolved
May 07, 2026, 06:55 AM UTC
Duration
21m
Affected: API (api.shipcloud.io)WebUI (app.shipcloud.io)
Timeline · 2 updates
  1. investigating May 07, 2026, 06:34 AM UTC

    We are currently investigating this issue.

  2. resolved May 07, 2026, 06:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 28, 2026

UPS disruption of service

Detected by Pingoru
Apr 28, 2026, 06:22 AM UTC
Resolved
Apr 28, 2026, 06:33 AM UTC
Duration
11m
Affected: UPS
Timeline · 2 updates
  1. identified Apr 28, 2026, 06:22 AM UTC

    The issue has been identified and a fix is being implemented.

  2. resolved Apr 28, 2026, 06:33 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 26, 2026

UPS: Disruption of Service

Detected by Pingoru
Apr 26, 2026, 08:00 PM UTC
Resolved
Apr 27, 2026, 07:45 AM UTC
Duration
11h 45m
Affected: UPS
Timeline · 2 updates
  1. investigating Apr 27, 2026, 07:41 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 27, 2026, 07:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 10, 2026

DHL: Disruption of Service

Detected by Pingoru
Apr 10, 2026, 08:18 AM UTC
Resolved
Apr 10, 2026, 08:43 AM UTC
Duration
25m
Affected: DHL
Timeline · 2 updates
  1. identified Apr 10, 2026, 08:18 AM UTC

    The DHL CIG (Customer Integration Gateway) is responding with errors, DHL is already investigating and trying to resolve the issue. https://post-paket-deutschland.status.api.dhl.com/incidents/230797?lang=de

  2. resolved Apr 10, 2026, 08:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 13, 2025

Problems with our cloud provider

Detected by Pingoru
Nov 13, 2025, 03:47 PM UTC
Resolved
Nov 13, 2025, 05:05 PM UTC
Duration
1h 17m
Affected: API (api.shipcloud.io)WebUI (app.shipcloud.io)
Timeline · 2 updates
  1. identified Nov 13, 2025, 03:47 PM UTC

    Due to problems with our cloud provider some carriers and services are currently unavailable. This also affects the usage of all shipcloud owned contracts. We are working hard on mitigating the problems and fixing the issue.

  2. resolved Nov 13, 2025, 05:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 10, 2025

DPD errors with shipcloud contract

Detected by Pingoru
Jul 10, 2025, 08:24 AM UTC
Resolved
Jul 10, 2025, 09:24 AM UTC
Duration
1h
Affected: API (api.shipcloud.io)WebUI (app.shipcloud.io)
Timeline · 2 updates
  1. investigating Jul 10, 2025, 08:24 AM UTC

    The API is partially responding with errors when creating shipment quotes or creating a shipment using shipcloud rates with carrier DPD. We have identified the cause of the problem and are working on a fix.

  2. resolved Jul 10, 2025, 09:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 9, 2025

shipcloud app and API performance

Detected by Pingoru
Jul 09, 2025, 10:02 AM UTC
Resolved
Jul 09, 2025, 10:35 AM UTC
Duration
33m
Affected: API (api.shipcloud.io)WebUI (app.shipcloud.io)
Timeline · 3 updates
  1. investigating Jul 09, 2025, 10:02 AM UTC

    We are investigating reports of degraded performance.

  2. investigating Jul 09, 2025, 10:20 AM UTC

    We are continuing to investigate the issue. Shipments with the carrier UPS are currently running into errors

  3. resolved Jul 09, 2025, 10:35 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 23, 2025

GLS: Disruption of service

Detected by Pingoru
Jun 23, 2025, 07:22 AM UTC
Resolved
Jun 23, 2025, 09:12 AM UTC
Duration
1h 49m
Affected: GLS
Timeline · 2 updates
  1. monitoring Jun 23, 2025, 07:22 AM UTC

    The GLS services are currently slow and/or running into timeouts.

  2. resolved Jun 23, 2025, 09:12 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 30, 2025

DHL Returns API Disruption of Service

Detected by Pingoru
Apr 30, 2025, 02:15 PM UTC
Resolved
Apr 30, 2025, 02:47 PM UTC
Duration
32m
Affected: DHL
Timeline · 2 updates
  1. identified Apr 30, 2025, 02:15 PM UTC

    The DHL Returns API is currently not available.

  2. resolved Apr 30, 2025, 02:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 29, 2024

DHL API performance degraded

Detected by Pingoru
Oct 29, 2024, 10:38 AM UTC
Resolved
Oct 30, 2024, 08:03 AM UTC
Duration
21h 25m
Affected: DHL
Timeline · 3 updates
  1. identified Oct 29, 2024, 10:38 AM UTC

    The DHL Shipping and Returns API currently shows unusually long response times.

  2. identified Oct 30, 2024, 08:01 AM UTC

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

  3. resolved Oct 30, 2024, 08:03 AM UTC

    This incident has been resolved.

Read the full incident report →