Omnilert incident

SNPP Trigger issue

Major Resolved View vendor source →

Omnilert experienced a major incident on March 4, 2019 affecting SNPP, lasting 1h 57m. The incident has been resolved; the full update timeline is below.

Started
Mar 04, 2019, 04:40 PM UTC
Resolved
Mar 04, 2019, 06:38 PM UTC
Duration
1h 57m
Detected by Pingoru
Mar 04, 2019, 04:40 PM UTC

Affected components

SNPP

Update timeline

  1. investigating Mar 04, 2019, 04:40 PM UTC

    We are currently investigating an issue with connections to snpp.omnilert.net for SNPP Triggered messaging. This incident impacts SNPP Triggers only. (The standard Omnilert web portals and other mechanisms are all operational.) Impact on Service: Some connections to SNPP servers (paging) may be unavailable.

  2. monitoring Mar 04, 2019, 05:02 PM UTC

    Omnilert engineers have implemented a fix. We've tested and confirmed SNPP connections are working properly and SNPP Triggers are now responding/functioning properly. We will continue to monitor, but no further issue is expected.

  3. resolved Mar 04, 2019, 06:38 PM UTC

    This incident has been resolved.