Check Outage History

Between approximately 19:11 and 19:23 UTC, a subset of Check API requests returned 5xx errors, which also intermittently impacted Console and Components. The errors occurred because a routine deployment introduced a new data value that application instances still running the previous version did not yet recognize; while the rollout was in progress, requests served by those older instances failed. Error rates returned to normal at 19:23 UTC once the deployment fully completed and all traffic was handled by the updated version. We are implementing safeguards, including updated data-migration and deployment practices plus additional automated review checks, to prevent similar issues in the future. No customer action is required, and the issue did not affect payment or payroll processing.

All instant payments scheduled for today have been successfully processed. If we have not contacted you via Slack or email, all your customers' employees were paid today.

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.

This issue has been resolved. This morning Check experienced a database overload from increased webhook traffic that spiked for a a period of time on the morning of 4/24, and surfaced as high latency and error count. The team identified the issue, resolved the immediate database load concerns and restored functionality. The Check engineering team will be following up promptly with a resolution to prevent recurrence.

We identified and resolved the cause of elevated latency and degraded performance. A newly enabled internal process for synchronizing tax filing data generated significantly higher database load than expected, impacting API response times from ~9:15am - 9:38am ET. The feature flag has been reverted and system performance has returned to normal.

All FedACH systems are operating normally again, as reported on the Fed's own status page here: https://www.frbservices.org/app/status/serviceStatus.do. We do not anticipate any further impact and all of our systems are operating normally. Marking this incident resolved.

From about 12:15am to 1:15am ET on Feb 16, users experienced elevated latencies and HTTP 5xx responses on payroll endpoints from unexpected contention caused by a routine database migration. Service indicators returned to normal around 1:15am. We will be analyzing the event to prevent recurrences.

The issue is now resolved and statuses are updated

This incident has been resolved.

Completed payment reporting was delayed by up to 3 hours this morning. We missed our reporting target and completed our last status updates at 11:20am ET. We have since made optimizations to prevent this delay. There was no impact to payments deliverability.

Retroactively resolved (resolved on Dec 15).

GET /payrolls/{id}/preview is 500ing in sandbox environments

This incident has been resolved. If your customer missed the payroll approval deadline as a result of this incident, our Support team is happy to assist with approving it after the deadline.

Document downloads in Console are operational following the resolution of increased error rates and latencies from the AWS us-east-1 region. The latest resolution time was 5:16am ET.

This incident has been resolved.

Confirming resolution of elevated API latency after monitoring.

The API Request Log is now up to date

All systems operational after monitoring overnight. We experienced service degradation on October 20, 2025 due to an AWS infrastructure outage affecting our us-east-1 region. Services and processing has returned to normal as of yesterday afternoon ET. No payments impacted.

This incident has been resolved.