Dwolla Outage History

23 incidents recorded over the last 365 days, 23 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Dwolla Incident

Dwolla incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 13, 2026Failures in Instant PaymentsThis incident has been resolved. Instant Payments are now processing normally. The last UR01 error was observed at 9:33 AM CT. Transfers that failed with UR01 during the disruption did not complete and may be…25 minResolved
Jul 22, 2026[Sandbox] Webhooks and dashboard unavailabilityWe 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.-282 minResolved
Jul 13, 2026Elevated API 500 errors on Customers, Funding Sources, and Mass PaymentsThis issue is resolved.2h 16mResolved
Jun 11, 2026Delayed Operational Notification Statuses in Dwolla DashboardThe 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…35 minResolved
Jun 9, 2026Elevated HTTP 500 Errors on Balance InquiriesWe 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…-64 minResolved
Jun 2, 2026Delay in processing ACH transactions and delivery of related webhooksThis 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…1h 36mResolved
May 14, 2026Delay in Same-Day ACH ClearingThe 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…3h 8mResolved
Apr 28, 2026Elevated HTTP 500 Errors on Balance Inquiries and TransfersThis incident has been resolved.2h 27mResolved
Apr 23, 2026Elevated HTTP 500 Errors on CustomersWe 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…-55 minResolved
Apr 13, 2026Delay in Same-Day ACH ClearingWe experienced 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…0 minResolved
Apr 3, 2026Errors on the customers/{accoundId}/transfers endpointA fix has been deployed and the errors have stopped occurring.22 minResolved
Mar 26, 2026Delay in processing ACH transactions and delivery of related webhooksThis incident has been resolved. All transfers statuses have been updated and webhooks have been delivered. There was no impact to the 9:00 AM CT export of Same-day ACH debit and credit transactions. All Same-day…1h 43mResolved
Mar 25, 2026Sandbox Transfer Searches DegradedThe fix is deployed and sandbox transfer search in the dashboard and api are functioning normally.2h 9mResolved
Mar 18, 2026[Sandbox] Experienced degraded performanceWe 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…0 minResolved
Mar 8, 2026Instant Payments Status UpdatesThis incident is resolved. All pending instant payment statuses have been updated.3h 37mResolved
Mar 3, 2026Delay in processing ACH transactions and delivery of related webhooksACH transfer statuses that were expected to update at 5pm have all been updated, and related webhooks are being delivered. This incident is resolved.10h 34mResolved
Feb 5, 2026Delay in processing Same-Day ACH transactionsThe 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…0 minResolved
Jan 29, 2026Issued 1099K forms with inflated amountsThe team has completed the Form 1099K corrections and filed them with the appropriate tax agencies. This incident is resolved.137h 8mResolved
Jan 5, 2026Delay in delivery of webhooks and operational notificationsAll delayed webhooks and customer notifications have been successfully sent. This incident is resolved.8h 25mResolved
Nov 18, 2025API Errors from Upstream ProviderThis incident has been resolved.5h 3mResolved
Nov 17, 2025Delays in Instant Payments (RTP/FedNow) Status UpdatesThis incident has been resolved.3h 56mResolved
Oct 27, 2025Delay in processing ACH transactions and delivery of related webhooksDue to this incident, some of the usual 9:00 AM CT export of Same-day ACH debit and credit transactions might have been delayed. The affected transactions, if any, will now be exported at 1:00 PM CT. All of the…34 minResolved
Aug 26, 2025Intermittent high response times and timeouts on /customers and /transfersThis incident has been resolved.3h 47mResolved

How to Read This Dwolla Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Dwolla acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Dwolla outage in this window ran 5d 17h, against a mean recovery of 9h 23m. If you depend on Dwolla in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.