PhoneBurner had 11 outages in the last 2 years totaling 9h 36m of downtime — averaging 0.5 incidents per month.
There were 11 PhoneBurner outages since May 30, 2024 totaling 9h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating performance issues with the website.
Site performance is improving. We're monitoring.
Site performance is back to normal operation.
We have identified an intermittent issue with the dialer where the buttons don't work as expected. We have identified it as an issue with one of our vendors. We're working closely with them to resolve the issue.
The vendor is still researching the issues on their end.
We have started the process of moving all the usage away from the problematic vendor. We are monitoring. We recommend any users experiencing the issues log out of your account and login again to ensure you pickup the new configurations.
Traffic is migrated away from the problematic vendor and we'll continue monitoring.
We are investigating issues with the site
We've identified the source of the issue and we're remediating. We're starting to see performance improvements.
We are seeing full site performance recovery. We are monitoring.
Site performance has been restored. We've determined that an upstream provider was having performance issues that degraded some aspects of our site. We have mitigated those issue and the site is performing well. We'll continue monitoring.
We are investigating degraded website performance
Engineers have identified the issue and we're seeing performance recover. We're monitoring.
Site performance has been restored.
We have identified the issue and are working on a resolution.
Engineering team has identified a fix and an update and/or fix should be deployed shortly.
Calls are completing successfully. We are monitoring the make sure the system is stable.
The incident is resolved.
We are investigating the issue.
The team continues to investigate the issue. A new update will come shortly.
We are continuing to work on a fix for the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investing issues with the site loading slowly.
We have identified the source of the issue and the team is working on resolution.
We're observing site performance improvements. We're monitoring.
The site performance has been restored.
We have identified an issue with some outbound calls through the dialer. This includes call transfers as well. Engineers are actively working through the issues.
Issue has been identified and resolved. We are monitoring.
Systems are fully operational.
We are currently researching issues related to slow site performance.
We have identified the source of the issue and are deploying a fix.
A fix has been implemented and performance is recovering. We are monitoring.
Issues are not resolved. We are triaging a deployment issue.
Fixes are confirmed in good working order. We are monitoring performance.
Site performance is fully restored and operating normally.
We are currently investigating an issue with the dialer.
We have identified the issue and are working on a fix.
We are actively resolving the issue and we're starting to see recovery.
Dialer has been restored and fully functional.
We are currently investigating reports of a slow and/or unresponsive site.
The team is still researching. We'll update again shortly.
The team believes there is a performance problem with some in-browser integrations. We have disabled that integration and are monitoring performance. We also believe this does not impact everyone.
The team has confirmed that the 3rd party library in the browser is in fact driving high CPU and making the browser window unresponsive. The integration has been disabled, and the site is in working as expected. We are closing the incident and the team will continue to monitor.