Live status & reliability report

emerchantpay status, outages & reliability

emerchantpay is a UK-based payment service provider and acquirer, running the Genesis gateway, that serves high-risk sectors including online gaming.

Data updated Nov 1, 2026 · score recalculated

Over the last 90 days emerchantpay had 99.97% effective uptime across 4 status page incidents, resolving them in 3h 41m on average.

91.7/100Reliability scoreVisit emerchantpay ↗

Is emerchantpay down right now?

No, emerchantpay is up and running.

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

Official emerchantpay status page ↗

Uptime (90d)99.97%33m weighted downtime
Incidents (90d)40.4 per 30 days
Major / partial outages0
Avg time to resolve3h 41m
Outages we detected0by our independent probes

90-day uptime

Aug 4, 2026 – Sep 22, 2026: no incidentsSep 23, 2026: 97.70% uptime, 1 incident (Degraded performance)Sep 24, 2026 – Nov 1, 2026: no incidents
90 days ago99.974% average daily uptimeToday
  • No incidents
  • Degraded
  • Partial outage
  • Major outage
  • No data

Key facts about emerchantpay's reliability

  • Over the past 12 months, emerchantpay published 5 incidents on its status page, 1 of them partial or major outages.
  • Its longest outage on record in that time was “Temporary issues in 3DS authentications with Mastercard only” on Jul 15, 2026, which lasted 1h 5m.
  • The part of emerchantpay most often affected was Genesis - API (PRODUCTION) (4 of 5 incidents).
  • emerchantpay reported 4 incidents in the last 90 days, up from 1 in the 90 days before.
  • emerchantpay's 90-day uptime of 99.97% is above the average for iGaming payment providers (99.48%).
  • It resolves incidents more slowly than the typical iGaming payment provider: 3h 41m on average, against a median of 2h 28m.

Score breakdown

Uptime · 40% weight
97
99.974% effective uptime
Incident frequency · 20% weight
90
0.42 weighted incidents per 30 days
Time to resolve · 20% weight
74
3h 41m average
Transparency · 20% weight
100
No unreported outages detected

How the score is calculated →

Incidents per month

01234DecJan ’26FebMarAprMayJun1 partial outage incident1Jul1 informational incident1Aug1 degraded performance incident1 informational incident2Sep1 informational incident1OctNov
  • Major outage
  • Partial outage
  • Degraded
  • Informational

Response time

Daily average response time of emerchantpay'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.

emerchantpay incident history (last 90 days)

Source: emerchantpay status page · last checked

Our independent monitoring

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

PageLast checkUptime (30d)Avg response
Genesis gatewayUp 100%622 ms
Web payment formUp 100%433 ms
HomepageUp 100%476 ms

How emerchantpay compares

Most reliable emerchantpay alternatives →

emerchantpay status FAQ

Is emerchantpay down right now?

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

How reliable is emerchantpay?

emerchantpay has a reliability score of 91.7 out of 100, ranking #4 of 9 iGaming payment providers. Over the last 90 days it had 99.97% effective uptime.

How often does emerchantpay have outages?

emerchantpay published 4 incidents on its status page in the last 90 days (0 partial or major outages) and 5 in the past 12 months.

How long do emerchantpay outages last?

emerchantpay resolves incidents in 3h 41m on average. Its longest outage in the past year lasted 1h 5m, on Jul 15, 2026.

Does emerchantpay have a status page?

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