Myphoner - Notice history

All systems operational

Myphoner Voice - Operational

100.0% uptime
Aug 2016 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2016
Sep 2016
Oct 2016

Support Widget/Chat - Operational

Support Backend - Operational

Marketing and Documentation Pages - Operational

Notice history

View current status

Oct 2016

Excessive memory consumption causing long response times
ResolvedDegraded performance31 minutes
  • ResolvedUTC

    The fix has been confirmed to resolve the issue.

  • MonitoringUTC

    Fix is deployed and we are monitoring the effects.

  • IdentifiedUTC

    We've identified the issue and a fix is being rolled out as we speak.

  • InvestigatingUTC

    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.

Sep 2016

Email delivery issues
ResolvedDegraded performance1 hour 6 minutes
  • ResolvedUTC

    We have confirmed that emails are delivering normally again.

  • MonitoringUTC

    This issue has reportedly been resolved. Now monitoring.

  • IdentifiedUTC

    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.

Downtime
ResolvedPartial outage2 hours 47 minutes
  • ResolvedUTC

    This incident has been resolved.

  • UpdateUTC

    Our hosting provider is still reporting issues, but all myphoner systems are running stable again. We will continue to monitor for the time being.

  • MonitoringUTC

    Looks like systems are back up. Still monitoring. More updates on https://status.heroku.com/

  • IdentifiedUTC

    Our hosting and infrastructure provider is having major issues. We are still awaiting them to resolve their issues.

  • UpdateUTC

    Still seeing issues. Only some requests gets through.

  • MonitoringUTC

    Looks like systems are slowly getting back up. We are monitoring.

  • IdentifiedUTC

    Confirmed: it's an issue with our hosting and infrastructure provider. We are awaiting their investigation. See more at https://status.heroku.com/

  • UpdateUTC

    Systems at our hosting and infrastructure providers are also affected. Still investigating.

  • InvestigatingUTC

    We are investigating downtime on several systems simultaneously.

Long response times
ResolvedDegraded performance2 hours 54 minutes
  • ResolvedUTC

    A fix has been issued and systems has been showing normal response times for an extensive period.

  • IdentifiedUTC

    We have identified the cause of the long response times and timeouts. We are now working on a fix.

  • UpdateUTC

    We have scaled the systems and restarted some slow processes to regain operability. We are still investigating the root cause of this incident.

  • InvestigatingUTC

    We are experiencing long response times, sometimes resulting in timeouts. The app can appear to be down.

Aug 2016

Application crash
ResolvedPartial outage2 minutes
  • ResolvedUTC

    We are back online after rolling back to the last stable release. We identified a flaw in our deploy procedure that is being fixed.

  • IdentifiedUTC

    We have an application crash due to a bad deploy, we are rolling back to the last working version as we speak.

Previous

Aug 2016 to Oct 2016

Next