Live status & reliability report

GetResponse status, outages & reliability

GetResponse is an email marketing and automation platform headquartered in Gdansk, Poland.

Data updated Nov 1, 2026 · score recalculated

Over the last 90 days GetResponse had 99.94% effective uptime across 2 status page incidents, resolving them in 3h 47m on average.

90.9/100Reliability scoreVisit GetResponse ↗

Is GetResponse down right now?

No, GetResponse is up and running.

  • GetResponse's status page reports all systems operational. Checked .
  • All 3 GetResponse pages we check are responding. Checked .

Official GetResponse status page ↗

Uptime (90d)99.94%1h 8m weighted downtime
Incidents (90d)20.3 per 30 days
Major / partial outages0
Avg time to resolve3h 47m
Outages we detected0by our independent probes

90-day uptime

Aug 4, 2026 – Sep 13, 2026: no incidentsSep 14, 2026: 97.39% uptime, 1 incident (Degraded performance)Sep 15, 2026 – Oct 20, 2026: no incidentsOct 21, 2026: 97.87% uptime, 1 incident (Degraded performance)Oct 22, 2026 – Nov 1, 2026: no incidents
90 days ago99.947% average daily uptimeToday
  • No incidents
  • Degraded
  • Partial outage
  • Major outage
  • No data

Key facts about GetResponse's reliability

  • Over the past 12 months, GetResponse published 16 incidents on its status page, 6 of them partial or major outages.
  • Its longest outage on record in that time was “Issue with SMS provider” on May 8, 2026, which lasted 2d 11h.
  • The part of GetResponse most often affected was Marketing Pages (7 of 16 incidents).
  • Incidents most often began on a Tuesday (5 of 16, UTC).
  • GetResponse's 90-day uptime of 99.94% is above the average for email marketing platforms (99.71%).

Score breakdown

Uptime · 40% weight
95
99.947% effective uptime
Incident frequency · 20% weight
92
0.33 weighted incidents per 30 days
Time to resolve · 20% weight
73
3h 47m average
Transparency · 20% weight
100
No unreported outages detected

How the score is calculated →

Incidents per month

012343 degraded performance incidents1 informational incident4Dec1 degraded performance incident1Jan ’26Feb1 partial outage incident1 informational incident2Mar2 partial outage incidents2Apr1 partial outage incident1 informational incident2MayJunJulAug1 degraded performance incident1Sep1 degraded performance incident1OctNov
  • Major outage
  • Partial outage
  • Degraded
  • Informational

Response time

Daily average response time of GetResponse's public pages, measured by our probes.

Not enough data yet — this chart fills in as our monitoring runs.

Score trend

Daily reliability score (rolling 90-day window).

Not enough data yet — this chart fills in as our monitoring runs.

GetResponse incident history (last 90 days)

Source: GetResponse status page · last checked · Subscribe via RSS

Our independent monitoring

We check these public GetResponse pages every 5 minutes. An outage is recorded after two consecutive failed checks.

PageLast checkUptime (30d)Avg response
HomepageUp 100%595 ms
App loginUp 100%512 ms
API v3 (unauthenticated)Up 100%336 ms

How GetResponse compares

Most reliable GetResponse alternatives →

GetResponse status FAQ

Is GetResponse down right now?

No, GetResponse is up and running. GetResponse's status page currently reports all systems operational, and all 3 of the GetResponse pages we check every five minutes are responding. This page updates automatically when that changes.

How reliable is GetResponse?

GetResponse has a reliability score of 90.9 out of 100, ranking #7 of 13 email marketing platforms. Over the last 90 days it had 99.94% effective uptime.

How often does GetResponse have outages?

GetResponse published 2 incidents on its status page in the last 90 days (0 partial or major outages) and 16 in the past 12 months.

How long do GetResponse outages last?

GetResponse resolves incidents in 3h 47m on average. Its longest outage in the past year lasted 2d 11h, on May 8, 2026.

Does GetResponse have a status page?

Yes. GetResponse's official status page is status.getresponse.com. We read it every five minutes and keep its full incident history.