Singular incident

This is an example incident

Notice Resolved View vendor source →

Singular experienced a notice incident on August 5, 2019, lasting —. The incident has been resolved; the full update timeline is below.

Started
Aug 05, 2019, 01:00 PM UTC
Resolved
Aug 04, 2019, 01:16 PM UTC
Duration
Detected by Pingoru
Aug 05, 2019, 01:00 PM UTC

Update timeline

  1. investigating Aug 05, 2019, 01:00 PM UTC

    When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.

  2. identified Aug 05, 2019, 01:00 PM UTC

    As you continue to work through the incident, update your customers frequently.

  3. monitoring Aug 05, 2019, 01:00 PM UTC

    Let your users know once a fix is in place, and keep communication clear and precise.

  4. resolved Aug 05, 2019, 01:00 PM UTC

    Empathize with those affected and let them know everything is operating as normal.