Resolved incident

Delay in SLO and errors in Trigger notifications

Honeycomb · None · Started

Duration
34m
Severity
None
Status
Resolved

Summary

None · Resolved

This incident has been resolved.

View official incident ↗

Event timeline

How this incident unfolded, from the official status page.

  1. Monitoring

    Honeycomb

    An error in our production AWS configuration caused a brief interruption that affected Service Maps and caused an delay in delivering SLO notifications, and errors delivering Trigger notifications between 9:54AM UTC-5 and 10:05AM UTC-5. If any longer Triggers (1 day) would have activated within this window, they may not have sent a notification.

  2. Resolved

    Honeycomb

    This incident has been resolved.