Is Five9 Down?

No — Five9 is up

Reachable from all 8 checked regions

Average response time: 127ms

Last checked 4 hours ago · checks run every 6 hours

Official status page: https://www.five9.com/trust/system-status

Five9 uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

160ms

Avg response, 30 days

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

30-day history

20-day clean streak

Aug 12 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.

arn

208ms

DNS 0ms TCP 10ms TLS 24ms TTFB 174ms

bom

20ms

DNS 0ms TCP 1ms TLS 4ms TTFB 13ms

cdg

215ms

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

dfw

22ms

DNS 0ms TCP 0ms TLS 4ms TTFB 16ms

ewr

93ms

DNS 0ms TCP 12ms TLS 28ms TTFB 69ms

fra

40ms

DNS 1ms TCP 1ms TLS 4ms TTFB 30ms

gru

333ms

DNS 0ms TCP 4ms TLS 9ms TTFB 328ms

iad

85ms

DNS 2ms TCP 9ms TLS 21ms TTFB 62ms

What Five9 does

Five9 runs cloud contact centers, handling inbound and outbound voice, routing, agent desktops, workforce management and reporting. Its customers are support and sales organisations whose agents log in to it for an entire shift. An outage stops paid staff working and leaves callers unanswered, so the cost is measured per minute rather than per incident.

What an outage looks like

Agents cannot log in to the desktop, or log in and then find the softphone will not register. Calls connect but carry one-way or no audio. Inbound calls stop arriving in queues while callers hear ringing or a fast busy. Outbound dialling campaigns pause. Supervisors lose live queue statistics and real-time dashboards, and reporting falls behind even after calls resume.

What to do about it

five9.com/trust/system-status is the public page and carries the current state plus incident history. Detailed status for your own instance sits behind the Status Portal login, so the public page and your tenant can legitimately disagree. If agents cannot take calls, the immediate move is to fail traffic over to whatever backstop your carrier or IVR provides rather than waiting, because unanswered inbound calls are not recoverable later.

Is it down for everyone, or just you?

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

Test it yourself

Related services

RingCentral

Dialpad

8x8

Twilio

Five9 outage FAQ

Is it Five9 or my agents' network?

Check whether the failure is shared. A single agent with registration trouble points at that workstation, its headset or the local network, while every agent failing at once points at the platform. Voice quality problems that follow one site but not another are usually local bandwidth or firewall rules, since media paths differ per location.

Where do I see status for my own Five9 instance?

Behind the Status Portal login. Five9's public page at five9.com/trust/system-status reports platform-wide state and incident history, while instance-specific detail requires signing in. This is why the public page can read All Systems Operational while your own tenant has a problem, and why an all-clear there is not proof your contact center is healthy.

What happens to calls that arrive during an outage?

Inbound calls that cannot be delivered are lost rather than queued. Voice has no equivalent of a retried webhook: a caller who hears a fast busy or unanswered ringing simply hangs up. This is why contact centers keep a carrier-level or IVR failover path, and why the first action during an incident is to divert traffic rather than to wait for recovery.

Will my reporting data be missing afterwards?

Reporting commonly lags rather than loses. Statistics and recordings are written by separate pipelines from live call handling, so those pipelines can be catching up for a while after agents are back on calls. Treat gaps in dashboards during the hours after an incident as backlog until the incident report says otherwise.

Does a Five9 outage affect my CRM as well?

Not directly, though the integration between them will stall. Screen pops, click-to-dial and call logging depend on Five9 being reachable, so those features stop while the CRM itself keeps working normally for everything else. Agents can usually keep updating records by hand during an incident, which avoids a second backlog afterwards.

How we measure this

We request Five9's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
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 Five9 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 Five9 goes down

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

Start Free Monitoring

Free plan available No credit card required