Is Ooma Enterprise Down Right Now? Check if there is a current outage ongoing.

Ooma Enterprise will be performing gradual systems updates in our Global Point of Presences (POP) During this time, intermittent connection issues may be experienced. Down time is not expected to exceed 5 minutes.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

This incident has been resolved.

We are continuing to investigate this issue.

We have identified a service impacting issue, and some calling features may be affected. Our engineers are actively working on resolving this, and an update will be posted shortly to provide additional information.

Our San Jose POP experienced a brief outage from 12:55pm - 1:05pm PST due to SIP flooding.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

Our carrier is currently experiencing a second DDoS attack. Until we reach a resolution, you may be experiencing failed calls, latency/time outs, and/or delayed or failed messages.

Operational but continuing to work on a fix for this issue.

Our carrier is currently experiencing a second DDoS attack. Until we reach a resolution, you may be experiencing failed calls, latency/time outs, and/or delayed or failed messages.

Services are operational, and our team is continuing to monitor the situation closely.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

There was an incident in the Vancouver POP. This disruption was short in nature, and did cause phones to lose registration, and thus re-register to the San Jose POP.

Today we experienced a brief interruption. The great news is that some of the mitigation steps put in place last night reduced the interruption time from an hour to 8 minutes today.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

Users connected to our Vancouver data center experienced an issue where devices lost registration, and some users may have dropped calls in progress. Those customers may have also not received any calls during the brief duration the server was unavailable while services rerouted to the in place, on line redundant servers. Most users were able to re-register within 5 minutes.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

The Monitoring phase is complete and the issue is confirmed to be resolved. Should you still be experiencing issues, please submit a ticket to enterprisesupport@ooma.com and we will resolve your issues as soon as possible.

The issue was identified and a fix has been implemented. All devices on the network should register back to the SJC POP and begin to function as expected. Should you still be experiencing issues, please submit a ticket to enterprisesupport@ooma.com and we will resolve your issues as soon as possible.

We are currently investigating an outage to the SJC POP. All client devices should failover to the VAN POP and be able to make and take calls shortly.

All testing for the San Jose POP has been completed and everything is functioning correctly. Please reach out to enterprisesupport@ooma.com with the subject "Urgent" if you encounter any issues.

The maintenance has been completed and we have begun testing and confirming everything is operating effectively. Calls and registrations will now be routed back through the San Jose POP. Please reach out to enterprisesupport@ooma.com with the subject "Urgent" if you encounter any issues during this time.

Maintenance has begun on the San Jose POP. Connectivity is expected to be interrupted, however phones, devices, and calling services are expected to fail over to our Vancouver POP automatically. Please reach out to enterprisesupport@ooma.com with the subject "Urgent" if you encounter any issues during this time.

Please note: Planned maintenance is being performed on our network in San Jose, Saturday March 27 (27/03/2021) at 9:30am-12:00pm PT and may last up to 2.5 hours. Connectivity is expected to be interrupted, however phones, devices, and calling services are expected to fail over to our Vancouver POP automatically. Please reach out to enterprisesupport@ooma.com with the subject "Urgent" if you encounter any issues during this time.

Dear Ooma Customer, The Federal Communications Commission (FCC) has adopted 988 as a new three-digit number to be used nationwide to reach the National Suicide Prevention and Mental Health Crisis Lifeline, starting July 16, 2022. Customers must continue to dial 1-800-273-TALK to reach the Lifeline until July 16, 2022. For 988 to work in your area code, 10-digit local dialing will be implemented. You will need to change the way you dial local calls. What will be the new dialing procedure? To complete all local calls, you will now need to dial area code + telephone number. This applies to all calls within your area code that are currently dialed with seven digits. Who will be affected? Anyone with a telephone number from your area code will need to make a change from 7-digit local dialing to 10-digit local dialing. When will the change begin? Beginning immediately, you should begin dialing 10 digits (area code + telephone number) for all local calls. If you forget and dial just 7 digits, your call will still be completed. Beginning October 24, 2021, you must dial 10 digits (area code + telephone number) for all local calls. On and after this date, local calls dialed with only 7 digits may not be completed, and a recording will inform you that your call cannot be completed as dialed. You must hang up and dial again using the area code and the 7-digit number. Beginning July 16, 2022, dialing "988" will route your call to the National SuicidePrevention and Mental Health Crisis Lifeline. What will you need to do? In addition to changing the way you dial local calls, all services, automatic dialing equipment, or other types of equipment that are programmed to complete calls to 7-digit local numbers will need to be reprogrammed to complete calls to 10-digit numbers. Some examples are life safety systems or medical monitoring devices, PBXs, fax machines, Internet dial-up numbers, fire or burglar alarm and security systems or gates, speed dialers, mobile or other wireless phone contact lists, call forwarding settings, voicemail services, and other similar functions. Be sure to check your website, personal and business stationery, advertising materials, personal and business checks, contact information, your personal or pet ID tags, and other such items to ensure the area code is included. What will remain the same? - Your telephone number, including the current area code, will not change. - The price of a call, coverage area, or other rates and services will not change due to the dialing change. - What is a local call now will remain a local call regardless of the number of digits dialed. - You will continue to dial 1+ area code + telephone number for all long distance calls. - You can still dial just three digits to reach 711 (relay services) and 911 (emergency services). - Any 211, 311, 411, 511, 611, or 811 services available in your community can still be reached by dialing their three-digit codes. - The National Suicide Prevention Lifeline can still be reached by dialing 1-800-273-TALK(8255).

This work has been completed. There was disruption on San Jose between 8:48am PST and 9:02am PST. Most endpoints failed over correctly, and returned to San Jose when the work was complete. If you noticed that your service was unavailable during that entire period, or is still not available, please submit a support ticket so that we can investigate with you why your phones did not behave as expected.

Please note: Scheduled maintenance is being performed on our network in San Jose, tomorrow 20/03/2021 at 9am PT and may last up to 30 minutes. Connectivity is expected to be interrupted, however phones, devices, and calling services are expected to fail over to our Vancouver POP automatically. Please reach out to enterprisesupport@ooma.com if you encounter any issues during this time.

This incident has been resolved. For a detailed report on the outage, please submit a ticket and we will respond accordingly.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently investigating an outage with the Vancouver POP.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating an issue with our Vancouver server cluster.

This incident has been resolved.

AT&T has just update us that they are continuing to investigate the cause of this major outage, and are working to find a way to restore service. This is impacting our business customers as well as some home users. Some of our users have even reported that their AT&T wireless service has also been interrupted, although that falls outside of what Ooma provides. AT&T has no estimated time of restoration yet. Thank you for your patience.

We are currently experiencing an issue with dedicated voice circuits provided by AT&T. They are experiencing a major outage impacting all AT&T services. We are continuing to monitor and wait for updates from AT&T.

This incident has been resolved.

A fix has been implemented and we are closely monitoring the situation.

We are currently investigating an issue where around 75% of inbound calls are not being connected. Initial investigation has revealed that the issue is with our carrier and we have escalated this issue with them.

Our Engineering team has investigated and resolved this issue. You will now be able to access all your extensions with no issues.

We are currently investigating an error when you click any extension in the Management portal; you will receive a 404 status error. You will be unable to make any updates to extensions at this time. Updates will be posted as they become available.

We are marking this outage as resolved. We have had no further reports in the last day, and our monitoring platform hasn't shown any further connection issues in the region. However please submit a ticket to enterprisesupport@ooma.com if you continue to experience call quality issues.

Cogentco has removed their advisory from their status page, and our monitoring has not shown any further data loss on our monitoring routes. We will continue to monitor the situation, however please submit a ticket to enterprisesupport@ooma.com if you continue to experience call quality issues.

We've identified identified data loss across cogentco networks in Western Canada. Their advisory states that this is due to a backhaul fiber cut which they're working to resolve, but currently do not have an ETA on.

We are currently investigating several reports of call quality issues with our Vancouver POP. Updates to follow.

This incident has been resolved.

We have rerouted calls through alternative carriers as the carrier in question works on their routes. Calls should be completing as intended and audio should be back to normal moving forward.

We are currently investigating an issue with an upstream carrier. You may experience issues with inbound and outbound call connectivity or audio availability until this has been resolved or we find a work around.

We have completed the investigation of the service interruption in our San Jose POP this morning, Aug. 10/2018 From 10:07 AM - 10:40 AM PDT, and again from 11:17 AM - 11:29 AM PDT, one of our primary paths into our San Jose facility was impacted by severe network congestion. This had a negative impact on our systems attempting to deliver internal requests, and as a result caused some inbound calls and extension to extension calls to fail. We have implemented measures to work around the affected paths in San Jose. We have also made appropriate changes to our systems to reduce impact in the event that congestion occurs again. We apologize for the impact this morning. We know that voice services are a critical part of your business and Voxter is proud to be your provider.

We have seen no further issues in our San Jose POP. All routes are no normal, and our mitigation measures have worked effectively.

We have put in place some additional measures to mitigate the impact caused by this issue. We are continuing to monitor.

We are continuing to monitor for any further issues.

We are no longer seeing any issues impacting customers in our San Jose POP. We are continuing to monitor.

We are continuing to monitor for any further issues.

We have implemented a work around the impacted routes. Functionality has been restored for our customers connecting to our San Jose POP. We are continuing to monitor the issue.

We have identified a routing congestion that might be impacting the ability to complete calls. We have our network team working to resolve the issue as quickly as possible.

We are investigating an issue in our San Jose POP that is causing inbound calling for some customers to fail intermittently. We will post updates to this page as we know more.

We have completed our investigation of service interruption in our San Jose, Chicago, and Vancouver POPs for September 07, 2018. We performed a platform upgrade the night of Thursday, September 6th. Prior to the upgrade, we had been running the upgrade in our staging environment for 3 weeks. Up to and including prior to the cutover, all tests we performed had passed as expected. As the load increased across the network post upgrade, we identified that some requests were taking longer than expected to complete, and as a result some operations would time out without a successful response. As these timeouts were largely impacting SJC and CHI sites, we moved customer traffic to run on adjacent infrastructure in our other sites, and temporarily disallowed new connections to the affected infrastructure in SJC and CHI. Additionally, we identified an upstream telecom carrier configuration issue where customer phone numbers that were routed to SJC as a primary were not failing over to the adjacent infrastructure as intended. Customers who bring their own carrier would be impacted if their failover was not properly configured. The network is designed with failover in mind, such that minimizing negative impact would require disabling a negatively impacted facility, to allow for a healthy adjacent facility to take over. The root cause of the issue has been identified as a bug related to the maximum number of concurrent requests that a given node can handle. These values are set from our provisioning process, and in this case the wrong values were deployed in error. This caused delays as load increased; and made the problem more difficult to identify as we had to isolate each affected component individually. We were able to patch the bug and reapply the appropriate settings for the number of available workers to handle requests. We apologize for the impact this may have caused. We know that voice services are a critical part of your business and Voxter is proud to be your provider.

We have not seen any further issues at this time. Stability has returned to all of the affected clusters. We will be providing a post mortem about this incident and sharing it via this page.

We have resolved the timeout issues in the affected POPs. Customer phones should now be registered to the most appropriate POP. We will continue to monitor the issue and will post updates if necessary.

SJC and CHI POPs are stabilized. We are working at gracefully bringing those sites and services back into the network.

We are continuing to resolve issues in SJC and CHI POPs. Work arounds are in place for customers that connect primarily to those sites.

We have work arounds in place for affected customers and are continuing to repair issues in SJC and CHI. We will update this page with more information as it becomes available.

We have a work around in place for impacted customers in SJC and CHI. We will continue to work on resolving timeouts. All phone connectivity should be resolved shortly for customers in SJC and CHI.

VAN customers are operating normally. We are continuing to work on resolved timeouts within our SJC and CHI infrastructure.

We have stabilized connectivity for VAN customers and are working on resolving the delays for CHI and SJC and customers. We will continue to update here as we discover more.

We are continuing to work on implementing a fix for the timeouts. During this time you may notice that your phone will periodically lose service, take longer to log in, or connect calls. We will post updates here as they become available.

We are working of a fix as quickly as possible to resolve the intermittent connectivity issues that some customers are experiencing.

We have identified some components within our infrastructure that are creating timeouts to occur. Customers may notice their phones will periodically display no service as we seek to isolate and remove these components. Inbound and outbound calling may also be impacted.

We have resolved the issue creating intermittent call delivery issues in our Vancouver facility. All services have returned to normal.

We have identified the issue and resolved it. We will most more information here as required. All services have returned to normal.

We are currently investigating an issue impacting calls being delivered consistently to customers connected to our Vancouver POP. We will update this page as we know more.

We have completed our investigation of service interruption in our San Jose and Vancouver POPs for October 31, 2018. We were monitoring an issue with one our servers in our SJC data centre. At 4:06PM Oct. 31 we removed that server from the availability pool because it was causing timeouts that were delaying requests. This was done to ensure health of the entire network. When the connections failed over to the backup facility, the congestion created delays answering requests in that facility as well. We moved traffic back to the primary in SJC and repaired the issue. The total service interruption in VAN was approximately 5 minutes. The total service impact in San SJC was 52 minutes; calls were being created and delivered with delays for 36 minutes of the impacted time. The root cause of the issue has been identified and we have adjusted configurations in SJC and VAN to allow for a more graceful failover between the two sites. We apologize for the impact this may have caused. We know that voice services are a critical part of your business and Voxter is proud to be your provider.

We believe this incident to be resolved as there have been no further delays to call delivery both inbound in outbound across our network. We will provide a post mortem to this even within the next 24 hrs.

We have implemented a fix and calls are delivering to customers connect to SJC. We are monitoring the situation and will post here with updates as needed or when we believe the issue to be resolved.

We are continuing to repair delays to call delivery in SJC POP.

We are continuing to work on a fix for this issue.

Calls are being delivered but some calls still are experiencing delays for customers in SJC. We are continuing to implement a fix.

We have identified the source of the issue in our SJC POP. We are working on implementing a fix as soon as possible.

We are continuing to work on repairing issues in SJC. Calls are experiencing delays in delivery for both inbound and outbound.

We have resolved intermittent busy and delayed calls in our VAN POP. Issues still remain for customers connected to SJC. We are implementing a fix as quickly as possible.

We are continuing to investigate reports of delayed call completion in both VAN and SJC POPs.

We are currently investigating an issue where some customers are experiencing intermittent busy signals when placing both inbound and outbound calls.

Emergency maintenance has been completed and the server migration was successful. Operations in our SJC POP have returned to normal.

Emergency Maintenance window is almost completed. We will post more information to this page as we finish the maintenance.

We are currently performing some emergency maintenance to our San Jose POP. There may be delays in call delivery as we migrate a server to better accommodate load. Failover has to our Vancouver POP has occurred and is keeping up with the load; there should not be a service impact.

All sites are operational. The Core Router in VAN has been repaired and connectivity issues for SJC and VAN have been resolved. Dedicated Voice Circuit connectivity has been restored. We will provide a post mortem via this page within 24hrs.

Services have been restored. We are monitoring stability within our network.

Services have been restored for SJC. We are completing so additional restarts of VAN core routers as part of completing repairs.

We are restoring services in VAN, and have had reports of delayed calls in our SJC POP. We are working on restoring services in both POPs as quickly as possible.

We have been able to restore the affected router. We are working on bringing stability back to the VAN POP. Dedicated Voice Circuit customers should see connectivity being restored.

We are continuing to restore services in VAN POP and will post more updates to this page as we have them.

We are continuing to restore services in VAN POP and will post more updates to this page as we have them.

We are restoring services in VAN. Preliminary tests and health checks are passing but we expect some continue instability as we resolve the issue.

We are restoring connectivity to the VAN POP and affected equipment is being brought back online.

We are currently performing repairs on the affected equipment. We will update this page again shortly.

We have technicians onsite in our VAN datat centre facility investigating the issue with one of our core routers and the fibre connectivity into our POP. We will update this page as we know more.

We are continuing to investigate this issue.

We are currently investigating an issue with a Core Router in our VAN POP. Customers with Voxter Dedicated Voice circuits will not have connectivity via that circuit. Customers with backup connections will failover to our backup POPs. We will post here as we learn more.

Normal operations have resumed in our VAN POP. We will share a post mortem on this page after we complete our investigation.

We are continuing to monitor the affected hardware. Normal operations have returned to the VAN POP.

We have implemented another fix to the affected edge router in VAN. We are seeing normal operations and stability return to the POP. We will continue to monitor.

We are continuing to work on returning stability to our edge router in VAN POP. We will post more on this page as we know more.

We are seeing instability return to the affected edge router in VAN POP.

We have been able to implement a repair to the affected edge router in Vancouver. We will continue to monitor the network; all operations have been restored.

We have identified an issue causing instability in one of our edge routers in VAN POP. We are working on implementing work arounds.

We are continuing to investigate the issue in our VAN POP and will post more information as we have it.

Currently our VAN POP is not receiving calls. We are investigating packet loss in one of our Edge routers in the VAN POP. We will post here as we know more about the problem.

We are investigating an issue that is impacting the delivery of some calls to customers registered to ur VAN POP. We will post more here as we investigate.

This incident has been resolved.

We have resolved the timeout issues in the cluster impacting Phone applications. We will continue to monitor for further issues.

We have seen some timeouts return to the affect database. We are implementing an additional fix.

Timeouts have been removed from the system. All functions have returned to normal. We will continue to monitor for any impact.

We have identified the cause of the slow responses. Our engineers are currently repairing the database server with the load issues.

We are investigating an issue with our provisioning server. Some requests on our databases are taking longer to complete than normal due to a higher than expected load. On phone applications will be impacted as well as log in/log out functions.

We have seen no further issues in our Vancouver POP and all services have been restored. We apologize for the interruption. We will provide a post mortem within 24hrs.

The issue in our Vancouver POP has been resolved. We are continuing to monitor the issue, and will post additional updates here as needed.

We are continuing to work on restoring services in Vancouver. We will update this page as we know more, we are working on resolving this as quickly as possible.

We have identified an issue where customers connected to our Vancouver POP are receiving no service messages. We have identified the issue and are working on a resolution as quickly as possible

We have returned to normal operations. Our team is still investigating the root cause of the issue and we will provide a post mortem via this page when it is available.

Services have been restored. Phones that failed over to backup POPs will reconnect to VAN automatically as their registrations refresh. Inbound and Outbound calls are being delivered. We will continue to monitor the situation and provide further updates as needed.

We are continuing to work on solving the issue as quickly as possible. Some phones will have already failed back to VAN. Inbound calls are being delivered intermittently.

We are aware of an issue impacting phones phones registered to our Vancouver POP. Customer phones will failover to our backup POPs; this process takes up to 10 minutes in some cases. We are working on having this issue resolved as quickly as possible.

We are continuing to monitor for any further issues.

All services in VAN have been restored. We will continue to monitor the situation an post updates here as needed.

We have seen instability return to one of our routers in our VAN POP. We are investigating and will have the issue remediated as soon as possible.

Services have been restored. Phones that failed over to backup POPs will reconnect to VAN automatically as their registrations refresh. Inbound and Outbound calls are being delivered. We will continue to monitor the situation and provide further updates as needed.

We are continuing to work on solving the issue as quickly as possible. Some phones will have already failed back to VAN. Inbound calls are being delivered intermittently.

We are aware of an issue impacting phones phones registered to our Vancouver POP. Customer phones will failover to our backup POPs; this process takes up to 10 minutes in some cases. We are working on having this issue resolved as quickly as possible.

We continue to see our VAN POP operating without issue. We will be completing some maintenance on equipment tonight. We are closing this status notice.

We have not seen issues return to the VAN POP since we implemented some changes on 12/18. We continue to monitor our VAN POP closely.

After investigation of the loss of connectivity events from 12/14, 12/17 and 12/18, we have implemented a number of changes that should ease problems if the issue returns. There is malformed network traffic that is impacting one of our core routers; the issue re-appears mid-morning Pacific time. Failover POPs are standing by and ready to accept registrations in the event of an issue. A replacement for affected device is currently being configured and will be replaced Thursday evening, 12/20.

This incident has been resolved.

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

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.

We are continuing to investigate this issue.

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.

This incident has been resolved.

A fix has been implemented and service has restored to normal. We are continuing to monitor the situation closely.

We are currently experiencing an issue with our Vancouver and San Jose POPs. Our team is currently investigating and will post updates as they become available.

We have resolved the issue with SJC POP and have monitoring it for several hours. All traffic has resumed its regular path.

We have identified the issue with our SJC POP and are currently working to resolve the issue. All traffic will continue to be redirected in the interim.

We are currently investigating an issue with our SJC POP; it is temporarily offline. All traffic will be properly redirected to another POP. We will provide updates as they become available. If you do experience any issues, please contact our support team.

Resolved - We have resolved the issue with SJC Media Servers will be monitoring it. All traffic has resumed its regular path.

We have identified the issue with our SJC Media Servers and will have it resolved shortly.

Investigating - We are currently investigating an issue with our SJC POP; we are experiencing issues with the media servers. We will provide updates as they become available. If you do experience any issues, please contact our support team.

We have resolved the issue with our SJC Media Servers. All traffic has resumed its regular path.

Investigating - Our SJC media servers are experiencing issues once again. We are investigating this problem right now. We will provide updates as they become available.

This incident has been resolved.

ADSL is back online and is being monitored. Please contact us at support@voxter.com, enterprisesupport@ooma.com or by phone at 604-629-8647 if you're still experiencing issues.

We are currently investigating an issue with Voxter/Ooma provided ADSL in the Vancouver area due to a down fibre line. Customers who have secondary or a failover connection should not be impacted. Please contact us at support@voxter.com, enterprisesupport@ooma.com or by phone at 604-629-8647 if you're experiencing issues and would like your calls forwarded to a backup device.

This incident has been resolved.

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.

We are continuing to investigate this issue.

We are currently experiencing an issue with intermittent call connectivity. Our team is currently investigating and will provide updates as soon as possible.

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.

We are currently experiencing an issue with intermittent call connectivity. Our team is currently investigating and will provide updates as soon as possible.

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 support@voxter.com or enterprisesupport@ooma.com.

While our team is currently investigating, it is also expected that bidirectional calls are intermittently connecting.

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.

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 support@voxter.ca

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 enterprisesupport@ooma.com if you are unable to make or receive calls at this time.

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

Our monitoring over the last 24 hours has shown no more instability in the network after Telia was removed yesterday. We are considering this outage resolved.

At approximately 10:55am PT, a service provider (Telia Networks) that is one of many networks that provides internet connectivity into our facility in San Jose started to experience significant latency and packet loss that resulted in network links coming up and down repeatedly (also known as flapping). As a precautionary measure, our network operations team took our San Jose proxies out of rotation, which would have caused clients attached to our network to fail over to the next closest site in Vancouver. Any device attached to our network that was provisioned using our device provisioner will automatically do this. Some customers that have provisioned their devices manually may need extra guidance on how to configure fail-over settings correctly. If your device was offline during this window, please reach out to enterprisesupport@ooma.com to have your configuration reviewed and updated. Finally, at approximately 12:07pm PT, we were able to make appropriate modifications to our routing infrastructure in San Jose to take Telia Networks out of the network path, which restored connectivity there without packet loss or latency.

We have a confirmed outage on our SJC impact. We are still investigating the cause. We expect phones and calls in that region to failover to our VAN POP shortly.

We are currently investigating a possible outage with our SJC POP. Updates to follow shortly.

We believe the issue is resolved, and have monitored for the last 24 hours. We had a momentary blip with one of the routers at our Vancouver Data Centre yesterday morning. This affected some calling for select customers as the phones failed over to our San Jose Data Centre.

We have identified an issue within our Vancouver POP that was causing intermittent call connecting issue. We have implemented a fix and will continue to monitor, but calls should be connecting as usual!

We are continuing to investigate this issue.

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

This incident has been resolved.

An issue was identified with one of our upstream carriers that affected a subset of calls made through our San Jose POP between 18:26 - 18:52 UTC. We escalated to the carrier and they identified an issue within their network. They have resolved the issue and are monitoring. We are also continuing to monitor. Affected calls would have either been dropped or experienced poor audio.

We are currently investigating reports of degraded performance in our San Jose POP. Updates to follow.

Upstream carrier issues appear to be resolved.

The issue has been identified and a fix is being implemented.

Our upstream carriers have advised that there is a major nationwide outage with multiple telephone carriers, particularly with Sprint and T-Mobile. This has resulted in intermittent outbound call failures across the PSTN.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

Our upstream carrier has advised that they are experiencing issues connecting calls which may result in a busy tone being sent back. The issue has been identified and is in the process of being resolved.

This morning at 05:34 PT our San Jose data center lost network connectivity and became unreachable from the internet. Working with our network operations team, we were able to identify that our equipment was online and operational, and the problem was centric to a BGP routing problem whereby our data center provider was no longer announcing our IP block to the internet. We immediately reached out to the data center operator to engage their network engineering team who were able to restore service at 07:42 PT. We are still waiting for a root cause analysis from the provider, and will be following up to build a plan to mitigate a scenario like this from occurring in the future.

A fix has been implemented and we are continuing to monitor. All traffic has now moved back to SJC.

We have identified an issue with our San Jose POP. Our team is currently working to resolve the issue. Failover to the nearest POP should happen for the majority of users. You may experience calls talking slightly longer to connect during this time. If you are experiencing issues, please send us an email at enterprisesupport@ooma.com.

We are currently experiencing issues with our San Jose POP. Our team is currently investigating the issue. We will update once we have more information.

This incident has been resolved.

Our SJC POP is now back online. We are continuing to monitor the situation.

We are experiencing an issue with our SJC POP; a recurrence of the issue we faced this morning. We have put alternative routes in place and all clients should fail over to our Vancouver POP within a few minutes. We are working with our data center provider to resolve the issue.

The routing issue at our SJC POP is now resolved. Our team will keep monitoring for the rest of the day to be sure, but all systems are currently fully operational

Routing issues on our SJC POP have been resolved at our data center after they removed the bad link yesterday evening. Our Network team will continue to monitor today.

We have identified an upstream network loop within GTT/NTT networks. Our upstream vendors are attempting to work around these networks on their end.

An intermittent upstream internet routing issue has been identified in San Jose. This is causing intermittent call quality, call control, and dropped calls to San Jose. This issue is out of our direct control, however our engineers are attempting to adjust routing on our end to mitigate the impact this is having on our services.

Calling on SJC has been stable for the past 5 hours and the Engineering Team are confident that the issue has been resolved.

We have identified a node within SJC that was destabilizing the San Jose POP. We have removed this node from the rotation while we investigate and resolve the root cause. All calling services have been restored. If you're still experiencing issues please submit a ticket to enterprisesupport@ooma.com

We are currently investigating an outage in our San Jose pop. Updates to follow.