GetResponse Status · History · Incident #63977

RESOLVED

Ongoing Services Issue

Major · Started Apr 27, 2026 · 10:38 AM

  • Duration

    55m

  • Severity

    Major

  • Detection lead

  • User reports

Summary

Ongoing Services Issue

This incident has been resolved.


  • Started

    Apr 27, 2026 · 10:38 AM

  • Resolved

    Apr 27, 2026 · 11:33 AM

  • Duration

    55m

  • Severity

    Major

Event timeline

How this incident unfolded

  • Investigating

    Apr 27 · 10:38 AM GetResponse

    Some users may be experiencing issues trying to log into GetResponse. Our team's working on a solution. We'll let you know when access to GetResponse is restored. Sorry for the disruption!

  • Investigating

    Apr 27 · 10:45 AM GetResponse

    We are continuing to investigate this issue.

  • Investigating

    Apr 27 · 10:51 AM GetResponse

    We're experiencing issues affecting some of our services. Our team is working on a solution. We will keep you updated on the progress.

  • Investigating

    Apr 27 · 10:59 AM GetResponse

    We are continuing to investigate this issue.

  • Investigating

    Apr 27 · 11:03 AM GetResponse

    We are continuing to investigate this issue.

  • Monitoring

    Apr 27 · 11:17 AM GetResponse

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

  • Monitoring

    Apr 27 · 11:33 AM GetResponse

    We are continuing to monitor for any further issues.

  • Resolved

    Apr 27 · 11:33 AM GetResponse

    This incident has been resolved.

Get alerted before the next GetResponse outage.

Pulsetic catches degradations minutes before vendors acknowledge them.