Skip to content

Outage tracker

Dwolla: the full evidence record

The last 24 hours in detail, 15 days of measured availability, a 12-month summary, our own incident log, Dwolla's declared record, and how the two compare.

← Back to Dwolla's live status

We started measuring Dwolla on August 22, 2026, which is 15 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

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.

Each probe 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 probe is not an outage. Report bars count unverified reports, not people we verified; 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.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East100.00%617
US-West100.00%616
Europe100.00%612
Asia-Pacific100.00%597
US-Central100.00%59
Canada100.00%59
UK100.00%59
Southeast Asia100.00%56
Australia100.00%56
South America100.00%58

Monthly summary

Tracking Dwolla since Aug 22, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Oct 2025not tracked
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 22, 2026100%00 min
Sep 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for Dwolla: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Dwolla's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for Dwolla in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Dwolla's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for Dwolla since we started measuring it on August 22, 2026. We show nothing from before that date.

Their declared record

Dwolla's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

[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, 10:42 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, 9:04 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.
Elevated HTTP 500 Errors on CustomersAll systems operational
Apr 23, 2026, 8:25 PM UTC to Apr 23, 2026, 7:30 PM UTC (0 min)resolved
their latest update (Apr 23, 2026, 7:30 PM UTC): 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 …

Showing the 10 most recent of 51 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 the outages we detected ourselves. 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.

The scorecard

How Dwolla's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording Dwolla's own status page on August 22, 2026, 13 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for Dwolla since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

Dwolla decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If Dwolla believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.