Keeping incident

Ongoing connectivity issues

Major Resolved View vendor source →

Keeping experienced a major incident on July 16, 2024 affecting Chrome Extension and Keeping App, lasting 3h 9m. The incident has been resolved; the full update timeline is below.

Started
Jul 16, 2024, 03:39 PM UTC
Resolved
Jul 16, 2024, 06:49 PM UTC
Duration
3h 9m
Detected by Pingoru
Jul 16, 2024, 03:39 PM UTC

Affected components

Chrome ExtensionKeeping App

Update timeline

  1. monitoring Jul 16, 2024, 03:39 PM UTC

    The Keeping Chrome Extension and web application are experiencing connectivity issues due to an outage with our primary hosting provider. We've remediated the issue and are monitoring.

  2. resolved Jul 16, 2024, 06:49 PM UTC

    This incident has been resolved.

  3. postmortem Jul 16, 2024, 07:17 PM UTC

    ### Postmortem: Service Outage on July 16, 2024 **Incident Summary:** On 9:05 am EDT July 16, 2024, Keeping experienced intermittent connection issues that lasted approximately 2 hours. The outage affected both the Keeping Chrome Extension and the main application website at https://app.keeping.com/ **Timeline:** * **9:05 am EDT:** Initial reports of the website being inaccessible were received. * **9:07 am EDT** : Incident response team was alerted and began investigation. * **9:25 am EDT** : Root cause identified as a Denial of Service attack on Keeping’s hosting provider, Gigalixir. * **9:30 am EDT**: Mitigation steps initiated. * **10:25 am EDT**: Website functionality partially restored. * **11:00 am EDT**: Full service restored and confirmed stable. **Root Cause:** The outage was caused by [a SYN flood attack on Gigalixir’s load balancers](https://gigalixir.com/blog/gcp-us-central-service-outage/). Gigalixir is Keeping’s primary web hosting provider. **Impact:** During the outage, access to Keeping’s main web application was severely limited \(or impossible\), and syncing between agent accounts and shared mailboxes was paused. No data was lost.