FoodLogiQ had 3 outages in the last 2 years totaling 23h 48m of downtime — averaging 0.1 incidents per month.
There were 3 FoodLogiQ outages since October 20, 2025 totaling 23h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.
We have identified an issue that may cause failed requests or timeouts when using FoodLogiQ AI document or spec processing functions. We are working to resolve this issue and appreciate your patience while the fix is implemented.
This incident has been resolved.
FoodLogiQ is currently experiencing an issue impacting automated email notifications as of 4:00 AM EST. Customers may experience delays or missed notifications for Documents, Incidents, and new user invites. Withdrawals in FoodLogiQ Recall are not affected. Our team is actively working to resolve the issue and restore normal service. We will continue to share updates on this page as progress is made.
We are continuing to investigate this issue.
We’ve pinpointed the issue and are actively implementing a solution to resolve it as quickly as possible
We are continuing to work on the fix for this issue
A fix has been implemented we are monitoring the results
This incident has been resolved. We will continue to monitor the progress.
AWS is experiencing an outage in the US-EAST-1 Region which is being handled as a P1 incident. You will see a delay in email notification and todo processing. We are continuing to monitor the AWS status on the EAST-1 and will update this page as we see progress.
The AWS US-EAST-1 outage has not yet been fully resolved. AWS continues to provide regular status updates, and we are tracking them closely. We will share additional updates here as progress is made.
We are continuing to monitor the AWS status on the EAST-1 and will update this page as we see progress.
Following the latest AWS update, many services have been restored, and our backlog items are progressively getting resolved. Our team continues to closely monitor the situation for any additional issues.
This incident has been resolved.