Pagero Service Status

Resolved: Billing and transfer of shipments is back at a normal pace.

Identified: This issue is still being investigated.

Identified: There has been small patches deployed during the week, which has had some improvements on processing speed. We are still working on further fixes.

Investigating: This issue is still being investigated.

Identified: This issue is still under investigation.

Identified: We have released a patch for slow processing of invoices and shipments. The patch brought the time for processing down, but not enough. This is still under investigation.

Monitoring: All loadlists have been processed. We are monitoring this for the moment.

Monitoring: The fix has been deployed to PROD, and we could find new loadlists. We are monitoring the situation for now.

Identified: We believe we've found the root cause of the loadlists issues. A patch will be delivered in about 30 minutes.

Identified: The issues with routing has been solved. Pre-defined report has been fixed. Still investigating loadlists and slow processing of shipments.

Investigating: Load list and Pre-defined reports not working as indended. Error message is seen when trying to use them. The Routing issues is fixed, and should work as intended.

Monitoring: A lunch-release was sent, fixing the issue with multiple CSs not getting consolidated. Now, the work is to find the TSes, and update them, cancelling all but one and reroute the CSes to hit the same TS. We will update you with the instructions for this.

Investigating: We are continuing to investigate this issue.

Investigating: A patch has been deployed in our PROD-environment.

Investigating: We will deploy a patch at 12:25, which will log active users out of TMS. There will be a downtime of approximately 10-15 minutes. Sorry for any inconvenience.

Investigating: Right now, we are having issues with routing, and the system might behave unexpectedly. We will deploy a patch around 12:00, which might log out any users who are logged in during this period.

Resolved: The main issue has been resolved, and the status-flow is up and functional.

Identified: We have not yet found a fix, but found a way to handle all statuses manually until then.

Identified: All statuses in queue has been processed manually, but we are still working with the root cause.

Identified: We have been unable to process any statuses since the release on the 17th of November. The root cause has been found, and we are working on a fix at the moment.