Resolved
Resolved

Amazon Web Services is reporting that the underlying issue that caused today's widespread outages has been mitigated. While they are continuing to work toward full recovery for all impacted services, we are considering this case resolved as app access and performance remains stable across all Gingr applications. Thank you for your patience.

Updated

App access and performance continues to be stable across all Gingr applications. We will await further updates from Amazon Web Services before marking this issue as fully resolved. Thank you for your patience.

Recovering

At this time database connectivity appears to be restored for all Gingr customers. As this is related to an AWS outage, we will continue to monitor for any further developments.

Identified

While AWS continues to address the widespread outages, we are beginning to see improvement with system access and performance for some Gingr customers. We are continuing to actively monitor the situation and will provide additional updates as more information becomes available.

Updated

It has been identified that the current performance issues are due to a widespread Amazon Web Services (AWS) outage, and not the Gingr application itself. Updates are available on the AWS status page here: https://status.aws.amazon.com. We are working with the AWS team to resolve the issue as quickly as possible.

Updated

The app database errors and latency have been determined to be isolated to customers within one specific database cluster. We are actively working with our database hosting service to identify and resolve the issue. We will provide an additional update as soon as possible.

Investigating

At approximately 9:05am MST we began receiving reports of app outages and system latency. We are currently investigating the issue and working to address it as quickly as possible. We will provide an additional update within the next 15 minutes.

Began at:

Affected components
  • Web Application