Is Gusto Down? How to Tell and What to Do

Is Gusto Down? How to Tell and What to Do

Gusto handles payroll, benefits, and HR compliance for hundreds of thousands of businesses. When it goes down during a payroll run, the consequences are immediate: employees don't get paid on time, direct deposits fail to process, and tax filings are at risk.

The fastest way to know: Statusfield monitors Gusto continuously and alerts you within minutes. Without monitoring, you find out about Gusto outages when payroll processing has already failed.

---

Common Signs of a Gusto Outage

Symptom	What's likely happening
Payroll run won't process or submit	Payroll processing API is degraded
Direct deposit amounts not scheduled	ACH processing pipeline is blocked
Benefits enrollment changes not saving	Benefits administration layer is failing
Time tracking not syncing to payroll	Time tracking integration is degraded
Contractor payments stuck in pending	Payment processing pipeline is backed up
Tax documents unavailable or not generating	Document generation service is down
Dashboard returns 500 errors or blank screen	Web application layer is unavailable

---

How to Confirm It's Gusto, Not You

Before escalating to your HR team, rule out local issues:

1. Test from a different browser and network

Clear your browser cache and try logging in from a different device or mobile connection. If Gusto loads normally on mobile data but not on your office network, a firewall or network policy may be blocking access — not Gusto itself.

2. Check the payroll preview step

If you're mid-payroll, try navigating to the payroll preview screen without submitting. If the preview loads but submission fails repeatedly, the issue is in the ACH submission pipeline specifically — not the full dashboard.

3. Verify employee access separately

Have an employee check their Gusto account via the Gusto Wallet or employee self-service portal. If employees can view their pay stubs but you can't process payroll, the issue is in the payroll submission layer, not the whole platform.

4. Check API integrations

If you connect Gusto to an accounting tool (QuickBooks, Xero) or time tracking system (TSheets, Homebase), check whether those sync requests are failing. Third-party sync failures often surface before the main dashboard shows issues.

---

The Problem With Vendor Status Pages

When Gusto has a problem, checking their status page is the natural instinct. The issue: Gusto's status page, like most vendor status pages, is updated manually — often 20–30 minutes after the incident starts.

Payroll is uniquely time-sensitive. If you're running payroll on a Wednesday for Friday direct deposits, a 2-hour window matters. An NACHA cutoff missed by minutes can delay employee payments by a full business day.

Statusfield detects Gusto degradations the moment they start — before the status page is updated, before you miss an ACH cutoff.

---

What to Do During a Gusto Outage

Immediate (first 5 minutes)

1. Check your payroll deadline — what is the ACH cutoff for this payroll run? If you're close to the cutoff and Gusto is unresponsive, call Gusto support immediately. Do not wait for the status page.
2. Do not retry payroll submissions — repeated submission attempts during a partial outage can cause double-processing. Submit once, then wait and confirm before trying again.
3. Screenshot the error — capture any error messages from Gusto to share with support. Specific error codes help Gusto triage faster.
4. Check your bank ACH cutoff separately — Gusto submits ACH files to your bank ahead of employee pay dates. If the issue is a delayed submission, your bank's cutoff time determines whether Friday deposits are still possible.

Communication (first 15 minutes)

• Alert your HR or finance team that Gusto is experiencing an issue.
• If you're within 24 hours of payday and payroll hasn't processed, send employees a proactive heads-up that you're aware of the issue and working to resolve it. Employees who don't see a pending deposit notification will be anxious.
• Do not tell employees their pay will be delayed unless Gusto confirms the ACH file was not submitted — Gusto sometimes processes the file successfully even when the dashboard shows errors.

Recovery

• After Gusto recovers, confirm that your payroll run is in "Submitted" or "Processing" status — not still in "Pending."
• Check that any time-off requests or benefit enrollment changes submitted during the outage window were saved.
• Audit any contractor payments that were pending — confirm they're in queue for the expected pay date.

---

Gusto Components and What Each Outage Looks Like

Gusto's platform has several independently operable layers:

Component	Impact when degraded
Payroll processing engine	Payroll runs can't be submitted or confirmed
ACH file submission	Direct deposits fail to reach employees' banks on time
Benefits administration	Enrollment changes, carrier syncs, or deductions not saving
Time tracking sync	Approved hours don't flow into payroll calculations
Employee self-service portal	Employees can't view pay stubs or update direct deposit info
Document generation	W-2s, 1099s, offer letters unavailable
API / integrations layer	Accounting tool and HRIS syncs fail

A benefits administration outage doesn't affect payroll submission. But an ACH outage during active payroll is a high-severity incident regardless of whether the dashboard appears functional.

---

Why DIY Monitoring Misses the Real Failure

A "can I log in to Gusto" health check sounds sufficient but misses the most common Gusto failure patterns:

• Dashboard loads, payroll submission fails — the web app can be fully functional while the ACH processing backend is degraded.
• ACH cutoffs are unforgiving — by the time you manually notice a submission failure, the NACHA cutoff window may have passed.
• Partial outages look like user error — a payroll that won't submit returns the same UI behavior whether the issue is a data validation error or an infrastructure failure.
• Benefits syncs fail silently — carrier sync failures don't always surface as errors in the Gusto UI.

Effective Gusto monitoring checks the actual payroll processing pipeline, not just web app reachability. That's what Statusfield does.

---

Monitor Gusto Before Payroll Fails

Statusfield monitors Gusto and 1,700+ other services continuously. When something degrades, you get alerted — not after you've missed an ACH cutoff.

3 monitors, 10 alerts/month, no credit card required.

---

FAQ

Is Gusto down right now?

Statusfield monitors Gusto continuously and will tell you before you miss a payroll deadline. If your payroll won't process or your dashboard is showing errors, check Statusfield for real-time status.

Why won't my Gusto payroll submit?

If no data changes were made on your end, a Gusto platform incident is the most likely cause. Do not retry submission repeatedly — call Gusto support directly if you're within 24 hours of payday, as the ACH cutoff window is unforgiving.

How long do Gusto outages last?

Most incidents resolve within 1 to 3 hours. ACH-related delays can sometimes extend beyond platform recovery due to banking cutoff constraints.

How do I get alerted when Gusto goes down?

Statusfield monitors Gusto continuously and fires alerts the moment it detects a degradation. Every plan starts with a free trial — no credit card required.