Is nShift - Webshipper Down Right Now? Check if there is a current outage ongoing.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Dear partner,We would like to inform you about an upcoming maintenance of the Webshipper API.Planned maintenance is moved up one day, due to public holiday (Ascension Day) on the 29th of May. Maintenance will therefore be done Tuesday in the hours between 12:00 - 13:00 GMT+1.During the maintenance hours, the print service will temporarily go offline and restart shortly after. We apologize for any inconveniences this may cause.Kind regards, Your Webshipper Team

This incident has been resolved.

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

We made an update into 2 factor authentication. We are making a rollback to the code and operation will resume shortly.

This incident has been resolved.

API and backend systems restored, investigating root cause and implications.

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!

DAO is working again.

We are currently experiencing issues from DAO's systems with the error "The order could not be shipped. An error during address lookup.". They are currently working to resolve the problem. We will update this incident as soon as we receive any news.

This incident has been resolved.

The issue has been fixed and the emails are going out again. We are monitoring.

We are currently experiencing issues with sending the email notifications and we are working on solving it.

Follow this page for the postmortem updates: [https://status.nshiftportal.com/incidents/hwdmk2xq4tm7](https://status.nshiftportal.com/incidents/hwdmk2xq4tm7)

This incident has been resolved.

Recovery is still in progress for the affected carriers. They are partially working but some more configuration is needed.

We are still working on the issue.

A workaround for the issue has been identified by CrowdStrike. We are working with AWS to try to apply this fix across our systems. This will take some time as we have to go through each machine for the fix, will return with a timeline.

We have identified that our infrastructure have been affected with downtime due to issues with a 3rd party tool Security Tool Crowdstrike. We have identified a workaround to disable Crowdstrike that we are trying to apply on our production environment. Crowdstrike themselves have also just announced they are working on the problem.

We had connection issues with different carriers: Evri, DPD, Sandgroup and Airmee on 2024-06-19 07:47 and was resolved 2024-06-19 08:52

This incident has been resolved.

Several functions within Webshipper are experiencing unresponsive performance or are not functioning as intended. Our team is currently investigating these issues. Areas that are affected: Shipment history Bulk print Prints API Order import

This incident has been resolved.

A hotfix has been deployed and we are monitoring the results.

The DPD Global integration is currently experiencing issues resulting in downtime. We are investigating and working on resolving this with the carrier ASAP.

Time stamp: 4th of May 14:00 to 5th of May 09:20 Issue: internal Errors on shipments Description:  In an attempt to expand and upgrade the foundations for barcode formatting for all EDI based carrier integrations, we encountered some unexpected issues when changes were made to the barcode creation part of Webshippers API and carriers pool, which had unintended consequences. Due to these changes, duplicated barcodes were sometimes inadvertently generated, leading to Internal server errors on shipments and other errors with shipments such as track & trace issues. Although the faulty code was quickly reverted in the afternoon and successfully resolving the problem for the carrier pool service, a part of the code difference on the API was not reverted correctly on the new build due to an internal error from Bitbucket, behind the build process, creating an out of sync main branch, which caused the incident to persist for longer than intended. Due to the revert on the carrier pool being successful, some of the errors shown through the API were removed leading to false positives late in the afternoon. When discovered next morning, our team worked to address the issue as fast as we could, and the API was fully rolled back to the previous version on the morning of 5th of May, effectively closing the incident. Going forward, we will look into and implement better and stricter testing protocols for barcodes generation to prevent similar issues from arising in the future.

All issues related to internal server error and barcodes have been resolved since this morning.

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

We are currently experiencing internal issues in the system with some shipments. We are working intently on fixing all issues and apologize for the issues at hand.

All failed shipments due to barcode related issues, can now be re-shipped.

All deploys regarding barcode changes are reverted and normalized again. Failed shipments in this time period should now be attempted shipped again.

In our afternoon deploy, there was an issue with barcode formats and this has caused some issues with generating shipments. We are currently rolling back all deploys regarding barcodes. We expect it fixed within 30 mins. All failed shipments will at that time need to be attempted shipped again in order to be successfully booked. We apologize for the inconvenience.

All reports are confirming that the issue is resolved.

We are continuing to monitor for any further issues.

We have successfully rolled back all related deploys. Please try sending all your orders again to see if all failed orders can be shipped. Thank you.

Latest deploy last night seems to have caused issues with Postnord. We are currently rolling back all deploys related to the issue. Please do not call our support team, we are doing all we can to implement a fix as soon as possible. Stay tuned here for updates.

We are currently experiencing issues with Postnord and other carrier integrations with timed out requests but are working as fast as possible to identify and solve the issue. Please stay tuned for updates here.

This incident has been resolved.

Link Logistics are currently experiencing issues with carrier services. They are working intently on fixing the issue. Please contact Link logistics for further details.

This incident has been resolved.

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

The issue seems to be only affecting GLS Services through DSV Xpress. For more information, contact DSV Xpress.

DSV XPRESS is currently experiencing issues. Please contact DSV for further details

This incident has been resolved.

Postnord is currently experiencing issues with their drop points. They are working urgently to fix the issue. We expect Postnord to update their status page with more info. Keep updated here: https://developer.postnord.com/apis/status If you wish, you can temporarily hide your Postnord drop points in your checkout until the issue has been resolved. Best regards Your Webshipper team.

API update deployed.

Dear Customer, We are updating our API around 13:45. Print services may be affected and require a restart. If any problems, feel free to reach out. Thank you and have a nice day.

This incident has been resolved.

Lastest update. We will deploy a new API version around 15:30. This should improve search functionality quite a bit. We have also added multiple resources in the system to ensure no bottleneck incidents can occur. This is considered the highest priority and we are doing everything we can to ensure smooth usability. We understand how important this functionality is for everyone and apologize for the inconvenience this causes.

We are currently having issues with slow load times on the order and shipment overview. we are doing all we can to implement a fix. Thank you for your patience.

Reports confirm that all previously missing shipping rates in Shopify checkout are now visible again. If you do not see your Webshipper rates already, please check that you have enabled Webshipper Rate Provider in your Shopify zones and your Webshipper rates are set to be visible in your Webshipper account. All temporarily flat rates created in Shopify can be disabled again once you can confirm your Webshipper rates are visible in Checkout.

Latest update: After much effort and close dialog with Shopify Partner Support, we have been able to narrow down the issue and be able to create a fix that hopefully will solve all missing Webshipper Shipping rates in Shopify checkout. We would like your help to check if everything is working as intended with Webshipper rates again in your checkout. You may need to refresh your Shopify zone and connect to Webshipper Rate Provider again inside Shopify. Also if you have set your Webshipper rates as hidden, they will need to be made visible again. Try with one rate first to see if it will appear and if all is working as intended, you can freely add the rest. We would like a mail to support@webshipper.com if your rates are not working again as intended.

Latest update: We are still in close dialog with Shopify Partner Support regarding the issue of "Missing Rates in checkout". Shopify has requested API logs and we are currently looking into building more extensive logging for Shopify. However, our API requests match the Shopify documentation and we are therefore currently investigating what may be missing in that documentation together with Shopify. We are still unable to determine if the current approval process to make Webshipper's app listed in Shopify, is directly related to the issue or not. For now, we will not rule out any possible options.

More reports have come in to confirm that if you update your existing shipping rates and zones in Shopify, this general issue will apply and all your shipping rates from Webshipper will potentially no longer be displayed in checkout. If you are already affected by the issue, the only solution is to create flat rates in Shopify and match them to your Webshipper rates. Please follow this guide on how to proceed with matching/linking orders to Webshipper rates. https://help.webshipper.com/hc/en-us/articles/360010079357-How-do-I-link-shipping-rates-to-my-orders-

Updated: The Webshipper app have been approved by the automated app checker in Shopify. Webshipper is awaiting the final and manuel approval for our app with Shopify.

Updated: It seems that the issue may be connected to when there have been made a change/update to rates and/or zones in Shopify. This is, however, unconfirmed. But still, we recommend being careful with making updates, as what we are seeing is that once there is one update to one zone, it is causing a general error on all existing shipping rates.

Dear Shopify user We are currently receiving reports from customers that shipping rates are no longer been shown in checkout. In short - we are able to receive API requests from the checkout for shipping rates and we can also confirm that we are sending the rates to checkout as requested. However, something appears to be blocking the actual display of rates in Shopify checkout. We are currently investigating with Shopify Partner Support why Shopify is not displaying the rates. We consider this issue of the highest priority and will be doing everything we possibly can to find the root cause of the block. The reports started after the 1st of November when Shopify required all "unlisted" apps to become "Listed". However, Webshipper has received a continuance until the 1st of December to become "listed" Unfortunately, while Webshipper is in the process of final app approval with Shopify, we are unable to search up errors and locate any issues related to Shopify. It is likely that all issues will be fixed automatically when Webshipper becomes a "Listed" app. It may also simply just allow us to search for errors again once the app is approved. For now, the only workaround solution is that you create Shopify flat rates directly in Shopify and then link/match those rates with your current Webshipper rates. For info on how to please see this guide: https://help.webshipper.com/hc/en-us/articles/360010079357-How-do-I-link-shipping-rates-to-my-orders- If you need help with creating matches/link from flat rates to Webshipper rates or simply have questions regarding the issue, feel free to reach out to us at support@webshipper.com. Best regards from Your Webshipper support team Steffen, Alex, Rasmus K., Rasmus S., Stine & Ninna

This incident has been resolved.

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

We are still working on implementing a fix for this issue. We also like to request that you subscribe to this status page for notifications whenever something is not working as intended. You will not receive newsletters or other non-operational notifications via this Status page.

We are currently experiencing issues with logging into the printer client. Updates will follow.

Resolved All print services have been able to catch up and reconnect for all tenants Also, all search functionality is confirmed back up and running as usual. We apologize for the inconvenience this caused.

Print is currently not operational. We are working as fast as we can to implement a fix. We are implementing a hot fix right now.

We are continuing to work on a fix for this issue as there are still search and print issues active. Updates will follow.

We are implementing a fix on our API to ensure high functionality for all customers. Updates will follow.

Initial search issues have been fixed and all should be up and running again for order and shipment search funtionality. Related print issues are still being investigated and updates will follow.

We are continuing to work on a fix for this issue. Updates will follow here.

We have now doubled our database resources to ensure a high searchability. This may cause a temporary API refresh which can affect print services as well. Updates will follow here.

We are currently experiencing a search issue on the platform. Errors may occur upon searching for orders or shipments. Updates will follow here.

A fix has been implemented and Bring is monitoring the results. Please see Bring status page here: https://status.bring.systems/

Bring is currently experiencing service issues. Please see Bring status page here: https://status.bring.systems/

Our Amazon Webservice ECR repository which holds our build images of all our services, unfortunately, had a rule set up on drop point services to delete images older than 90 days. And drop point service had not been updated for 90 days since this weekend. Thus the ECS \(Which uses these images\) had nothing to pull since the old ones were deleted, this, therefore, resulted in no drop point services. We have now changed the policy rules to only delete if there are more than 5 images instead of 90 days. This will ensure that we will not run into this issue again.

This incident has been resolved.

Unfortunately our drop point service is currently unavailable

This incident has been resolved.

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

Something seems to be affecting Postnord API Servers. For more info click here https://apistatus.postnord.com/apistatus/#/overview

We are currently seeing errors with PostNord drop points. We are working as fast as possible to investigate the issue. Thank you for your patience.

This incident has been resolved.

We are currently experiencing minor issues with: - Waybills - Returns - Return portal Please be aware we are already implementing a fix and expect it all to be solved shortly.

We have continuously monitored the platform's search functionality and load functionality, and with the fix we have implemented, we considder the issue to be solved. We apologize for the inconvenience this has caused. Best regards from your Webshipper team

Update to search issues: A fix has been implemented and is confirmed to increase the platform's efficiency greatly. We will continue to monitor and track the platform search and usability over the next coming hours and ensure all runs smoothly for all.

A fix was implemented yesterday, unfortunately, our initial testing indicates that the issue still remains and platform search and load times are still reduced from the standard usability. We are working hard to solve the issue and apologize for any inconvenience this causes in your day-to-day operations.

We are experiencing that both orders and shipments for customers can take a high amount of time to load. A fix is being implemented and integrated later today. We will continue to observe the issue. Please keep updated on changes here.

We are currently experiencing issues with our search functionality. We are doing everything we can to implement a fix. We apologize for any inconvenience this may cause.

Dear partners & users, We would like to inform you that the issues on Customer Portal have been resolved. API is up and running again. We apologize for any inconvenience caused. Kind regards, Deutsche Post International team

Please be informed that Deutsche Post currently experiencing general issues with their API. They working with the highest priority to solve this issue and will inform all as soon as it is fixed. Remember to subscribe to updates for you and your colleagues.

We are currently receiving error reports on booking requests with Deutsche Post. Error message generated from Deutsche Post is "403 forbidden". We are in contact with Deutsche Post on the matter and will keep you updated as we know more.

After an investigation, it was determined that our search indexing was running a few seconds behind which caused the search function to not generate results as fast as usual. The indexing has been updated and all the indexing that was missing is now completed. All orders and shipments should be searchable once again on the references however, we expect some slight delays that may still occur on searches. Please contact support@webshipper.com if you have any questions to the issue.

We are pushing updates to the API which may result in a required reboot for printer clients. Simply find the program Webshipper Silent Printer and login to your account with your account name and credentials. If in doubt of what your account name is, please see this guide: https://help.webshipper.com/hc/en-us/articles/360010129918-How-to-find-your-ID

We are currently experiencing issues with searching up order/shipment references. Please use the search functionality for on names, id, address or other values rather then the order/shipment reference number. We are investigating the issue and working to resolve it as fast as possible. We apologize for the inconvenience.

A fix has been implemented and we are now able to receive services from Bring via the updated API Endpoint.

Update: Bring have updated their service endpoint and terminated the old endpoint at the same time. We are currently updating the endpoint in Webshipper and expect the services with Bring to be available shortly.

We are currently not receiving any services from Bring API. Bring is currently investigating the issue. As soon as we know more, this issue will be updated.

Everything is confirmed fully operational again. If any questions regarding the incident, please contact DSV EXPRESS for further details.

DSV EXPRESS is currently experiencing downtime on API integrations. Their API team is working as fast as possible to implement a fix.

Shipments with DSV Express are currently getting errors on the validation of API tokens. We are currently investigating this issue with DSV EXPRESS

This incident has been resolved.

The carrier BRING is experiencing server issues. They are currently working on solving the issue and implementing a fix.

This incident has been resolved.

Issues with GLS' API, send.gls.dk and YourGLS 16.05.2022 GLS API, send.gls.dk and YourGLS are not working correctly at the moment. It means some may not be able to create or buy a label. YourGLS are working on the issues. Please wait a while with your shipment and try again later. Details here: https://it.gls.dk/index-en.html

Please be informed that Deutsche Post was facing issues with the label generation of their API. This affected all customers of Deutsche Post. The issue was resolved within less than an hour and everything is now back up and running as usual again. We apologize for any inconvenience this issue causes.

At 2022-02-09 14:35 CET our primary database had a malfunction which caused an automatic failover. Usually automatic failovers stabilise in less than a minute with minimal effect on update, but because of an automatic cleanup job, our primary API instances were not able to respawn new instances since essential build assets had been cleaned up. Webshipper staff, after identifying the issue, instantiated a new deploy of the platform which added the essentials build assets. To mitigate this happening in the future we have modified the cleanup job to not remove essentials assets and will put effort into minimising the time needed to do a full re-deploy. ‌ We sincerely apologize and any inconvenience during this downtime. ‌ Best, The Webshipper Team

This incident has been resolved.

We are currently investigating this issue.

YourGLS is up and running again. You may have to reboot to access the system. We apologize for the inconvenience this has caused. Subscribe to YourGLS status news here: https://gls-group.eu/DK/en/business/customer-information/operational-status

YourGLS server is unresponsive and you will currently be able to see errors with issues with logging in to your YourGLS account as a result.

YourGLS is experiencing downtime. Contact YourGLS for details. Keep updated here: https://gls-group.eu/DK/da/loesninger/kundeinformation/driftsstatus

This incident has been resolved.

PostNord API team has located the issue and is currently working on implementing a fix for all customers.

PostNord DK is returning an error on shipments. The issue is being investigated.

This incident has been resolved.

Bring has implemented a fix and all services have returned to normal. We are monitoring the status of all services.

Bring is currently working on solving the issue with the highest priority. All services should return to normal as soon as the issue is fixed.

https://www.mybring.com/ is currently unavailable. All bring websites and servers are currently offline.

Anyone with a BRING integration will not be able to ship orders until the issue has been resolved. We are currently investigating this issue.

We have received confirmation that the effected services with Deutche Post, are back to normal.

Customers creating shipments using Deutche Post, may experience issues currently. Deutche Post are focused on fixing these errors. Webshipper will monitor the situation and will update this status message - when we have an update from Deutche Post. We apologize for any inconvenience this may have caused.

This incident has been resolved. All shipments can again be booked as usual with YourGLS. The error on the GLS booking server is no longer active and all previously failed bookings can be attempted shipped again. If any questions regarding the matter, please contact GLS.

GLS is currently experiencing issues with their services. Please wait a while when sending your order and try again.

DSV Express is investigating and working on a fix for the issue. If you experience issues with API requests failing when creating shipments, our best advice would be to wait a minute and try again. For further details regarding the issue, contact DSV Express.

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

We are currently seeing booking requests to DSV EXPRESS timed out in DSV's system. Our team is in a dialog with DSV EXPRESS to solve the issue. If you experience issues, please wait a minute or two and try shipping again.

Briefly this morning DAO had a minor spelling error in their SQL database. This caused shipments to report an error: "SQL Query failed: 96-1054/Unknown column 'recevername' in 'field list'" 27 times the error was registered across all accounts in Webshipper, before Dao quickly fixed the error and we could confirm the error was in fact corrected. The DAO It team sends their sincere apology for the inconvenience to all affected.

The incident has been resolved and all shipments should be booked as usual again.

We are currently receiving error reports on DAO, primarily with returns. We have informed DAO who is now investigating the issue.

All services are up and running with Bring again and all orders can be resent for booking.

Bring is experiencing downtime and is working to fix the issue. Please contact Bring for further details. All failed shipments can be attempted resent once the incident is fixed by Bring.

Bring is currently experiencing service issues. We are currently investigating the issue.

The support phone is up and running again.

We are currently having issues with our phone. While we investigate, please reach out to us via e-mail: support@webshipper.com - we hope to have the phone up and running as soon as possible.

This incident is considered resolved as shipments are confirmed operation and as normal.

Update: The issue has been located. Bring has started redirecting to a different URL in the API. We're adding a quick fix to accommodate Bring's changes. We expect it to be working within the next 30 minutes.

Bring is currently experiencing downtime. Are you unable to create shipments with BRING then please wait a while and try again later. If the problem persists, contact Bring for further details.

Operational status: Normal. https://gls-group.eu/DK/en/business/customer-information/operational-status

GLS is currently experiencing slow response time. This affects all customers using YourGLS and GLS Unibox but also PakkeCenterNord and Coolrunner. Contact GLS for further details if you are experiencing continued issues.

This incident has been resolved.

We have received information that the issue at DAO, has been solved. It is possible to book shipment again. We will monitor the service for the time being.

DAO is currently expecting downtime - contact DAO for further details.

A fix has been implemented and all PostNord shipments can now be sent as normal.

PostNord is continuing to work on a fix

PostNord is working to implement a fix

We are currently experiencing issues with international shipments with PostNord. Everything is being done to fix this with PostNord as fast as possible. We apologize for the inconvenience.

This incident has been resolved.

DSV XPRESS has depleted their registered amount of barcodes with GLS and therefore you may see an error message in regards to booking with the DSV EXPRESS and GLS combination. Please contact DSV XPRESS for further details.

This incident has been resolved.

Shopify is experiencing issues. Please keep updated here: https://www.shopifystatus.com/

This incident has been resolved.

DSV Xpress will implement a fix tonight and thus the service should be back to normal again by Thursday morning.

DSV Xpress is currently experiencing issues with their Private Delivery service and is working hard to implement a fix to solve the issue. Until the issue is resolved, it is recommended to apply the service ParcelShop instead.

Today we experienced an issue with Tracking links on DAO Labels. Dao had changed their API logic which resulted in wrongful tracking links and delays in creating shipments. After an open dialog between DAO and Webshipper the issue was quickly resolved and future labels was brought back to normalcy again. Some shipments from earlier this morning may still be affected by the issue. The Issue only affected DAO integrations directly.

The official Danish address register had issues and experienced downtime. This caused issues in Webshipper when trying to call drop point address from their database. We have implemented a failsafe if their database have any issues in the further so addresses will be pulled from google instead. This will ensure more stability and less vunerability in the future. Kind regards from your Webshipper team.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results. Please refresh your browser and try again. Incognito browser will avoid any cache-stored data in your checkout.

We are currently experiencing issues with the drop point selector for Danish addresses with carriers: PostNord, YourGLS, Bring, DAO, DPD and possibly others. We are working as fast as we can to implement a fix. Subscribe to status news to keep updated on errors and issues. We apologize for the inconvience.