All Systems Operational

API Operational
90 days ago
99.92 % uptime
Today
Console Operational
90 days ago
99.98 % uptime
Today
Onboard Operational
90 days ago
99.98 % uptime
Today
Payments Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Jun 9, 2026

No incidents reported today.

Jun 8, 2026

No incidents reported.

Jun 7, 2026
Resolved - Resolved: The database fix has been fully applied and verified. Payroll preview and approval are operating normally across all environments. This incident has been resolved.

Root cause: A database limit was reached that prevented payroll calculations from being processed. We have applied a permanent fix and are adding monitoring to prevent recurrence.

We apologize for the disruption and thank you for your patience.

Jun 7, 01:06 UTC
Monitoring - Update: The database fix has been successfully applied to production. Payroll preview and approval are now operational and we are no longer seeing errors. We will continue monitoring to confirm stability before fully resolving this incident.
Jun 6, 22:51 UTC
Update - Update: The database fix has been successfully applied to our sandbox environment. The fix is now in progress on production. Estimated time to resolution: 60-90 minutes. We will update when complete.

Payroll preview and approval remain impacted in production. Sandbox payroll operations have been restored.

Jun 6, 21:51 UTC
Identified - Update: We have confirmed the root cause and are now applying a database fix. We are rolling the change through sandbox first before applying to production. Due to the size of the change, we are revising our estimated time to resolution to several hours. We will continue to provide updates as the fix progresses.

Payroll preview and approval remain impacted across all payroll types in production. These endpoints will be unavailable in sandbox during application of our database fix. Other endpoints are not affected.

Jun 6, 20:56 UTC
Investigating - We are investigating an issue impacting payroll preview and approval. Requests to preview or approve payrolls are returning errors. This affects all payroll types. Other endpoints are not impacted.

Our team has identified a database capacity issue as the root cause and is implementing a permanent fix. Estimated time to resolution: within 90 minutes.

Jun 6, 20:41 UTC
Jun 6, 2026
Jun 5, 2026

No incidents reported.

Jun 4, 2026

No incidents reported.

Jun 3, 2026

No incidents reported.

Jun 2, 2026

No incidents reported.

Jun 1, 2026

No incidents reported.

May 31, 2026

No incidents reported.

May 30, 2026

No incidents reported.

May 29, 2026

No incidents reported.

May 28, 2026

No incidents reported.

May 27, 2026
Resolved - On the evening of Tuesday, May 26, 2026, a code change caused a subset of API key requests to incorrectly return 403 Forbidden. We detected the issue after a partner report, reverted the change, and restored service within approximately 5 hours. We are deeply sorry for the disruption. This explains what happened and what we are doing to prevent recurrence.

Impact

The issue was live from Tuesday, May 26 at 8:04 PM ET to Wednesday, May 27 at 1:27 AM ET, a window of 5 hours and 23 minutes. During that time, API requests that create or update resources (POST and PATCH) returned 403 Forbidden for a subset of partners: partners who had their API key associated with a Console user of the roles standard or cost owner. Most partners were not affected. Read traffic (GET) and the underlying data were not affected; no records were created, modified, or lost as a result of this bug, and approved payrolls and scheduled payments continued to process normally.

Root cause

We deployed an authorization refactoring on our write endpoints. The change contained a bug that caused the new check to incorrectly reject legitimate write requests for some partners if their API key was tied to a Console user with a role of either standard or cost owner. These unintended errors were mixed with legitimately rejected traffic, which affected our detection time. The change was reverted. No further action is required from partners, and any request that failed with a 403 during the window can be viewed in API Logs and safely retried.

What we are doing differently

First, we will reintroduce the change behind a safer rollout, re-landing the additional write-path authorization check with additional automated tests for this API key provisioning setup and in more incremental stages. Second, we will tighten our deploy guardrails by restricting changes affecting authentication or authorization to adjusted hours, along with implementing more robust post-deploy monitoring for faster response.

If you believe you saw a related issue outside the window above, or have questions about this incident, please reach out to us and reference this note.

May 27, 00:04 UTC
May 26, 2026

No incidents reported.