Major WMS service disruption
Affected: WMS ApplicationAPI
Ongoing Warehouse Outage History
Ongoing Warehouse is up right nowOngoing Warehouse had 14 outages in the last 2 years totaling 182h 57m of downtime — averaging 0.6 incidents per month.
There were 14 Ongoing Warehouse outages since June 27, 2025 totaling 182h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.
Issues with sending emails to Microsoft addresses
Affected: WMS Application
Timeline · 3 updates
- investigating Apr 28, 2026, 07:16 AM UTC
We are currently experiencing issues with sending emails to Microsoft addresses such as hotmail/msn/live addresses. We are investigating the issue.
- investigating Apr 28, 2026, 01:25 PM UTC
We are in communication with Microsoft about the issues
- resolved May 04, 2026, 08:46 AM UTC
This incident has been resolved.
Server issues
Affected: WMS Application
Timeline · 4 updates
- monitoring Apr 21, 2026, 02:02 AM UTC
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
- monitoring Apr 21, 2026, 02:20 AM UTC
There are still some reports of FTP issues.
- monitoring Apr 21, 2026, 07:22 AM UTC
Functionality was fully restored at approx 08:15
- resolved Apr 21, 2026, 08:33 AM UTC
This incident has been resolved.
Legacy FTP access
Timeline · 1 update
- resolved Mar 17, 2026, 09:05 AM UTC
Legacy FTP access was unavailable between 16th 4:15 PM and 17th 9:00 AM CET due to a configuration error.
Supplier outage
Timeline · 1 update
- resolved Mar 16, 2026, 07:06 AM UTC
A temporary outage at one of our partners led to disturbances between 02:48 and 02:52
System outage
Affected: WMS ApplicationAPI
Timeline · 5 updates
- investigating Feb 24, 2026, 02:44 AM UTC
We are getting reports of system outage, and are currently investigating this.
- monitoring Feb 24, 2026, 03:10 AM UTC
A fix is being implemented and we are monitoring results
- identified Feb 24, 2026, 03:59 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Feb 24, 2026, 04:48 AM UTC
We have restarted all applications and are now monitoring the results.
- resolved Feb 24, 2026, 06:35 AM UTC
This incident has been resolved.
Demo systems unreachable
Timeline · 3 updates
- investigating Feb 18, 2026, 02:30 PM UTC
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.
- monitoring Feb 18, 2026, 03:01 PM UTC
The issue have been identified and a fix as been implemented. We are now monitoring the results of the fix.
- resolved Feb 18, 2026, 05:15 PM UTC
This incident has been resolved.
Demo systems and public websites
Affected: Main websiteDocumentation centerDeveloper documentation
Timeline · 2 updates
- investigating Dec 16, 2025, 07:10 PM UTC
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.
- resolved Dec 16, 2025, 07:43 PM UTC
Maintenance is now complete.
API service disruption
Affected: API
Timeline · 4 updates
- identified Nov 27, 2025, 09:08 AM UTC
We have identified that the API service is down for example affecting automation equipment.
- identified Nov 27, 2025, 09:09 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Nov 27, 2025, 09:13 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Nov 27, 2025, 09:44 AM UTC
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.
Service Disruption
Affected: WMS ApplicationAPI
Timeline · 3 updates
- investigating Nov 25, 2025, 09:23 PM UTC
We are getting reports of service disruptions. We are currently investigating.
- monitoring Nov 25, 2025, 09:44 PM UTC
We have identified an issue with the API server and have implemented a fix. We are now monitoring the situation.
- resolved Nov 25, 2025, 10:19 PM UTC
We can confirm that the fix has resolved the issue.
Ongoing WMS Scheduled maintenance at one of multiple server sites
Affected: WMS Application
Timeline · 2 updates
- investigating Nov 03, 2025, 11:34 PM UTC
Ongoing WMS cannot be accessed at the moment. This incident was created by an automated monitoring service.
- resolved Nov 04, 2025, 06:51 AM UTC
This automated alarm was due to a scheduled maintenance at one of our sites. WMS Functionality was never affected.
Service disturbances
Affected: WMS ApplicationAPIMain websiteDocumentation centerDeveloper documentation
Timeline · 4 updates
- investigating Oct 28, 2025, 06:20 PM UTC
We are getting reports about disturbances and are currently investigating.
- investigating Oct 28, 2025, 06:56 PM UTC
An issue has been identified with one of our server locations. We are switching to another location.
- monitoring Oct 28, 2025, 07:35 PM UTC
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.
- resolved Oct 29, 2025, 08:58 AM UTC
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.
Service disruption
Affected: WMS Application
Timeline · 1 update
- resolved Sep 18, 2025, 12:07 PM UTC
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.
Issues with sending email to Outlook addresses
Timeline · 1 update
- resolved Aug 21, 2025, 01:51 PM UTC
During August 20th there were issues with sending email to Outlook addresses (such as outlook.com, hotmail.com, msn.com, live.com etc.).