Meadow incident

Provider Downtime

Critical Resolved View vendor source →

Meadow experienced a critical incident on February 28, 2017, lasting 5h 12m. The incident has been resolved; the full update timeline is below.

Started
Feb 28, 2017, 05:58 PM UTC
Resolved
Feb 28, 2017, 11:10 PM UTC
Duration
5h 12m
Detected by Pingoru
Feb 28, 2017, 05:58 PM UTC

Update timeline

  1. investigating Feb 28, 2017, 05:58 PM UTC

    We are currently investigating an issue with one of our service providers.

  2. identified Feb 28, 2017, 06:10 PM UTC

    Amazon Web Services (https://status.aws.amazon.com/) is currently experiencing downtime. We do not have an ETA from Amazon at this time, but we will update as soon as we have more information.

  3. monitoring Feb 28, 2017, 07:08 PM UTC

    Amazon is currently working to mitigate the downtime. We want to re-iterate that all of your data is completely safe, secure, and encrypted. There will be no data loss whatsoever once everything is back up. Please reach out to [email protected] with any questions you may have.

  4. monitoring Feb 28, 2017, 09:11 PM UTC

    Service is beginning to be restored. Embedded menus and point of sale are up and running. Admin.getmeadow.com will be online shortly. Thank you for your patience.

  5. resolved Feb 28, 2017, 11:10 PM UTC

    All service has been completely restored and verified.