Ineoys incident

This is an example incident

Notice Resolved View vendor source →

Ineoys experienced a notice incident on March 5, 2022, lasting —. The incident has been resolved; the full update timeline is below.

Started
Mar 05, 2022, 02:54 PM UTC
Resolved
Mar 04, 2022, 03:10 PM UTC
Duration
Detected by Pingoru
Mar 05, 2022, 02:54 PM UTC

Update timeline

  1. investigating Mar 05, 2022, 02:54 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 Mar 05, 2022, 02:54 PM UTC

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

  3. monitoring Mar 05, 2022, 02:54 PM UTC

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

  4. resolved Mar 05, 2022, 02:54 PM UTC

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