Web Application - Operational
Previous page
Next page
Myphoner Voice - Operational
Marketing and Documentation Pages - Operational
Marketing and Documentation Pages
Support Widget/Chat - Operational
Support Widget/Chat
Support Backend - Operational
Support Backend
The fix has been confirmed to resolve the issue.
Fix is deployed and we are monitoring the effects.
We've identified the issue and a fix is being rolled out as we speak.
We are investigating a series of automatic process reboots due to excessive memory consumption. Some users may have experienced long response times or even timeouts.
We have confirmed that emails are delivering normally again.
This issue has reportedly been resolved. Now monitoring.
The IP of our email server has been registered on a blacklist, and some receivers refuse to accept emails from us, because they are mistaken as spam. We are working with our email delivery provider to resolve.
This incident has been resolved.
Our hosting provider is still reporting issues, but all myphoner systems are running stable again. We will continue to monitor for the time being.
Looks like systems are back up. Still monitoring. More updates on https://status.heroku.com/
Our hosting and infrastructure provider is having major issues. We are still awaiting them to resolve their issues.
Still seeing issues. Only some requests gets through.
Looks like systems are slowly getting back up. We are monitoring.
Confirmed: it's an issue with our hosting and infrastructure provider. We are awaiting their investigation. See more at https://status.heroku.com/
Systems at our hosting and infrastructure providers are also affected. Still investigating.
We are investigating downtime on several systems simultaneously.
A fix has been issued and systems has been showing normal response times for an extensive period.
We have identified the cause of the long response times and timeouts. We are now working on a fix.
We have scaled the systems and restarted some slow processes to regain operability. We are still investigating the root cause of this incident.
We are experiencing long response times, sometimes resulting in timeouts. The app can appear to be down.
We are back online after rolling back to the last stable release. We identified a flaw in our deploy procedure that is being fixed.
We have an application crash due to a bad deploy, we are rolling back to the last working version as we speak.
Aug 2016 to Oct 2016
Next