Dwolla had 19 outages in the last 2 years totaling 174h 35m of downtime — averaging 0.8 incidents per month.
There were 19 Dwolla outages since July 29, 2025 totaling 174h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.
We experienced an issue affecting webhook delivery and dashboard login functionality in the Sandbox environment between 12:47pm CT and 4:44pm CT. This issue is now resolved.
We are currently investigating elevated error rates (HTTP 500) affecting requests to the Customers, Funding Sources, and Mass Payments API endpoints. Some requests to these endpoints may fail or time out. Our engineering team is actively investigating. We will provide an update within as soon as we have more information.
A fix has been deployed and error rates are returning to normal across the affected endpoints and the Dashboard. We are monitoring to confirm full recovery.
This issue is resolved.
We are currently investigating an issue causing delays or failures in sending operational email notifications to end-users. Please be assured that core API functionality, ACH transfer processing, and the Dwolla Dashboard are fully operational. Transfers are not impacted; only the automated email notifications sent to your end-users are currently delayed. We are working to resolve this as quickly as possible.
A fix has been implemented, and operational notifications to end-users are beginning to send normally. We are currently monitoring the delivery queues as they process the backlog of delayed emails. End-users should start receiving their delayed notification emails shortly. We will provide a final update once the queue is fully cleared.
The issue affecting the dashboard display for Operational Notification statuses has been fully resolved. All delivery statuses within the Dwolla Dashboard are now updating in real-time and accurately reflect historical deliveries. Thank you for your patience.
We experienced a brief service disruption in our Production environment between 3:14 PM and 3:35 PM CT. The issue was related to intermittent resource contention which impacted the processing of balance-related requests. This resulted in elevated error rates for: - Balance Inquiries: Retrieving account or funding source balances (/funding-sources/{id}/balance). System performance stabilized at 3:35 PM CT and error rates have returned to normal. This incident has been resolved.
We have experienced a delay in the morning processing of ACH transactions on the platform. This impacts the webhook delivery and API transfer status updates for ACH credit and debit transactions that are expected to update today. Due to today being a high processing day, we expect this issue to cause impacts with the 9:00 AM CT Same-day ACH debit and credit transactions. These transactions will likely be delayed to the 1PM CT Same-day ACH window. Our support team is working as quickly as possible to recover from this. We will provide an update when the process completes, and we apologize for any inconvenience caused by this disruption.
This incident has been resolved. All transfers statuses have been updated and webhooks are being delivered. Please note: As a result, this impacts the 9:00 AM CT export of Same-day ACH debit and credit transactions. These transactions will now export at 1:00 PM CT.
The FED has experienced system issues this morning causing a delay in Same Day ACH processing. Same-Day ACH debit and credit transactions that were expected to clear at 12:00 PM CT will be delayed. We are monitoring the situation and working with our partners, and will update this status when we have more information about when those transfers will be processed. We apologize for any inconvenience caused by this disruption.
The Federal Reserve experienced system issues this morning, causing a delay in Same-Day ACH processing. Same-Day ACH debit and credit transactions that were expected to clear at 12:00 PM CT will now clear at 5:00 PM CT. We apologize for any inconvenience caused by this disruption.
We are currently investigating reports of intermittent failures and elevated error rates (500 Internal Server Errors) affecting balance checks and balance-sourced transfers within our Production API. Our engineering team is actively working to identify the root cause. We will provide an update as soon as more information is available.
We experienced a service disruption in our Production environment between 11:25 AM and 11:36 AM CT. The issue was related to intermittent resource contention which impacted the processing of balance-related requests. This resulted in elevated error rates for: - Balance Inquiries: Retrieving account or funding source balances. - Transfer Requests: Initiating transfers, particularly those involving balance sources. System performance stabilized at 11:36 AM PDT and error rates have returned to normal. We are continuing to monitor our systems to ensure sustained stability while we complete our internal review.
This incident has been resolved.
We experienced a temporary outage that impacted the /customers endpoint. Between 2:22:57 PM and 2:32:38 PM CT, the system was returning HTTP 500 errors due to a brief disruption in service. The issue has been resolved, and the system is stable. We apologize for any inconvenience this may have caused.
We're investigating increased API 500 errors on the customers/{accoundId}/transfers and accounts/{accountId}/transfers endpoints. This affects the API and the Dashboard. We will provide updates as they are available.
A fix has been deployed and the errors have stopped occurring.
We have identified an issue impacting sandbox transfer searches via the dashboard and api. The team is working on a fix and will provide updates as they become available. This impacts the sandbox environment only.
A fix has been identified and is being deployed.
The fix is deployed and sandbox transfer search in the dashboard and api are functioning normally.
We experienced a brief disruption with the Sandbox API that impacted funding source creation and retrieval, as well as transfer creation and retrieval for all Sandbox users. The issue occurred between 9:06 AM CT and 9:27 AM CT and has since been resolved.
We are currently investigating an issue with instant payments status updates. The Dwolla platform is currently able to successfully create and process instant payments, but their statuses are not being updated in our system. Clients using instant payments will see these statuses marked as "pending". We are actively investigating and will provide updates as we make progress.
A fix has been applied, and the team is processing the backlog of status updates. We will provide an update when this is completed.
This incident is resolved. All pending instant payment statuses have been updated.
The Fed experienced a delay processing our Same-Day ACH transactions that should have exported today at 3:00 PM CT. This impacts the webhook delivery and API transfer status updates for Same-Day ACH credit and debit transactions that were expected to process at 5:00 PM CT today. As a result, these transfers are now expected be processed tomorrow morning 02/06/2026. We apologize for the inconvenience.
Dwolla has issued some 1099k forms to end users with the amounts higher than expected. If your business has customers who are receiving a 1099k from Dwolla, they may have received a form 1099k with the wrong amount. The Dwolla team is aware of the issue and is taking steps to correct it. We will provide more information on the steps taken as it becomes available. Note that Dwolla's payment platform and API are not impacted by this issue.
We have sent an email to all affected end users explaining what happened and informing them that corrected Form 1099-K will be issued, sent to them, and filed with the appropriate tax authorities. We are working through the process to send the corrected 1099-K forms to end users, and we will get those sent and filed by the February 2, 2026 deadline. Note that Dwolla's payment platform and API are not impacted by this issue.
We have resolved the issue that caused incorrect amounts. We intend to file the updated 1099K forms with the appropriate tax authorities on Monday morning to avoid any operational impact over the weekend. We will provide an update when this is complete.
Most of the incorrect 1099K forms that were sent to end users were stopped before they were filed with tax agencies. These 1099K forms have been updated and filed. A small number of 1099K forms were filed with tax agencies and require corrections. The team is working through the corrections process. We will provide an update when this is complete.
The team has completed the Form 1099K corrections and filed them with the appropriate tax agencies. This incident is resolved.
We have identified an issue causing a subset of webhooks to remain in a "Queued" or "Pending" state rather than being delivered to API consumer endpoints. Our engineering team has traced the issue to performance degradation within our processing infrastructure that began at approximately 1:30 AM UTC on Saturday, January 3rd. We have taken steps to isolate the affected components and have restored normal processing for new events. Impact: Webhooks generated between Saturday, Jan 3rd and Monday, Jan 5th may experience significant delays or may not have been sent yet. Current webhook traffic is processing normally.
We are currently monitoring system health to ensure continued stability. Our team is now working through the recovery process for webhooks that were delayed or missed during the service interruption. We will provide an update once the backlog has been fully processed and all events have been delivered.
The team is currently processing the backlog of webhooks. We will provide an update when this is complete.
All delayed webhooks and customer notifications have been successfully sent. This incident is resolved.
We are currently experiencing an issue with our API traffic related to the ongoing Cloudflare outage, being tracked at cloudflarestatus.com. A significant portion of requests to Dwolla's API are being returned by Cloudflare as errors. We are monitoring this situation closely and will provide updates as soon as possible.
Cloudflare has implemented a fix. We're seeing API and dashboard activity returning to normal. We will continue to monitor the systems.
We are investigating a small percentage of traffic that is still being returned as errors by Cloudflare's system. While API functionality is largely back to normal, clients may still experience some errors. We will continue to work with Cloudflare to resolve this as soon as possible.
The issue on Cloudflare's end appears to be resolved and API traffic is back to normal. We're continuing to monitor.
This incident has been resolved.
We are currently experiencing an issue affecting Instant Payments submitted through our API. Since approximately 7:58 AM CT, these payments have been processed as expected — meaning that funds are being successfully transferred to the intended bank accounts. However, their transfer status remains "pending" in our system, creating a discrepancy between the actual fund movement and the reported transaction state. The root cause has been identified, and we are actively implementing a fix to resolve the underlying issue. Note: To avoid unintended duplicate payments, please refrain from resubmitting these transactions, as the transfers are still being processed correctly. We appreciate your patience as we work to restore normal transfer status updates. Further updates will be provided as soon as they are available.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently experiencing higher than normal response times on the /customers and /transfers endpoints and are working to resolve this issue. We'll update again when this issue has been resolved.
We have identified the cause of the degraded performance and have implemented a fix. Response times across the API are now improving.
This incident has been resolved.
Last night, beginning approximately at 8:27 PM CT. A recent change resulted in a temporary outage of our RTP service. This caused a backlog of transactions to accumulate and delayed the processing of some payments. Our engineering team identified the root cause and took immediate action. We successfully restored the service at approximately 8:45 AM CT. All affected payments have now been successfully processed, and the system is operating as expected. We have implemented a permanent fix to address the underlying issue and prevent a recurrence. We apologize for any inconvenience this may have caused and appreciate your patience.