Ooma incident
Loss of Registrations/Intermittent Call Connectivity
Ooma experienced a minor incident on March 9, 2020 affecting Vancouver POP, lasting 2d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Mar 09, 2020, 05:27 PM UTC
We are currently experiencing issues with our Vancouver POP. It is expected that devices will failover to the closest regional POP. We are continuing to investigate and will post updates as they become available.
- investigating Mar 09, 2020, 05:37 PM UTC
While our team is currently investigating, it is also expected that bidirectional calls are intermittently connecting.
- monitoring Mar 09, 2020, 05:45 PM UTC
Our team has identified the issue and our Vancouver POP has now stabilized. We are continuing to monitor closely. All connectivity should have returned to normal. If you are experiencing any issues, please reach out to our support team at [email protected] or [email protected].
- investigating Mar 09, 2020, 08:05 PM UTC
We are currently experiencing an issue with intermittent call connectivity. Our team is currently investigating and will provide updates as soon as possible.
- monitoring Mar 09, 2020, 08:26 PM UTC
We have identified the issue and call connectivity has returned to normal. We are continuing to monitor. Tonight, we will be doing some emergency network maintenance to adjust some of the routing preferences on our core network. In this maintenance, we will be taking at least one upstream carrier out of our routing path as this is what ultimately lead to our network instability today.
- investigating Mar 10, 2020, 05:29 PM UTC
We are currently experiencing an issue with intermittent call connectivity. Our team is currently investigating and will provide updates as soon as possible.
- investigating Mar 10, 2020, 05:37 PM UTC
We are continuing to investigate this issue.
- monitoring Mar 10, 2020, 05:38 PM UTC
We identified a momentary issue with one of our upstream telecom carriers not connecting calls immediately. We believe the issue was resolved within minutes and everything should be working as normal, but the team will to monitor for the rest of the day.
- resolved Mar 11, 2020, 06:26 PM UTC
This incident has been resolved.