Skip to main content

Is 8x8 Down?

8x8 is responding, but blocks automated checks

When we last reached 8x8 directly, it answered and refused us — origin requires authentication for automated clients. An answer is proof the origin was serving traffic, but it measures our access, not the service, so we publish no percentage.

Last checked · checks run every 6 hours

Official status page: https://status.8x8.com

Why there is no uptime figure on this page

The last time we fetched 8x8's page directly, the origin answered and turned our client away rather than serving the page. That answer tells us the origin was reachable and responding, but it is a response about our automation, not about whether 8x8 works for you.

A percentage built from those checks would measure our own access, so we do not publish one. What this page does show is each region's most recent result and 8x8's own status feed, which you can weigh yourself.

30-day history

Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: blocked from automated checks
Aug 11: blocked from automated checks
Aug 12: blocked from automated checks
Aug 13: blocked from automated checks
Aug 14: blocked from automated checks
Aug 15: blocked from automated checks
Aug 16: blocked from automated checks
Aug 17: blocked from automated checks
Aug 18: blocked from automated checks
Aug 19: blocked from automated checks
Aug 20: blocked from automated checks
Aug 21: blocked from automated checks
Aug 22: blocked from automated checks
Aug 23: blocked from automated checks
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
edge reachable

A static asset loaded in 794ms. That proves the edge is up, but not that the site works.

arn
edge reachable

A static asset loaded in 963ms. That proves the edge is up, but not that the site works.

bom
edge reachable

A static asset loaded in 871ms. That proves the edge is up, but not that the site works.

cdg
edge reachable

A static asset loaded in 621ms. That proves the edge is up, but not that the site works.

dfw
edge reachable

A static asset loaded in 367ms. That proves the edge is up, but not that the site works.

sin
edge reachable

A static asset loaded in 1643ms. That proves the edge is up, but not that the site works.

sjc
edge reachable

A static asset loaded in 216ms. That proves the edge is up, but not that the site works.

syd
edge reachable

A static asset loaded in 1340ms. That proves the edge is up, but not that the site works.

yyz
edge reachable

A static asset loaded in 547ms. That proves the edge is up, but not that the site works.

What 8x8 does

8x8 provides cloud phone service, team messaging, video meetings and contact centre software for businesses. Its Work product covers calling, SMS, fax and chat across desk phones, desktop and mobile, while the Contact Center side handles queued customer calls and agent routing. When it fails, a company's main phone number and its support queue go down together.

What an outage looks like

8x8 reports status separately for Americas, EMEA and APAC, and splits Work Calling into inbound, outbound, endpoints, desk phones, and its mobile and desktop clients, alongside Meet, SSO, fax, messaging and SMS. Contact Center is broken out further by numbered instance. Inbound calls can fail while outbound still connects, and an SSO fault blocks sign-in while calls already in progress continue.

What to do about it

Check status.8x8.com and match both your region and your Contact Center instance, because the page is organised by geography and by numbered instance rather than as one verdict. An SSO component incident is a sign-in problem rather than a telephony one, which changes what you tell staff. Desk phones can retain registration through a portal outage, so place a real test call before declaring the phones down.

Is it down for everyone, or just you?

If this page says 8x8 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

8x8 outage FAQ

Our phones ring out but we can still dial. Is that 8x8?
Very possibly. 8x8 tracks inbound and outbound calling as separate components, and incidents regularly affect one direction while the other works. That asymmetry is confusing on the ground because staff report the system as working. Check the inbound line for your region on the status page, and treat inbound failure as the more urgent case since customers hit it before you do.
Why can I not sign in when calls are still working?
SSO is its own component, separate from calling. When it is affected, already-registered desk phones and signed-in clients often keep working while anyone trying to sign in fresh is blocked. During an SSO incident, avoid signing users out or restarting clients unnecessarily, because a session that is currently working may not be recoverable until sign-in is restored.
Does an 8x8 outage in one region affect our other offices?
Not usually. 8x8 publishes Americas, EMEA and APAC as separate columns and posts incidents against a region, so an EMEA problem can leave North American users untouched. Contact Center goes further and is listed by numbered instance, so two customers in the same region can be affected differently. Identify your instance once and keep it noted for future incidents.
What happens to calls in the queue during a Contact Center outage?
That depends on which component is affected, which is why the numbered instance matters. Contact Center is tracked separately from Work Calling, so a queue and routing problem can occur while direct extensions still ring. Check whether your instance is named in the incident, and if the queue is affected, publishing an alternative contact route is more useful than waiting for it to clear.

How we measure this

  • We request 8x8'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 8x8 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 — and when 8x8 blocks our checks entirely, we report the vendor's own status directly.

Get alerted when 8x8 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