Skip to main content

Is Dwolla Down?

No — Dwolla is up

Reachable from all 8 checked regions

Average response time: 136ms

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
102ms
Avg response, 30 days

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

30-day history

15-day clean streak
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: no data
Aug 17: no data
Aug 18: no data
Aug 19: no data
Aug 20: no data
Aug 21: no data
Aug 22: no data
Aug 23: no data
Aug 24: no data
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: no data
Aug 12 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.

gru
87ms
DNS 0ms TCP 2ms TLS 13ms TTFB 68ms
iad
59ms
DNS 1ms TCP 2ms TLS 12ms TTFB 45ms
jnb
197ms
DNS 0ms TCP 1ms TLS 8ms TTFB 190ms
lax
113ms
DNS 1ms TCP 1ms TLS 17ms TTFB 100ms
lhr
74ms
DNS 0ms TCP 8ms TLS 16ms TTFB 62ms
nrt
267ms
DNS 4ms TCP 1ms TLS 6ms TTFB 257ms
ord
68ms
DNS 1ms TCP 2ms TLS 9ms TTFB 42ms
sin
226ms
DNS 1ms TCP 1ms TLS 12ms TTFB 217ms

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