Ooma incident

Degraded Services

Minor Resolved View vendor source →

Ooma experienced a minor incident on April 8, 2020 affecting Vancouver POP, lasting 5d. The incident has been resolved; the full update timeline is below.

Started
Apr 08, 2020, 04:57 PM UTC
Resolved
Apr 13, 2020, 05:47 PM UTC
Duration
5d
Detected by Pingoru
Apr 08, 2020, 04:57 PM UTC

Affected components

Vancouver POP

Update timeline

  1. investigating Apr 08, 2020, 04:57 PM UTC

    We are currently investigating an issue with some calls not connecting in our Vancouver POP. Updates to follow.

  2. identified Apr 08, 2020, 05:07 PM UTC

    We have identified an issue with a specific server in the Vancouver POP that is not responding properly. We have performed some emergency maintenance and removed this server from the pool. Automatic failover should mean that most users should not notice this server out of commission. A very few number of users on legacy systems may not have automatic failover in place and will continue to have issues. Please email [email protected] if you are unable to make or receive calls at this time.

  3. resolved Apr 13, 2020, 05:47 PM UTC

    Maintenance was performed on a Media and SBC server in the Vancouver POP on April 10th. We have been monitoring over the last few days and believe issues with registration and call quality are resolved. If you continue to experience any issues, please submit a ticket to [email protected]