Ooma incident

Phones - No Service

Notice Resolved View vendor source →

Ooma experienced a notice incident on February 8, 2019 affecting Vancouver POP and San Jose POP and 1 more component, lasting 11h 31m. The incident has been resolved; the full update timeline is below.

Started
Feb 08, 2019, 02:23 PM UTC
Resolved
Feb 09, 2019, 01:54 AM UTC
Duration
11h 31m
Detected by Pingoru
Feb 08, 2019, 02:23 PM UTC

Affected components

Vancouver POPSan Jose POPProvisioner

Update timeline

  1. investigating Feb 08, 2019, 02:23 PM UTC

    We are currently investigating an issue impacting some phones registered to our VAN/SJC/CHI/ LON POPs. We are working on having this issue resolved as quickly as possible and will post updates when available.

  2. investigating Feb 08, 2019, 03:03 PM UTC

    We are continuing to investigate this issue.

  3. identified Feb 08, 2019, 03:06 PM UTC

    We believe we've identified the issue and have a resolution in place. We are currently monitoring the issue. If you're phones are at a login screen, please try logging in with your credentials.

  4. monitoring Feb 08, 2019, 03:33 PM UTC

    We are continuing to monitor the issue after putting a fix in place.

  5. resolved Feb 09, 2019, 01:54 AM UTC

    This incident has been resolved.