Is Check down?

The Usage API is currently unavailable, affecting the API and Console billing reports. We have identified the root cause and a fix is being implemented.

We are seeing Usage API now operational after being unavailable from 1:00pm–2:40pm ET. No records were impacted. We are now monitoring.

This incident has been resolved. Usage API continues operating as normal.

We've received reports of employees not receiving deposits this morning at The Bancorp Bank, the underlying bank for providers such as Chime. We reviewed the affected transactions and found no failed or delayed processing on Check's side. All reported payments were sent on time and confirmed completed by our payment processor. If you receive reports for missing deposits for employees not using The Bancorp Bank, please alert Check Support. Affected employees should contact their bank directly for timing on funds availability. We're continuing to monitor and will share updates as they become available.

Check has completed its review of the delayed deposits reported on 9/4 for employees banking with The Bancorp Bank (the underlying bank for providers such as Chime). All affected payments were sent on time and confirmed completed by our payment processor. The delay occurred at The Bancorp Bank, and funds should now be available. If an employee still hasn't received a deposit, they should contact their bank directly for timing on funds availability. Please continue to report any missing deposits for employees not banking with The Bancorp Bank to Check Support.

We are aware of some payees not receiving direct deposits this morning and are actively investigating.

So far we've seen no evidence of failed transactions.  We are currently investigating what appears to be delays with specific receiving institutions.

We have not seen any evidence of failed transactions and have traced the delays to two specific receiving banks — UMB and The Bancorp Bank, N.A. Many consumer banking providers (e.g., Chime uses Bancorp; Fidelity uses UMB) sit on top of these banks, which is why impact appears spread across multiple employers and "banks". What we know: * We have reviewed the affected transactions and have found no evidence of failed or delayed processing on Check’s side. All reported payments were sent on time and are confirmed as completed by our payment processor. * The delays appear to be occurring after the funds reached the receiving banks and before they are made available in employee accounts. * Employees whose accounts are not serviced by UMB or The Bancorp Bank appear to be unaffected. We have seen third-party reports of similar delays affecting non-Check users, but neither receiving bank has published an official outage incident. At this time, affected employees should contact their bank directly for additional information about when the funds will be made available. We will continue monitoring the situation and will share additional updates as they become available.

UMB has confirmed they are experiencing settlement delays. They have not confirmed expected settlement timelines at this point.

Deposits to UMB accounts are beginning to post, with multiple confirmed cases. Chime has confirmed they are experiencing delays and will notify affected users once the deposits post.

We've received reports that impacted banks have been successfully posting deposits. If an employee has not received their funds at this point, we advise them to contact their bank. If there are outstanding deposit issues please reach out to Check's Support team with the impacted employee IDs.

We have identified an increased number of 5xx errors in Check API, which is also impacting Console usage. Investigation is in progress.

The system has recovered and is now operating normally. The issue was transient and related to an in-progress deployment. We are continuing to monitor the system closely and are conducting a root cause analysis to better understand the issue and prevent similar occurrences in the future.

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.