← Back to Dwolla's check readings
We started checking Dwolla on August 22, 2026, which is 63 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Dwolla reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Dwolla's own status page declared. Below it, any public chatter we saw about Dwolla and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Dwolla's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Dwolla in the last 24 hours, which is not evidence that nothing is wrong.
Dwolla's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Dwolla's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Dwolla next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Their declared record
Dwolla's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Delay in processing ACH transactions, Instant Payments, and delivery of related webhooks in productionMinor incident
Sep 9, 2026, 11:50 AM UTC to Sep 9, 2026, 6:32 PM UTC (6h 43m)resolved
their latest update (Sep 9, 2026, 6:32 PM UTC): This incident has been resolved. All ACH transfer statuses have been updated and related webhooks have been delivered. Instant Payments have been processing normally since approximately 9:12 AM CT.
Please note: The 9:00 AM CT export of Same-day ACH debit and credit transactions …
[Sandbox] API and Dashboard ErrorsMajor outage
Sep 1, 2026, 9:50 PM UTC to Sep 1, 2026, 10:14 PM UTC (24 min)resolved
their latest update (Sep 1, 2026, 10:14 PM UTC): The fix has been deployed and the incident is resolved.
Failures in Instant PaymentsMinor incident
Aug 13, 2026, 2:24 PM UTC to Aug 13, 2026, 2:50 PM UTC (26 min)resolved
their latest update (Aug 13, 2026, 2:50 PM UTC): This 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 retried.
We appreciate your patience.
[Sandbox] Webhooks and dashboard unavailabilityAll systems operational
Jul 22, 2026, 6:00 PM UTC to Jul 22, 2026, 6:00 PM UTC (0 min)resolved
their latest update (Jul 22, 2026, 6:00 PM UTC): 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.
Elevated API 500 errors on Customers, Funding Sources, and Mass PaymentsPartial outage
Jul 13, 2026, 5:03 PM UTC to Jul 13, 2026, 7:20 PM UTC (2h 17m)resolved
their latest update (Jul 13, 2026, 7:20 PM UTC): This issue is resolved.
Delayed Operational Notification Statuses in Dwolla DashboardAll systems operational
Jun 11, 2026, 7:09 PM UTC to Jun 11, 2026, 7:45 PM UTC (36 min)resolved
their latest update (Jun 11, 2026, 7:45 PM UTC): 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.
Elevated HTTP 500 Errors on Balance InquiriesAll systems operational
Jun 9, 2026, 8:00 PM UTC to Jun 9, 2026, 8:00 PM UTC (0 min)resolved
their latest update (Jun 9, 2026, 8:00 PM UTC): 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 Inqui…
Delay in processing ACH transactions and delivery of related webhooksMinor incident
Jun 2, 2026, 11:38 AM UTC to Jun 2, 2026, 1:14 PM UTC (1h 36m)resolved
their latest update (Jun 2, 2026, 1:14 PM UTC): 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.
Delay in Same-Day ACH ClearingMinor incident
May 14, 2026, 3:08 PM UTC to May 14, 2026, 6:17 PM UTC (3h 9m)resolved
their latest update (May 14, 2026, 6:17 PM UTC): 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 disrupti…
Elevated HTTP 500 Errors on Balance Inquiries and TransfersAll systems operational
Apr 28, 2026, 4:43 PM UTC to Apr 28, 2026, 7:10 PM UTC (2h 27m)resolved
their latest update (Apr 28, 2026, 7:10 PM UTC): This incident has been resolved.
Showing the 10 most recent of 52 incidents Dwolla has declared in the history we hold.
These entries are Dwolla's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Dwolla's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.