50 Webshipper incidents · février 2022 — official updates, affected components, duration and resolution details.
We detected an issue on API V2 - Health at 2026-08-06 17:24 UTC. Get "https://monitoring.api.webshipper.io/health": request timed out.
Service restauré après 1m. Merci de votre patience.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous avons détecté un problème sur l'API V2 - Taux à 2026-08-06 17:23 UTC. Post "https://monitoring.api.webshipper.io/v2/rate quotes": demande timed out.
Service restauré après 1m. Merci de votre patience.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
We are currently experiencing slow response times and errors from DAO's IT systems. This can result in errors on shipment creation, label generation and updating tracking information. We will update this incident as soon as we receive any news.
This incident has been resolved.
GLS is timing out on most shipment booking requests. The carrier's support team has been contacted. We will post when we have more updates.
GLS have acknowledged the issue and confirmed it is isolated to international labels. We are actively monitoring the situation.
We are closing this incident, as we have not seen any new issues/reports in the past hours.
We are currently experiencing slow response times from PostNord's API systems. We have notified PostNord about the issue and they are currently working to resolve the problem. We will update this incident as soon as we receive any news. https://apistatus.postnord.com/
The incident has been resolved - https://apistatus.postnord.com/
We are currently experiencing an issue affecting shipments booked via DSV (including GLS services), where bookings may fail with an error during processing. DSV has confirmed they are experiencing issues with their rate calculation (service quote) system. - DSV is aware of the issue and actively investigating - No confirmed ETA yet, though initial indications suggest a resolution may be possible within the next hours - If you encounter this issue, we recommend retrying later - For urgent shipments, please contact DSV directly for guidance
The issue affecting shipments via DSV has now been resolved. DSV has confirmed that their rate calculation system is functioning again, and bookings are being processed as expected. If you previously experienced errors, you should now be able to proceed with bookings normally.
We are currently experiencing a degraded performance of PostNord Denmark. The issue has been found and we're currently working on a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Danske Fragtmænd API had issues and was not respoding to calls. We received the confirmation from the carrier that they have solved the issues on their side, but we can still see some issues in Webshipper. We are currently monitoring if it's resolved.
This incident has been resolved.
Bring is currently having issues with their API not returning Pickup points. For more details, check Bring's webpage for status: https://status.bring.systems/
The issue has been fixed on Bring side and they are monitoring.
This incident has been resolved.
We have ongoing timeout errors with Postnord, and we are working on a fix.
Fix deployment should be ready within the next 10 minutes. We will update with more info once completed.
The first deploy did not fix the issue. We are investigating another possible fix and will have more info shortly.
The latest fix restored services. All requests are coming in successfully at the moment and services are green. We will continue to monitor but seems issue is resolved.
All services are operational. No more errors encountered.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
DHL is experiencing issues with their API connection.
DHL is running normally.
We are seeing some downtime on some of our internal support tools. This may cause some delays in our handling of support requests. The incident does not affect Webshippers core platforms - but it may affect external systems like Shopify and carriers. The issues is related to recent status messages posted by Cloudflare. For more information, please see their status page at https://www.cloudflarestatus.com/
Our support tool and Shopify are running again. We apologize for any delays in responses.
This incident has been resolved.
DSV Xpress is experiencing downtimes, please refer to their status page: https://www.dsv.com/da-dk/online-services
DSV is still experiencing downtime, please continue to refer to their status page for updates https://www.dsv.com/da-dk/online-services
Cloudflare have reported a major outage affecting several services. While our services are not directly affected this has affected some third party carriers. Please see Cloudflares status page at the link below for more details. cloudflarestatus.com
Cloudflare have confirmed that their services returned to normal. Closing incident.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have experienced intermittent disruptions to our production systems due to operational challenges at AWS, including issues affecting the service provider hosting our System Status page. Some carrier connections have been impacted by the AWS-related issues. The AWS service status page can be accessed here: https://health.aws.amazon.com/health/status We are seeing improvements across the board and we will provide more updates when the services are back to normal.
According to AWS status page Amazon is still working on fully recovering AWS issues. However we now seem to have all affected services on our side stabilized and we see response times are back to normal. We continue monitoring the situation closely.
This incident has been resolved.
We are experiencing disruptions on several carriers with the error "The communication with the carrier's web service took too long and was intrerupted. We are investigating at the moment.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We made an update into 2 factor authentication. We are making a rollback to the code and operation will resume shortly.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
At noon today we became aware that our backend system + API wasn't responding and hasn't been responding between 13:19:28 to 13:26:28 GMT+1. Within five minutes both were fully restored and working as expected again, but we are investigating what the root cause has been and if there are any implications to consider. We recommend to check your printing clients to verify they are still connected and apologize for any inconvenience this may have caused!
API and backend systems restored, investigating root cause and implications.
This incident has been resolved.