Apertur incident

This is an example incident

Resolved after 10 minutes, on April 5, 2026.

investigating Apr 05, 2026, 12:47 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.

Started
Apr 05, 2026, 12:11 PM UTC
Resolved
Apr 05, 2026, 12:21 PM UTC
Duration
10m
Detected by Pingoru
Apr 05, 2026, 12:11 PM UTC

Update timeline

  1. monitoring Apr 05, 2026, 12:11 PM UTC

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

  2. identified Apr 05, 2026, 12:17 PM UTC

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

  3. resolved Apr 05, 2026, 12:21 PM UTC

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

  4. investigating Apr 05, 2026, 12:47 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.

Your product runs on more than Apertur

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →