Is Genesys Cloud Down?

No — Genesys Cloud is up

Reachable from all 8 checked regions

Average response time: 209ms

Last checked 40 minutes ago · checks run every 6 hours

Official status page: https://status.mypurecloud.com

Elevated Error Rates - EMEA (UAE)

critical monitoring

Genesys Cloud services in the EMEA (UAE) region remain unavailable due to significant infrastructure challenges affecting the platform provider. This incident has caused widespread service disruptions impacting core platform functions including database operations, virtual machine provisioning, monitoring systems, message processing, storage operations, and automated workflows, with no estimated time for recovery. This post consolidates the previous announcement due to the volume of updates previously provided, and Genesys will continue to share updates as new information becomes available. We strongly recommend all affected customers migrate workloads to alternate AWS regions, work with your Genesys Cloud account team on migration planning, and export critical data and configurations to ensure business continuity if not already done so. Please contact your Genesys Cloud account team if you need assistance or have questions.

Components the vendor reports as affected: EMEA (UAE) Major Outage

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Genesys Cloud fail from enough regions to rule out probe noise.

Genesys Cloud uptime

—

Last 7 days

—

Last 30 days

—

Last 90 days

—

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 2 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

Jul 25 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

314ms

DNS 0ms TCP 2ms TLS 10ms TTFB 173ms

arn

202ms

DNS 0ms TCP 1ms TLS 6ms TTFB 177ms

bom

372ms

DNS 0ms TCP 3ms TLS 8ms TTFB 313ms

cdg

168ms

DNS 0ms TCP 2ms TLS 7ms TTFB 144ms

dfw

89ms

DNS 0ms TCP 1ms TLS 10ms TTFB 80ms

ewr

98ms

DNS 0ms TCP 2ms TLS 7ms TTFB 89ms

fra

178ms

DNS 0ms TCP 1ms TLS 8ms TTFB 169ms

gru

257ms

DNS 0ms TCP 3ms TLS 10ms TTFB 197ms

yyz

81ms

DNS 0ms TCP 1ms TLS 6ms TTFB 73ms

What Genesys Cloud does

Genesys Cloud is a hosted contact center platform that runs inbound and outbound voice, IVR, ACD routing, web messaging, chat and email for support and sales teams. Agents work in a browser softphone rather than on desk hardware, so the platform sits between a company's customers and the people answering them. Capacity is split across separate Americas, Asia Pacific and EMEA regions.

What an outage looks like

Agents see the softphone fail to register or calls drop mid-conversation, while queued callers hear silence or are routed nowhere because ACD is affected. Web messaging and chat widgets on the company's own site stop delivering. Because the status page reports per region, one region can show a major outage while every other region keeps answering normally.

What to do about it

Check status.mypurecloud.com and read your own region's row rather than the headline: the page splits every component across Americas, Asia Pacific and EMEA groups. Identity and Access Management is listed separately from the channels, so a login failure and a call failure are different incidents. community.genesys.com carries operator discussion when the status page has not yet been updated.

Is it down for everyone, or just you?

If this page says Genesys Cloud is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Genesys Cloud outage FAQ

Is Genesys Cloud down for everyone or only my region?

Almost always only some regions. Genesys Cloud reports each component separately for Americas, Asia Pacific and EMEA, and incidents are frequently confined to a single named region while every other region keeps handling calls. Find the region your tenant runs in first, then read that row. A red banner at the top of the status page does not mean your own contact center is affected.

Can agents still take calls if the Genesys Cloud softphone fails?

Not through the browser softphone, which depends on the platform to register. Genesys Cloud tracks Genesys Cloud Soft Phone as its own component, separate from Inbound Calls and ACD Routing, so check which one is red. If routing is healthy but the softphone is not, the failure is at the agent's endpoint rather than in the queue, and callers may still be reaching the IVR.

Does a Genesys Cloud outage affect recordings and reporting?

They are tracked separately and often survive a channel outage. Recording, Quality Management, Reporting and Workforce Engagement each have their own rows on the status page, so voice can fail while reporting stays green, or the reverse. If Recording is the affected component, calls connect normally but the audio for that window may not be retained, which matters for compliance teams.

What happens to WhatsApp and Facebook messages during an outage?

Genesys Cloud lists Third-Party Digital Channels as a distinct component from its own Web Messaging and Chat. An incident affecting third-party channels means messages from external networks are not reaching agents, even though the widget on the company's own site works. Both rows are worth reading, because a partial digital outage is easy to mistake for a quiet afternoon.

How we measure this

We request Genesys Cloud's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Genesys Cloud publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Genesys Cloud goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required