Tenfold incident

Chrome extension authentication

Minor Resolved View vendor source →

Tenfold experienced a minor incident on October 31, 2019 affecting Chrome Extension, lasting 18h 58m. The incident has been resolved; the full update timeline is below.

Started
Oct 31, 2019, 06:30 PM UTC
Resolved
Nov 01, 2019, 01:28 PM UTC
Duration
18h 58m
Detected by Pingoru
Oct 31, 2019, 06:30 PM UTC

Affected components

Chrome Extension

Update timeline

  1. investigating Oct 31, 2019, 05:18 PM UTC

    [Sev 3] Tenfold is experiencing an issue with the Chrome Extension and CTD Chrome Extension. Some customers may not be able to log back in if they log out. Tenfold engineering is aware of the issue and will be resolving ASAP. Customers using the Tenfold Chrome Extension are urged to not log out if possible.

  2. identified Oct 31, 2019, 05:36 PM UTC

    [Sev 3] Tenfold engineers have identified the cause and are working on deploying a fix. The next scheduled update will come at 18:30 UTC however any new information will be shared as soon as it is available.

  3. identified Oct 31, 2019, 06:30 PM UTC

    [Sev 3] Tenfold engineers are testing the fix before scheduling deployment. Once the fix has been approved, we will update here with that information. The next scheduled update will be at 20:00 UTC if the fix has not been rolled out by that time.

  4. identified Oct 31, 2019, 08:01 PM UTC

    [Sev 3] Tenfold engineers continue to test the fix prior scheduling deployment. Once the fix has been approved, we will update here with that information. The next scheduled update will be at 22:30 UTC if the fix has not been rolled out by that time.

  5. identified Oct 31, 2019, 09:30 PM UTC

    [Sev 3] Tenfold engineers will be deploying a solution momentarily. The next scheduled update will remain at 22:30 UTC.

  6. monitoring Oct 31, 2019, 10:44 PM UTC

    [Sev 3] Tenfold engineers have successfully deployed a fix to this issue. Engineers will continue to closely monitor the situation overnight for any anomalies. The next scheduled update will be on 11/1/2019 at 14:00 UTC however we will update this status page with any new findings as they become available.

  7. resolved Nov 01, 2019, 01:28 PM UTC

    [Sev 3] This issue has been resolved.