Bondsmith incident

This is an example incident

Notice Resolved View vendor source →

Bondsmith experienced a notice incident on October 23, 2025, lasting –. The incident has been resolved; the full update timeline is below.

Started
Oct 23, 2025, 03:39 PM UTC
Resolved
Oct 23, 2025, 03:39 PM UTC
Duration
–
Detected by Pingoru
Oct 23, 2025, 03:39 PM UTC

Update timeline

  1. investigating Oct 24, 2025, 03:23 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 Oct 24, 2025, 03:23 PM UTC

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

  3. monitoring Oct 24, 2025, 03:23 PM UTC

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

  4. resolved Oct 24, 2025, 03:23 PM UTC

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