Investigating - Due to the coronavirus, carriers need to adapt their services. This may result in increased shipping restrictions or delays.
Please find up-to-date information in our Help Center: https://support.shipcloud.io/de/collections/2209298-corona-update

In the news ticker and with helpful tips for your shipping, we will keep you informed about upcoming changes in the foreseeable future.

----------------------------

Coronavirus: Auswirkungen auf Ihren Versand
Aufgrund des Coronavirus müssen die Versanddienstleister ihre Services anpassen. So kann es vermehrt zu Einschränkungen im Versand oder Verzögerungen kommen.
Aktuelle Informationen hierzu finden Sie in unserem Help Center: https://support.shipcloud.io/de/collections/2209298-corona-update

Im Newsticker sowie mit hilfreichen Tipps für Ihren Versand halten wir Sie so in absehbarer Zeit über bevorstehende Änderungen auf dem Laufenden.
Mar 18, 15:43 CET
API (api.shipcloud.io) ? Operational
90 days ago
100.0 % uptime
Today
WebUI (app.shipcloud.io) ? Operational
90 days ago
100.0 % uptime
Today
Developer Portal (developers.shipcloud.io) Operational
90 days ago
100.0 % uptime
Today
Website (www.shipcloud.io) ? Operational
90 days ago
100.0 % uptime
Today
Carrier APIs ? Operational
90 days ago
99.33 % uptime
Today
DHL ? Operational
90 days ago
94.07 % uptime
Today
DPD ? Operational
90 days ago
100.0 % uptime
Today
GLS ? Operational
90 days ago
100.0 % uptime
Today
Hermes ? Operational
90 days ago
100.0 % uptime
Today
Iloxx ? Operational
90 days ago
100.0 % uptime
Today
UPS ? Operational
90 days ago
100.0 % uptime
Today
DHL Express ? Operational
90 days ago
100.0 % uptime
Today
DPAG ? Operational
90 days ago
99.94 % uptime
Today
Hermes (HSI) ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Response Time
Throughput
Past Incidents
Jun 15, 2021

No incidents reported today.

Jun 14, 2021

No incidents reported.

Jun 13, 2021

No incidents reported.

Jun 12, 2021

No incidents reported.

Jun 11, 2021

No incidents reported.

Jun 10, 2021
Resolved - We have not received an update from DHL, but recent tests show that the issue no longer exists.
Jun 10, 12:29 CEST
Monitoring - We have deployed a temporary fix and we are monitoring the results. The DHL customs declaration documents (CN23) should include the description of contents entries again.
We will keep the incident open and post updates until DHL has resolved the issue.
Jun 7, 21:36 CEST
Identified - Unfortunately, the problem of the incorrect customs declaration documents (CN23) could not be solved by DHL yet. We are currently working intensively on an alternative solution, which is expected to be available on Monday, June 8th, 2020.
Despite our information, the electronic data transfer to customs is not sufficient and most of the shipments are currently rejected by customs.
As an interim solution, we recommend using the customs documents from DHL and filling them in manually (https://www.dhl.de/content/dam/images/pdf/dhl-zollinhaltserklaerung-cn23-032020.pdf), or withhold your dutiable shipments until Monday.
Please excuse the inconvenience this may cause.
Jun 5, 11:10 CEST
Investigating - The description of contents are currently missing on the documents created by DHL for the customs declarations. We have reported the issue to DHL.
May 19, 12:23 CEST
Resolved - This incident has been resolved.
Jun 10, 12:15 CEST
Monitoring - We've been notified by DHL of the following problem with their sandbox system:
> due to today's changeover of the sandbox environment for the Business Customer Shipping API to a new platform, there is currently some misbehaviour in the sandbox area.
>
> Among other things, this particularly affects some services that can no longer be accessed because the corresponding permissions are no longer available.
>
> Also, the use of the sender reference in the sandbox temporarily no longer works, so it is currently not possible to create labels via the sender reference or with a logo.
>
> All shipment numbers assigned by the sandbox currently end with the letter "C".
Jan 26, 16:11 CET
Resolved - We have not received an update from DHL, but recent tests show that the issue no longer exists.
Jun 10, 12:13 CEST
Monitoring - We've been notified by DHL of the following incident:
> due to a malfunction, error 1000 "General Shipment Backend Error" occurs in the sandbox under the UpdateShipment and DeleteShipment operations. We are working to find a solution.
Mar 15, 15:22 CET
Resolved - As of today, around 10:25 a.m., DHL has fixed the problem with the missing country name in the web service response on their part as well.
Jun 10, 12:07 CEST
Monitoring - Since DHL has not been able to solve the issue so far, we have implemented a fix at short notice that bypasses the bug. We are monitoring the results
Jun 9, 18:54 CEST
Investigating - We are currently investigating an issue with missing receiver country on DHL PDF A6 labels. The issue is caused by an unannounced change in the DHL web service response. We have forwarded the issue to DHL.
Until further notice DHL A6 labels should not be used. Please use A5 labels or a different carrier.
Jun 9, 17:28 CEST
Jun 9, 2021
Jun 8, 2021

No incidents reported.

Jun 7, 2021

No incidents reported.

Jun 6, 2021

No incidents reported.

Jun 5, 2021

No incidents reported.

Jun 4, 2021

No incidents reported.

Jun 3, 2021

No incidents reported.

Jun 2, 2021

No incidents reported.

Jun 1, 2021

No incidents reported.