Is Gusto Down?

No — Gusto is up

We cannot measure Gusto directly — it blocks automated checks — but Gusto's own status page currently reports no issues.

Last checked 3 hours ago · checks run every 6 hours

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

Why there is no uptime figure on this page

The last time we fetched Gusto'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 Gusto 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 Gusto's own status feed, which you can weigh yourself.

30-day history

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

dfw

edge reachable

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

ewr

edge reachable

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

fra

edge reachable

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

gru

edge reachable

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

iad

edge reachable

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

jnb

edge reachable

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

lax

edge reachable

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

lhr

edge reachable

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

What Gusto does

Gusto is a payroll, benefits and HR platform used mainly by small and mid-sized US employers. It runs payroll, administers health insurance and retirement enrollment, and holds employee records and onboarding. Its status page reports Payroll, Benefits and HR as separate products alongside the website, mobile app and API, which is how most customers meet it during an incident.

What an outage looks like

The Gusto web app fails to load or hangs after sign-in, and payroll runs cannot be submitted or approved. Sign-in can break independently: Gusto lists two-factor authentication text messages as its own component, so an account using SMS codes can be locked out while the rest of the product serves normally. The mobile app and API are reported separately.

What to do about it

Check status.gusto.com and read the specific component rather than the top banner. Gusto publishes its upstream dependencies there too, including Cloudflare and several AWS services, so an incident is often narrower than the headline suggests. If two-factor authentication text messages are the failing component, the problem is the SMS path and not your password. Do not resubmit a payroll run that may already have been accepted.

Is it down for everyone, or just you?

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

Gusto outage FAQ

Is Gusto down for everyone, or just my company?

Gusto's status page reports components rather than customer segments, so it cannot answer that directly. Start by matching your symptom to a component: Payroll, Benefits, HR, Gusto.com website, Gusto Mobile and API are all listed separately. If every component reads operational while only your team is affected, look at your network, browser session or SSO provider next.

Can I still run payroll during a Gusto outage?

It depends which component is affected. Payroll is reported separately from Benefits, HR and the website, so an incident scoped elsewhere can leave payroll submission working. If Payroll itself is the failing component, wait rather than retrying: a submission that timed out may already have been accepted, and a duplicate payroll run is far harder to unwind than a late one.

I cannot receive my Gusto two-factor code. Is that an outage?

Check the two-factor authentication text messages component, which Gusto reports on its own. When that row is affected the failure is in SMS delivery rather than in your credentials, so repeatedly re-requesting a code will not help. It also means the rest of Gusto can be entirely healthy while you cannot get past the login screen.

Does a Gusto outage mean my employees will be paid late?

Not automatically. Whether a payment is affected depends on where in the cycle the outage falls and whether your run was already submitted and accepted. Gusto does not publish that relationship on its status page, so confirm the state of the specific payroll run once the Payroll component recovers rather than assuming either outcome.

Is the problem Gusto or one of its providers?

Often the latter, and Gusto makes this unusually easy to see. Its status page lists Cloudflare SSL Certificate Provisioning, Cloudflare Gateway, Cloudflare Authoritative DNS, Cloudflare Bot Management and several AWS services as components in their own right. When one of those rows is the affected one, the incident is upstream and resolves when the provider does.

How we measure this

We request Gusto'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 Gusto 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 Gusto blocks our checks entirely, we report the vendor's own status directly.

Get alerted when Gusto 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