GetResponse Outage History

GetResponse is up right now

GetResponse had 31 outages in the last 2 years totaling 5h 23m of downtime — averaging 1.3 incidents per month.

There were 31 GetResponse outages since June 26, 2024 totaling 5h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getresponse.com

Major February 13, 2025

Ongoing Service Issue with domain services.

Detected by Pingoru
Feb 13, 2025, 10:30 AM UTC
Resolved
Feb 13, 2025, 10:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Feb 13, 2025, 05:47 PM UTC

    We experienced an issue where DKIM authentication dropped for EU DataCenter clients, and their DKIM records appeared to have changed. Our team investigated the root cause and implemented a resolution. The issue has now been fully resolved, and DKIM authentication is functioning as expected. No scheduled email sends were affected during this incident, and all deliveries proceeded as expected. Thank you for your patience and understanding.

Read the full incident report →

Major January 29, 2025

Ongoing Service Issue Affecting EU and US DataCenter Clients

Detected by Pingoru
Jan 29, 2025, 07:35 AM UTC
Resolved
Jan 29, 2025, 07:42 AM UTC
Duration
7m
Timeline · 3 updates
  1. identified Jan 29, 2025, 07:35 AM UTC

    Our developers are working on solving the root cause of the issue. Thank you for your patience!

  2. monitoring Jan 29, 2025, 07:38 AM UTC

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

  3. resolved Jan 29, 2025, 07:42 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 22, 2025

Ongoing Service Issue with Dashboard

Detected by Pingoru
Jan 22, 2025, 01:15 PM UTC
Resolved
Jan 22, 2025, 01:27 PM UTC
Duration
12m
Affected: Dasbhboard
Timeline · 2 updates
  1. investigating Jan 22, 2025, 01:15 PM UTC

    We're experiencing an issue with our Dashboard services. Our team is working on a solution. We will keep you updated on the progress.

  2. resolved Jan 22, 2025, 01:27 PM UTC

    We're happy to report that we've resolved the issues affecting our Dashboard. There should be no more delays or interruptions. Thank you for sticking with us!

Read the full incident report →

Major December 5, 2024

Ongoing Service Issue with login to platform

Detected by Pingoru
Dec 05, 2024, 02:57 PM UTC
Resolved
Dec 05, 2024, 03:03 PM UTC
Duration
5m
Affected: Dasbhboard
Timeline · 2 updates
  1. investigating Dec 05, 2024, 02:57 PM UTC

    We're experiencing an issue with login services. Our team is working on a solution. We will keep you updated on the progress.

  2. resolved Dec 05, 2024, 03:03 PM UTC

    We're happy to report that we've resolved the issues affecting our system. There should be no more delays or interruptions. Thank you for sticking with us!

Read the full incident report →

Major November 7, 2024

Ongoing Service Issue

Detected by Pingoru
Nov 07, 2024, 11:30 AM UTC
Resolved
Nov 07, 2024, 02:29 PM UTC
Duration
2h 58m
Affected: Transactional Emails
Timeline · 2 updates
  1. investigating Nov 07, 2024, 11:30 AM UTC

    We're experiencing an issue with Transactional Emails services for EU DateCenter. Our team is working on a solution. We will keep you updated on the progress.

  2. resolved Nov 07, 2024, 02:29 PM UTC

    We're happy to report that we've resolved the issues affecting our system. There should be no more delays or interruptions. Thank you for sticking with us!

Read the full incident report →

Minor June 26, 2024

Issues with our API

Detected by Pingoru
Jun 26, 2024, 08:49 AM UTC
Resolved
Jun 26, 2024, 10:48 AM UTC
Duration
1h 59m
Affected: Contacts (+Import)Email Marketing
Timeline · 5 updates
  1. investigating Jun 26, 2024, 08:49 AM UTC

    We're experiencing issues with our API affecting on retrieving segments via API and we have connected to this issue in newsletters - only for MAX PL customers. We're working hard to fix the issues as quickly as we can.

  2. investigating Jun 26, 2024, 08:55 AM UTC

    We are continuing to investigate this issue.

  3. identified Jun 26, 2024, 09:53 AM UTC

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

  4. monitoring Jun 26, 2024, 10:20 AM UTC

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

  5. resolved Jun 26, 2024, 10:48 AM UTC

    This incident has been resolved.

Read the full incident report →