Check Outage History
Check is up right nowCheck had 19 outages in the last 2 years totaling 537h 59m of downtime — averaging 0.8 incidents per month.
There were 19 Check outages since June 5, 2025 totaling 537h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.
Spikes in Check API Latency and Errors
Timeline · 3 updates
- 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.
Service degradation impacting Production and Sandbox
Timeline · 4 updates
- 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.
Delayed delivery of FedACH direct deposits
Timeline · 3 updates
- 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.
[RESOLVED] Payroll endpoints degraded for one hour starting 12:15am ET
Timeline · 1 update
- 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.
Instant payment status reporting delayed
Timeline · 2 updates
- 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
Elevated API latency
Timeline · 3 updates
- 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.
Delayed payment completion reporting [resolved]
Timeline · 1 update
- 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.
Elevated 500s on POST /bank_accounts
Timeline · 3 updates
- 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).
Sandbox Payroll Preview Down
Timeline · 1 update
- resolved Nov 27, 2025, 06:56 PM UTC
GET /payrolls/{id}/preview is 500ing in sandbox environments
Payroll approval blocked for payrolls with $0 liabilities
Timeline · 2 updates
- 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.
Issues downloading some documents in Console
Timeline · 2 updates
- 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.
Console sandbox unavailability
Timeline · 2 updates
- 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.
High API Latency and Error Rates
Timeline · 2 updates
- 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.
API Request Logs Degraded
Timeline · 3 updates
- 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
AWS outage impacts
Timeline · 6 updates
- 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.
Sandbox Outage
Timeline · 3 updates
- 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.
Increased Errors on Payroll Endpoint
Timeline · 2 updates
- identified Jun 06, 2025, 01:22 PM UTC
We have identified an issue causing elevated rates of 500 errors on the payroll endpoint. A fix for this issue is currently being deployed.
- resolved Jun 06, 2025, 02:12 PM UTC
The scope of impact was limited to deleting payrolls. A fix is live in production and we are seeing complete recovery.
500s on payroll preview
Timeline · 3 updates
- identified Jun 05, 2025, 05:14 PM UTC
We have identified an issue causing elevated rates of 500 errors on payroll preview. A fix for this issue is currently being deployed.
- monitoring Jun 05, 2025, 05:55 PM UTC
A fix has been deployed, and we are monitoring the results.
- resolved Jun 05, 2025, 07:00 PM UTC
This incident has been resolved.