Skip to main content

Is Dwolla Down?

No — Dwolla is up

Reachable from all 8 checked regions

Average response time: 276ms

Last checked · checks run every 6 hours

Official status page: https://status.dwolla.com

Dwolla uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
149ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 29 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

29-day clean streak
Aug 25: no data
Aug 26: 100.00% uptime, 24 checks
Aug 27: 100.00% uptime, 32 checks
Aug 28: 100.00% uptime, 32 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 100.00% uptime, 31 checks
Aug 31: 100.00% uptime, 31 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 31 checks
Sep 3: 100.00% uptime, 32 checks
Sep 4: 100.00% uptime, 24 checks
Sep 5: 100.00% uptime, 21 checks
Sep 6: 100.00% uptime, 21 checks
Sep 7: 100.00% uptime, 31 checks
Sep 8: 100.00% uptime, 32 checks
Sep 9: 100.00% uptime, 30 checks
Sep 10: 100.00% uptime, 38 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 24 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 40 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 8 checks
Aug 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

fra
305ms
DNS 256ms TCP 2ms TLS 9ms TTFB 294ms
gru
271ms
DNS 193ms TCP 2ms TLS 9ms TTFB 229ms
iad
115ms
DNS 67ms TCP 1ms TLS 8ms TTFB 102ms
jnb
450ms
DNS 240ms TCP 0ms TLS 8ms TTFB 443ms
lax
165ms
DNS 48ms TCP 2ms TLS 15ms TTFB 154ms
lhr
363ms
DNS 317ms TCP 2ms TLS 8ms TTFB 353ms
nrt
285ms
DNS 20ms TCP 2ms TLS 8ms TTFB 277ms
ord
256ms
DNS 208ms TCP 2ms TLS 9ms TTFB 245ms

What Dwolla does

Dwolla moves money between bank accounts in the United States over the ACH network. Platforms embed its API to pay out to users, collect funds and verify bank accounts instead of building bank connectivity themselves. Because it sits between a product and the banking system, an incident stops payments inside somebody else's application.

What an outage looks like

Calls to create transfers return errors or time out, and money movement stops rather than failing loudly for end users. Webhooks that tell your backend a transfer settled stop arriving, so transfer status in your own database goes stale while the underlying payment may still be progressing. The dashboard can be unavailable separately from the API.

What to do about it

Check Dwolla's status page and read the component rows: API, Dashboard and Website are reported separately for Production and Sandbox, so a Sandbox incident does not affect live money. The page also tracks upstreams including Plaid, MX, Visa, Cloudflare, AWS and Federal Reserve services. Do not retry transfers blindly, since a request that timed out may have been accepted.

Is it down for everyone, or just you?

If this page says Dwolla is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Dwolla outage FAQ

Will my in-flight ACH transfers still settle?
Generally yes. ACH settlement runs on banking infrastructure and a Dwolla API incident does not reverse transfers already submitted. What you lose is visibility: status updates and webhooks are delayed, so your records lag behind reality. Dwolla has reported exactly this shape, where processing was delayed and webhooks were delivered once the incident resolved.
Should I retry a transfer that returned an error?
Not without checking. A request that timed out may have been accepted before the response failed, and retrying risks sending money twice. Query the transfer by its idempotency key, or list recent transfers once the API returns, confirm what actually exists, and only then resubmit the ones that genuinely did not land.
Is the Federal Reserve part of this?
Dwolla's status page lists Federal Reserve services among the infrastructure it depends on, alongside Cloudflare and AWS. ACH clearing runs on that rail, so a banking-side delay can slow settlement even when Dwolla's own API is fully operational. Same-day ACH clearing delays have appeared as incidents in their history.
Does a Sandbox outage mean Production is affected?
No. Dwolla reports API, Dashboard and Website separately for Production and Sandbox. A Sandbox incident affects testing and integration work while real money movement continues normally. It is worth checking which environment an incident names before telling customers their payments are delayed.

How we measure this

  • We request Dwolla's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Dwolla publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Dwolla goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required