FoodLogiQ experienced a major incident on November 20, 2017, lasting 11m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Nov 20, 2017, 06:06 PM UTC
We're currently investigating a degradation of service primarily on the Connect Servers which may be indirectly affecting our API v2 Services. We'll continue to keep everyone posted on progress.
- monitoring Nov 20, 2017, 06:08 PM UTC
Services are now operating as expected. We will continue to monitor performance and will update everyone on complete resolution.
- resolved Nov 20, 2017, 06:18 PM UTC
On Nov 20th, 2017, FoodLogiQ Connect experienced a degradation of service. The outage lasted approximately from 1:01 PM until approximately 1:04 EST. Though the issue has been fully resolved, we value transparency and open communication with our customers. If you have any questions, please visit our Contact Us page.
- postmortem Jul 30, 2018, 08:42 PM UTC
During a routine deployment process, our automatic build operation failed to set an environment variable which caused an error. Due to this, our underpinning Infrastructure API was not able to successfully boot application servers during their cycle process, which in turn introduced a short interruption of service (for approximately 4 minutes). We were able to quickly identify the issue and restore service immediately. In addition, we have now introduced tests to verify all configuration settings are set correctly as well as introduced a new check in our server cycle process where no more than 1 server will be booting at any one time to ensure continued and uninterrupted service. Though the issue has been fully resolved, we value transparency and open communication with our customers. If you have any questions, please visit our Contact Us page.