Sep <var data-var='date'> 9</var>, <var data-var='time'>19:16</var> UTC Resolved - This incident has been resolved. Usage API continues operating as normal. Sep <var data-var='date'> 9</var>, <var data-var='time'>18:50</var> UTC Monitoring - We are seeing Usage API now operational after being unavailable from 1:00pm–2:40pm ET. No records were impacted. We are now monitoring. Sep <var data-var='date'> 9</var>, <var data-var='time'>18:31</var> UTC Identified - 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.

Usage API unavailable

Sep <var data-var='date'> 6</var>, <var data-var='time'>13:48</var> UTC Completed - The scheduled maintenance has been completed. Sep <var data-var='date'> 6</var>, <var data-var='time'>13:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>27</var>, <var data-var='time'>21:28</var> UTC Update - We will perform planned database maintenance. Webhook deliveries attempted during the interruption will be retried automatically and money movement will not be affected. Aug <var data-var='date'>27</var>, <var data-var='time'>21:19</var> UTC Update - We will be undergoing scheduled maintenance during this time. Aug <var data-var='date'>27</var>, <var data-var='time'>21:18</var> UTC Update - We will be undergoing scheduled maintenance during this time. Aug <var data-var='date'>27</var>, <var data-var='time'>21:18</var> UTC Scheduled - We will perform planned database maintenance. Webhook deliveries attempted during the interruption will be retried automatically and money movement will not be affected.

Planned Database Maintenance

Sep <var data-var='date'> 5</var>, <var data-var='time'>13:53</var> UTC Resolved - 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. Sep <var data-var='date'> 4</var>, <var data-var='time'>15:09</var> UTC Monitoring - 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.

Delayed Payments 9/4

Jul <var data-var='date'>31</var>, <var data-var='time'>18:50</var> UTC Resolved - 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. Jul <var data-var='date'>31</var>, <var data-var='time'>16:17</var> UTC Update - 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. Jul <var data-var='date'>31</var>, <var data-var='time'>15:39</var> UTC Update - UMB has confirmed they are experiencing settlement delays. They have not confirmed expected settlement timelines at this point. Jul <var data-var='date'>31</var>, <var data-var='time'>15:20</var> UTC Monitoring - 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. Jul <var data-var='date'>31</var>, <var data-var='time'>13:46</var> UTC Update - So far we've seen no evidence of failed transactions.  We are currently investigating what appears to be delays with specific receiving institutions. Jul <var data-var='date'>31</var>, <var data-var='time'>13:30</var> UTC Investigating - We are aware of some payees not receiving direct deposits this morning and are actively investigating.

Delayed Payments 7/31

Jun <var data-var='date'>22</var>, <var data-var='time'>20:56</var> UTC Resolved - 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. Jun <var data-var='date'>22</var>, <var data-var='time'>19:29</var> UTC Monitoring - 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. Jun <var data-var='date'>22</var>, <var data-var='time'>19:24</var> UTC Investigating - We have identified an increased number of 5xx errors in Check API, which is also impacting Console usage. Investigation is in progress.

Spike in Check API 5xx Errors

Jun <var data-var='date'>18</var>, <var data-var='time'>22:25</var> UTC Resolved - 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. Jun <var data-var='date'>18</var>, <var data-var='time'>18:09</var> UTC Update - We have rescheduled all delayed employee payments due today. We are actively working with our payments processor to ensure timely processing of these rescheduled instant payments. Most are completed, and a minority of those due today are still impacted. Funding payments have not been impacted. Jun <var data-var='date'>18</var>, <var data-var='time'>16:32</var> UTC Monitoring - Our payment processor has deployed a fix and we are working through the backlog of delayed payments. Jun <var data-var='date'>18</var>, <var data-var='time'>15:52</var> UTC Update - Our payment processor has developed and is deploying a fix. We will provide another update at 12:30pm ET. Jun <var data-var='date'>18</var>, <var data-var='time'>15:22</var> UTC Update - Our payment processor has identified the issue leading to delayed payments and is working on a fix. We will provide another update at 11:45am ET. Jun <var data-var='date'>18</var>, <var data-var='time'>15:21</var> UTC Identified - Our payment processor has identified the issue leading to delayed payments and is working on a fix. We will provide another update at 11:45am ET. Jun <var data-var='date'>18</var>, <var data-var='time'>14:38</var> UTC Investigating - Delayed employee payments were identified this morning and are under active investigation. Many payments are processing, though arriving later than expected, and the total number of outstanding payments is actively decreasing. Work with our banking partner is ongoing, and we expect to work through the remainder of the day to ensure all affected payments are processed. Note: This only impacts payments that were funded and scheduled to land today. Please confirm any reported late payments are included in a payroll dated for today with no funding issues before escalating. No support outreach is needed to ensure payments are included in our efforts.

Delayed Employee Payments

Jun <var data-var='date'> 7</var>, <var data-var='time'>01:06</var> UTC 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 <var data-var='date'> 6</var>, <var data-var='time'>22:51</var> 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 <var data-var='date'> 6</var>, <var data-var='time'>21:51</var> 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 <var data-var='date'> 6</var>, <var data-var='time'>20:56</var> 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 <var data-var='date'> 6</var>, <var data-var='time'>20:41</var> 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.

Payroll preview and approval errors

May <var data-var='date'>27</var>, <var data-var='time'>00:04</var> UTC 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.

API 403 errors on May 26

May <var data-var='date'>17</var>, <var data-var='time'>13:30</var> UTC Completed - The scheduled maintenance has been completed. May <var data-var='date'>17</var>, <var data-var='time'>13:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'>11</var>, <var data-var='time'>13:31</var> UTC Scheduled - We will be undergoing scheduled maintenance to upgrade our API infrastructure on 5/17/26 @ 9:00 AM ET. From 9:00–9:30 AM ET, we expect none to up to 5 minutes of downtime for Check API, Console, and Components.

[Production] Maintenance window on Sunday, May 17th

May <var data-var='date'> 3</var>, <var data-var='time'>05:30</var> UTC Completed - The scheduled maintenance has been completed. May <var data-var='date'> 3</var>, <var data-var='time'>05:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'>27</var>, <var data-var='time'>23:53</var> UTC Scheduled - We will be undergoing scheduled maintenance to update our API infrastructure on 4/3/26 @ 1:00 AM EDT. During a 30 minute window from 1 AM EDT to 1:30 AM EDT, we expect 5 minutes of downtime for Check API, Console, and Components.

[Production] Planned downtime on Sunday, May 3rd for maintenance

Apr <var data-var='date'>28</var>, <var data-var='time'>16:01</var> UTC Resolved - 4/28 — Resolution Update and RCA Impact and duration: From approximately 1:05 AM PT to 1:44 AM PT on Tuesday, April 28 (~40 minutes), API endpoints across the platform returned elevated error rates and Console pages were intermittently unavailable. Health checks returned to green at 1:44 AM PT and the system has been stable since. What happened: Two scheduled background jobs ran simultaneously in the early-morning window and pushed our cache layer past its memory limit. Once the cache filled, normal cache writes began failing globally, which surfaced as the broad API degradation. Today's root cause is distinct from the SEV-2 on Friday, 4/24, which was driven by an inbound webhook volume spike from a banking partner. We traced today's failures directly to cache memory pressure, not webhook volume. Going forward: We are taking immediate steps to prevent recurrence, including reducing the load these scheduled jobs place on the cache layer and improving how the system handles cache pressure so it degrades gracefully rather than producing errors. We are also strengthening monitoring on cache health and related signals so this class of issue is caught before it impacts API availability. Apr <var data-var='date'>28</var>, <var data-var='time'>08:45</var> UTC Monitoring - The system is recovering. We are actively monitoring to ensure it remains recovered. Root cause analysis to follow. Apr <var data-var='date'>28</var>, <var data-var='time'>08:37</var> UTC Investigating - We've identified an event impacting AVI availability and performance inconsistency. Investigation in progress.

Degraded API Availability + Performance

Apr <var data-var='date'>24</var>, <var data-var='time'>21:10</var> UTC Resolved - 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. Apr <var data-var='date'>24</var>, <var data-var='time'>13:36</var> UTC Update - System is recovering. We are still investigating this issue to understand root cause and therefore prevent recurrence, as well as assessing potential impact. Apr <var data-var='date'>24</var>, <var data-var='time'>13:33</var> UTC Investigating - We identified spikes in API latency and errors. Investigation in progress.

Spikes in Check API Latency and Errors

Apr <var data-var='date'> 9</var>, <var data-var='time'>16:45</var> UTC Resolved - 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. Apr <var data-var='date'> 9</var>, <var data-var='time'>13:42</var> UTC Monitoring - A fix has been implemented and we are actively monitoring our systems. Apr <var data-var='date'> 9</var>, <var data-var='time'>13:26</var> UTC Update - We are continuing to investigate this issue. Apr <var data-var='date'> 9</var>, <var data-var='time'>13:25</var> UTC Investigating - We are currently investigating this issue with the highest levels of urgency.

Service degradation impacting Production and Sandbox

Mar <var data-var='date'> 3</var>, <var data-var='time'>20:25</var> UTC Resolved - 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. Mar <var data-var='date'> 3</var>, <var data-var='time'>12:52</var> UTC Monitoring - As of 7:30am ET the FedACH system has successfully distributed all files containing Check's overnight payments to the receiving banks. These files were distributed by FedACH approximately 8 hours later than normal, at 7:30am ET today vs typical distribution at 11:30pm ET last night. This is likely to result in some banks reflecting direct deposits in recipient bank accounts later than normal. We do not have visibility or control into when each individual receiving bank will reflect these payments in the recipients' accounts as each bank individually recovers from this FedACH processing delay. Mar <var data-var='date'> 3</var>, <var data-var='time'>11:41</var> UTC Investigating - Overnight, the Federal Reserve reported delays processing and delivering ACH payment files through FedACH. As a result, some ACH payments (including employee direct deposits) may post later than expected today, and inbound ACH transfers/returns may also be delayed. The exact impact is not yet clear, but we believe that all direct deposits landing this morning may be impacted. We’re actively monitoring the Fed’s updates and our processing/settlement flows. Until the Federal Reserve resolves the underlying issue, there isn’t a lever we can pull to speed up delivery. We will follow-up as soon as we know more, no later than 9am ET. You can monitor the status of FedACH directly at: https://frbservices.org/app/status/outage.do?oId=145787.

Delayed delivery of FedACH direct deposits

Jan <var data-var='date'>16</var>, <var data-var='time'>05:00</var> UTC 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.

[RESOLVED] Payroll endpoints degraded for one hour starting 12:15am ET

Jan <var data-var='date'> 7</var>, <var data-var='time'>16:53</var> UTC Resolved - The issue is now resolved and statuses are updated Jan <var data-var='date'> 7</var>, <var data-var='time'>16:18</var> UTC Investigating - We're investigating an issue where Instant Payment transactions from this morning are still displaying as Pending. We've confirmed that this purely a reporting issue and all payments have been sent

Instant payment status reporting delayed

Jan <var data-var='date'> 5</var>, <var data-var='time'>15:23</var> UTC Resolved - This incident has been resolved. Jan <var data-var='date'> 5</var>, <var data-var='time'>13:48</var> UTC Monitoring - Latency has stabilized. We'll continue to monitor Jan <var data-var='date'> 5</var>, <var data-var='time'>13:38</var> UTC Identified - Since 11pm ET last night (Jan 4th) the API has had elevated latency across all resources. We've identified the issue and are implementing a fix.

Elevated API latency

Jan <var data-var='date'> 2</var>, <var data-var='time'>16:54</var> UTC 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.

Delayed payment completion reporting [resolved]

Jan <var data-var='date'> 2</var>, <var data-var='time'>16:53</var> UTC Resolved - Retroactively resolved (resolved on Dec 15). Dec <var data-var='date'>15</var>, <var data-var='time'>16:34</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Dec <var data-var='date'>15</var>, <var data-var='time'>15:39</var> UTC Identified - We are seeing a high failure rate when creating bank accounts. We have identified the root cause and a code-fix is underway.

Elevated 500s on POST /bank_accounts

Dec <var data-var='date'>14</var>, <var data-var='time'>18:18</var> UTC Completed - The scheduled maintenance has been completed. Dec <var data-var='date'>14</var>, <var data-var='time'>17:48</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Dec <var data-var='date'> 9</var>, <var data-var='time'>17:52</var> UTC Scheduled - We will be undergoing scheduled maintenance to update our API infrastructure on 12/14/25 @ 11am EST. During a 30 minute window from 11am EST to 11:30am EST, we expect 5 minutes of downtime for Check API, Console, and Components.

[Production/Sandbox] Planned downtime on Sunday, December 14th for maintenance

Nov <var data-var='date'>27</var>, <var data-var='time'>10:30</var> UTC Resolved - GET /payrolls/{id}/preview is 500ing in sandbox environments

Sandbox Payroll Preview Down

Oct <var data-var='date'>30</var>, <var data-var='time'>00:06</var> UTC Resolved - 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. Oct <var data-var='date'>29</var>, <var data-var='time'>23:53</var> UTC Identified - A fix is being deployed. Reach out to Support if you need assistance to approve a payroll after the deadline.

Payroll approval blocked for payrolls with $0 liabilities

Oct <var data-var='date'>29</var>, <var data-var='time'>13:43</var> UTC Resolved - 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. Oct <var data-var='date'>28</var>, <var data-var='time'>22:51</var> UTC Identified - Attempts to download a subset of documents in Console are returning errors. The root cause has been identified and will be resolved upon working through a deployment issue with a vendor.

Issues downloading some documents in Console

Oct <var data-var='date'>27</var>, <var data-var='time'>20:15</var> UTC Resolved - Confirming resolution of elevated API latency after monitoring. Oct <var data-var='date'>27</var>, <var data-var='time'>15:07</var> UTC Monitoring - From 4:15a to 10:15a, performance across our API, console and onboard was degraded. The issue was resolved and we're continuing to monitor.

High API Latency and Error Rates

Oct <var data-var='date'>27</var>, <var data-var='time'>19:45</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'>27</var>, <var data-var='time'>17:30</var> UTC Identified - Console sandbox mode is currently unavailable. We have identified the issue and are working to resolve.

Is Check down?

Check status is UP

Lastest published events

Usage API unavailable

Planned Database Maintenance

Delayed Payments 9/4

Check Services, Components and Regions

Recent Check events

Usage API unavailable

Planned Database Maintenance

Delayed Payments 9/4

Delayed Payments 7/31

Spike in Check API 5xx Errors

Delayed Employee Payments