Ongoing Warehouse Outage History

This incident has been resolved.

The connectivity problems were traced to a transient error within our internal network infrastructure. The issue was temporary and resolved automatically, without any human intervention. Thanks to redundancy in our networking equipment only a subset of our clients were affected and many requests continued to be served normally throughout the incident. We are reviewing this event to better understand its cause and to identify improvements that will further strengthen the resilience of our infrastructure. We apologize for the disruption and appreciate your understanding.

This incident has been resolved.

This incident has been resolved.

Legacy FTP access was unavailable between 16th 4:15 PM and 17th 9:00 AM CET due to a configuration error.

A temporary outage at one of our partners led to disturbances between 02:48 and 02:52

This incident has been resolved.

Maintenance is now complete.

A configuration change in the hosting environment at 09:58 CET caused the API server to respond to requests with HTTP 500 Internal Error. We identified the issue at 10:02 and successfully re-routed traffic at 10:09 to fallback environments. Clients with persistent TCP sessions against the failing environment may continue to receive HTTP 500 errors. This is likely to self-heal, but to resolve it definitively, force your client to perform a new DNS lookup to api.ongoingsystems.se or initiate a new TCP session with the cached IP.

We can confirm that the fix has resolved the issue.

This automated alarm was due to a scheduled maintenance at one of our sites. WMS Functionality was never affected.

Full availability of the systems has now been restored. Between 19:03 and 19:20 CET on 28 Oct a network component failure at the primary hosting site caused all inbound and outbound traffic to drop. WMS application access stabilized shortly thereafter. As a safety measure, engineers initiated failover and completed diversion of web traffic to the secondary site at 19:50 CET. Following the failover, a latent error on one server in the secondary site affected some printer services responsible for generating automatic reports. This condition persisted overnight until a partial recovery at 03:10 CET and a definitive fix at 07:40 CET after modifying the network configuration. We are working with the hosting provider on the primary site to address the network failure and reduce recurrence. We apologize for the disruption and appreciate your understanding.