Check Outage History
Check is up right nowPingoru has recorded 51 incidents for Check: 23 in the last 12 months and 4 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 3 | 18 of 720 (3%) |
| May 2026 | 1 | 5 of 744 (1%) |
| June 2026 | 3 | 14 of 720 (2%) |
| July 2026 | 1 | 5 of 744 (1%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 2 | 24 of 720 (3%) |
| October 2026 | 1 | 45 of 523 (9%) |
Incidents, newest first
Minor October 20, 2026 API Request Log Search Indexing Delayed 1d 20h API, Console
Started Oct 20, 2026, 03:06 PM UTC· resolved Oct 22, 2026, 12:00 PM UTC
- investigating Oct 20, 2026, 03:06 PM UTC
API request logs search are experiencing a delay in processing such that they aren't appearing in the developer tab in Console in a timely manner. Logs are not lost and we're working with our vendor to understand the root cause. We'll report back here with more details as we have them.
- investigating Oct 20, 2026, 04:34 PM UTC
We are continuing to work with our vendor to identifying the exact cause of the delay. As soon as that is resolved, we're ready to push through all backlogged API request logs.
- resolved Oct 22, 2026, 12:00 PM UTC
Our vendor has identified and resolved the issue on their end and logs are flowing normally again.
Minor September 9, 2026 Usage API unavailable 45m API, Console
Started Sep 09, 2026, 06:31 PM UTC· resolved Sep 09, 2026, 07:16 PM UTC
- identified Sep 09, 2026, 06:31 PM UTC
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.
- monitoring Sep 09, 2026, 06:50 PM UTC
We are seeing Usage API now operational after being unavailable from 1:00pm–2:40pm ET. No records were impacted. We are now monitoring.
- resolved Sep 09, 2026, 07:16 PM UTC
This incident has been resolved. Usage API continues operating as normal.
Notice September 4, 2026 Delayed Payments 9/4 22h 43m Payments
Started Sep 04, 2026, 03:09 PM UTC· resolved Sep 05, 2026, 01:53 PM UTC
- monitoring Sep 04, 2026, 03:09 PM UTC
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.
- resolved Sep 05, 2026, 01:53 PM UTC
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.
Notice July 31, 2026 Delayed Payments 7/31 5h 19m Payments
Started Jul 31, 2026, 01:30 PM UTC· resolved Jul 31, 2026, 06:50 PM UTC
- investigating Jul 31, 2026, 01:30 PM UTC
We are aware of some payees not receiving direct deposits this morning and are actively investigating.
- investigating Jul 31, 2026, 01:46 PM UTC
So far we've seen no evidence of failed transactions. We are currently investigating what appears to be delays with specific receiving institutions.
- monitoring Jul 31, 2026, 03:20 PM UTC
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.
- monitoring Jul 31, 2026, 03:39 PM UTC
UMB has confirmed they are experiencing settlement delays. They have not confirmed expected settlement timelines at this point.
- monitoring Jul 31, 2026, 04:17 PM UTC
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.
- resolved Jul 31, 2026, 06:50 PM UTC
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.
Notice June 22, 2026 Spike in Check API 5xx Errors 1h 32m API, Console, Onboard
Started Jun 22, 2026, 07:24 PM UTC· resolved Jun 22, 2026, 08:56 PM UTC
- investigating Jun 22, 2026, 07:24 PM UTC
We have identified an increased number of 5xx errors in Check API, which is also impacting Console usage. Investigation is in progress.
- monitoring Jun 22, 2026, 07:29 PM UTC
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.
- resolved Jun 22, 2026, 08:56 PM UTC
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.
Minor June 18, 2026 Delayed Employee Payments 7h 47m Payments
Started Jun 18, 2026, 02:38 PM UTC· resolved Jun 18, 2026, 10:25 PM UTC
- investigating Jun 18, 2026, 02:38 PM UTC
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.
- identified Jun 18, 2026, 03:21 PM UTC
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.
- identified Jun 18, 2026, 03:22 PM UTC
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.
- identified Jun 18, 2026, 03:52 PM UTC
Our payment processor has developed and is deploying a fix. We will provide another update at 12:30pm ET.
- monitoring Jun 18, 2026, 04:32 PM UTC
Our payment processor has deployed a fix and we are working through the backlog of delayed payments.
- monitoring Jun 18, 2026, 06:09 PM UTC
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.
- resolved Jun 18, 2026, 10:25 PM UTC
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.
Major June 6, 2026 Payroll preview and approval errors 4h 25m API
Started Jun 06, 2026, 08:41 PM UTC· resolved Jun 07, 2026, 01:06 AM UTC
- investigating Jun 06, 2026, 08:41 PM UTC
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.
- identified Jun 06, 2026, 08:56 PM UTC
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.
- identified Jun 06, 2026, 09:51 PM UTC
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.
- monitoring Jun 06, 2026, 10:51 PM UTC
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.
- resolved Jun 07, 2026, 01:06 AM UTC
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.
Notice May 27, 2026 API 403 errors on May 26 5h
Started May 27, 2026, 12:04 AM UTC· resolved May 27, 2026, 05:04 AM UTC
- resolved May 27, 2026, 05:47 PM UTC
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.
Major April 28, 2026 Degraded API Availability + Performance 7h 24m API, Console
Started Apr 28, 2026, 08:37 AM UTC· resolved Apr 28, 2026, 04:01 PM UTC
- investigating Apr 28, 2026, 08:37 AM UTC
We've identified an event impacting AVI availability and performance inconsistency. Investigation in progress.
- monitoring Apr 28, 2026, 08:45 AM UTC
The system is recovering. We are actively monitoring to ensure it remains recovered. Root cause analysis to follow.
- resolved Apr 28, 2026, 04:01 PM UTC
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.
Minor April 24, 2026 Spikes in Check API Latency and Errors 7h 36m API, Console
Started Apr 24, 2026, 01:33 PM UTC· resolved Apr 24, 2026, 09:10 PM UTC
- investigating Apr 24, 2026, 01:33 PM UTC
We identified spikes in API latency and errors. Investigation in progress.
- investigating Apr 24, 2026, 01:36 PM UTC
System is recovering. We are still investigating this issue to understand root cause and therefore prevent recurrence, as well as assessing potential impact.
- resolved Apr 24, 2026, 09:10 PM UTC
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.
Critical April 9, 2026 Service degradation impacting Production and Sandbox 3h 19m API, Console, Onboard
Started Apr 09, 2026, 01:25 PM UTC· resolved Apr 09, 2026, 04:45 PM UTC
- investigating Apr 09, 2026, 01:25 PM UTC
We are currently investigating this issue with the highest levels of urgency.
- investigating Apr 09, 2026, 01:26 PM UTC
We are continuing to investigate this issue.
- monitoring Apr 09, 2026, 01:42 PM UTC
A fix has been implemented and we are actively monitoring our systems.
- resolved Apr 09, 2026, 04:45 PM UTC
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.
Major March 3, 2026 Delayed delivery of FedACH direct deposits 8h 43m Payments
Started Mar 03, 2026, 11:41 AM UTC· resolved Mar 03, 2026, 08:25 PM UTC
- investigating Mar 03, 2026, 11:41 AM UTC
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.
- monitoring Mar 03, 2026, 12:52 PM UTC
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.
- resolved Mar 03, 2026, 08:25 PM UTC
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.
Notice January 16, 2026 [RESOLVED] Payroll endpoints degraded for one hour starting 12:15am ET –
Started Jan 16, 2026, 05:00 AM UTC· resolved Jan 16, 2026, 05:00 AM UTC
- resolved Jan 16, 2026, 01:01 PM UTC
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.
Notice January 7, 2026 Instant payment status reporting delayed 35m Payments
Started Jan 07, 2026, 04:18 PM UTC· resolved Jan 07, 2026, 04:53 PM UTC
- investigating Jan 07, 2026, 04:18 PM UTC
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
- resolved Jan 07, 2026, 04:53 PM UTC
The issue is now resolved and statuses are updated
Minor January 5, 2026 Elevated API latency 1h 45m API, Console, Onboard
Started Jan 05, 2026, 01:38 PM UTC· resolved Jan 05, 2026, 03:23 PM UTC
- identified Jan 05, 2026, 01:38 PM UTC
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.
- monitoring Jan 05, 2026, 01:48 PM UTC
Latency has stabilized. We'll continue to monitor
- resolved Jan 05, 2026, 03:23 PM UTC
This incident has been resolved.
Notice January 2, 2026 Delayed payment completion reporting [resolved] – Payments
Started Jan 02, 2026, 04:54 PM UTC· resolved Jan 02, 2026, 04:54 PM UTC
- resolved Jan 02, 2026, 04:54 PM UTC
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.
Major December 15, 2025 Elevated 500s on POST /bank_accounts 18d 1h API, Onboard
Started Dec 15, 2025, 03:39 PM UTC· resolved Jan 02, 2026, 04:53 PM UTC
- identified Dec 15, 2025, 03:39 PM UTC
We are seeing a high failure rate when creating bank accounts. We have identified the root cause and a code-fix is underway.
- monitoring Dec 15, 2025, 04:34 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 02, 2026, 04:53 PM UTC
Retroactively resolved (resolved on Dec 15).
Notice November 27, 2025 Sandbox Payroll Preview Down –
Started Nov 27, 2025, 10:30 AM UTC· resolved Nov 27, 2025, 10:30 AM UTC
- resolved Nov 27, 2025, 06:56 PM UTC
GET /payrolls/{id}/preview is 500ing in sandbox environments
Notice October 29, 2025 Payroll approval blocked for payrolls with $0 liabilities 13m API
Started Oct 29, 2025, 11:53 PM UTC· resolved Oct 30, 2025, 12:06 AM UTC
- identified Oct 29, 2025, 11:53 PM UTC
A fix is being deployed. Reach out to Support if you need assistance to approve a payroll after the deadline.
- resolved Oct 30, 2025, 12:06 AM UTC
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.
Minor October 28, 2025 Issues downloading some documents in Console 14h 51m Console
Started Oct 28, 2025, 10:51 PM UTC· resolved Oct 29, 2025, 01:43 PM UTC
- identified Oct 28, 2025, 10:51 PM UTC
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.
- resolved Oct 29, 2025, 01:43 PM UTC
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.
Major October 27, 2025 Console sandbox unavailability 2h 15m Console
Started Oct 27, 2025, 05:30 PM UTC· resolved Oct 27, 2025, 07:45 PM UTC
- identified Oct 27, 2025, 05:30 PM UTC
Console sandbox mode is currently unavailable. We have identified the issue and are working to resolve.
- resolved Oct 27, 2025, 08:18 PM UTC
This incident has been resolved.
Minor October 27, 2025 High API Latency and Error Rates 5h 7m API, Console, Onboard
Started Oct 27, 2025, 03:07 PM UTC· resolved Oct 27, 2025, 08:15 PM UTC
- monitoring Oct 27, 2025, 03:07 PM UTC
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.
- resolved Oct 27, 2025, 08:15 PM UTC
Confirming resolution of elevated API latency after monitoring.
Minor October 23, 2025 API Request Logs Degraded 1d 2h API, Console
Started Oct 23, 2025, 08:23 PM UTC· resolved Oct 24, 2025, 10:35 PM UTC
- investigating Oct 23, 2025, 08:23 PM UTC
Since 10/22 10:14a ET, new requests have not been added to the API Requests Log and are unavailable at /logs.
- identified Oct 24, 2025, 02:38 AM UTC
The underlying issue was resolved and the missing request logs are in the process of being backfilled.
- resolved Oct 24, 2025, 10:35 PM UTC
The API Request Log is now up to date
Minor October 20, 2025 AWS outage impacts 23h 50m API, Console, Onboard, Payments
Started Oct 20, 2025, 02:38 PM UTC· resolved Oct 21, 2025, 02:28 PM UTC
- investigating Oct 20, 2025, 02:38 PM UTC
We're investigating any impacts from the AWS outage this morning. We identified that some completed payments are incorrectly showing as “processing.” We’re actively correcting the affected statuses. There is no impact to the delivery of payments.
- investigating Oct 20, 2025, 03:26 PM UTC
All impacted payments's statuses are now up to date. We're still investigating for other impacts.
- investigating Oct 20, 2025, 05:07 PM UTC
Bank account creation is unavailable from the API, console and onboard. Updates in pending payrolls are delayed.
- investigating Oct 20, 2025, 08:11 PM UTC
Bank account creation is operational in API, console and onboard. Pending payroll updates have resumed. Payment status updates remain delayed.
- monitoring Oct 20, 2025, 08:52 PM UTC
All functionality is operating as normal. We're still monitoring for any remaining degradation from the AWS outage
- resolved Oct 21, 2025, 02:28 PM UTC
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.
Major August 19, 2025 Sandbox Outage 12m API, Console, Onboard
Started Aug 19, 2025, 07:07 PM UTC· resolved Aug 19, 2025, 07:20 PM UTC
- investigating Aug 19, 2025, 07:07 PM UTC
We are currently experiencing an outage with the Sandbox environment. Our team is actively investigating the cause and working to restore service as quickly as possible. We will provide updates here as soon as more information becomes available.
- monitoring Aug 19, 2025, 07:12 PM UTC
A fix has been implemented and we are monitoring the results
- resolved Aug 19, 2025, 07:20 PM UTC
This incident has been resolved.