Ongoing Warehouse had 21 outages in the last 2 years totaling 366h 34m of downtime — averaging 0.9 incidents per month.
There were 21 Ongoing Warehouse outages since November 13, 2024 totaling 366h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently experiencing issues with sending emails to Microsoft addresses such as hotmail/msn/live addresses. We are investigating the issue.
We are in communication with Microsoft about the issues
This incident has been resolved.
We have identified issues with a server. It has been taken out of use, but for approx 30 minutes 03:15-03:45 UTC Scheduled Jobs may not have been triggered and FTP may have been down
There are still some reports of FTP issues.
Functionality was fully restored at approx 08:15
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
We are getting reports of system outage, and are currently investigating this.
A fix is being implemented and we are monitoring results
The issue has been identified and a fix is being implemented.
We have restarted all applications and are now monitoring the results.
This incident has been resolved.
Demo/test WMS are currently experiencing issues and may currently unreachable at times. Note that this does not affect production WMS applications. We are currently investigating the issue.
The issue have been identified and a fix as been implemented. We are now monitoring the results of the fix.
This incident has been resolved.
Demo/test WMS systems and public websites will be undergoing maintenance which may cause the websites to be unreachable at times. Public websites refer to these URLs: ongoingwarehouse.se docs.ongoingwarehouse.com developer.ongoingwarehouse.com Note that this does not affect production WMS applications.
Maintenance is now complete.
We have identified that the API service is down for example affecting automation equipment.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
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 are getting reports of service disruptions. We are currently investigating.
We have identified an issue with the API server and have implemented a fix. We are now monitoring the situation.
We can confirm that the fix has resolved the issue.
Ongoing WMS cannot be accessed at the moment. This incident was created by an automated monitoring service.
This automated alarm was due to a scheduled maintenance at one of our sites. WMS Functionality was never affected.
We are getting reports about disturbances and are currently investigating.
An issue has been identified with one of our server locations. We are switching to another location.
The issue with the primary server location was resolved within roughly 20 minutes. Nonetheless, to ensure availability, all traffic has now successfully been redirected to the secondary server location. We are actively monitoring the status of the WMS applications.
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.
Between 10:45 and 10:55 CET today, some users experienced issues accessing Ongoing WMS. This disruption occurred during a scheduled maintenance window when certain web traffic was accidentally routed to a server that had not fully initialized the application. Immediate action was taken to manually redirect traffic, and the environment has now been fully restored. Please note that API calls (such as those from automation equipment) and scheduled integration jobs were not affected during this period. We apologize for any inconvenience this may have caused and appreciate your understanding.
During August 20th there were issues with sending email to Outlook addresses (such as outlook.com, hotmail.com, msn.com, live.com etc.).
We have been getting reports of performance issues from some of our customers. We are currently investigating.
We are continuing to investigate the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Between 02:40 and 06:23 it was not possible to reach several systems. API communication and scheduling was not affected.
We have been getting reports of performance issues. We are currently investigating.
We have identified high load on one of our servers, and have taken action to distribute the functionality over more servers.
This incident has been resolved.
We are currently facing performance issues affecting some systems and are investigating it.
The performance degradation was temporary and we see improved performance again. We are monitoring the issue and are performing a root cause analysis.
We have identified the root cause of the issue and are working on a fix.
Some scheduled WMS integrations were unable to run between 10:00AM-11:00AM Swedish time (CEST) due to a temporary network issue. The issue has been resolved and no action needs to be take because the next scheduled run of the integrations after failure takes the disruption into account.
We are experiencing degraded performance for several customers at the moment, affecting printing and GUI response times. We have implemented fixes and are monitoring the results.
We see improvements from earlier performance issues and are continously monitoring the impact.
This incident has been resolved and we have made necessary changes in our infrastructure which should mitigate similar performance issues in the future.
We are currently experiencing performance issues, Ongoing WMS can be slow to respond and there are issues generating reports for printing. We are investigating the issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
After continued monitoring this incident is resolved and a long-term fix has been implemented.
The main website (ongoingwarehouse.com) was unreachable for a while this morning. The issue has now been resolved.