Skip to content

Outage tracker / Dwolla

Is Dwolla down?

Short linkrlup.io/down/dwolla

I'm having a problem

Operationalchecked 14 minutes ago

We reached Dwolla from all 10 regions we check.

Functional endpoints verified

We have an outage open for Dwolla, 7h 27m so far.

No outage recorded in the 15 days we have measured Dwolla (since Aug 22, 2026).

our independent probeslive · checked Sep 6, 2026, 4:22 AM UTC
US-East632 msOperational
US-West150 msOperational
Europe869 msOperational
Asia-Pacific695 msOperational
US-Central333 msOperational
Canada619 msOperational
UK1018 msOperational
Southeast Asia1080 msOperational
Australia1193 msOperational
South America1486 msOperational
their status pagetheir claim, not our reading

Dwolla reports: All systems operational (“All Systems Operational”)

from Dwolla's own status page, checked Sep 5, 2026, 11:10 PM UTC

Dwolla's own component breakdown, as they publish it (our last read of their page failed, so this is the previous reading)

  • API - ProductionOperational
  • CloudflareOperational
  • PlaidOperational
  • Amazon Web Services EC2Operational
  • API - SandboxOperational
  • MXOperational
  • Dashboard - ProductionOperational
  • VisaOperational
  • Dashboard - SandboxOperational
  • Website - ProductionOperational
  • Website - SandboxOperational
  • Developer PortalOperational
  • API DocsOperational
  • Federal Reserve Services - FedACHOperational
  • Tax formsOperational

These are Dwolla's components, named and scored by Dwolla. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Dwolla's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Dwolla response time, by region

US-East
506msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 1.3s2026-08-23 UTC: p95 1.3s2026-08-24 UTC: p95 1.1s2026-08-25 UTC: p95 903ms2026-08-26 UTC: p95 952ms2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 660ms2026-08-29 UTC: p95 994ms2026-08-30 UTC: p95 1.1s2026-08-31 UTC: p95 1.2s2026-09-01 UTC: p95 1.1s2026-09-02 UTC: p95 382ms2026-09-03 UTC: p95 774ms2026-09-04 UTC: p95 697ms2026-09-05 UTC: p95 229ms2026-09-06 UTC: p95 506ms
Aug 8Aug 22Sep 6
US-West
488msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 408ms2026-08-23 UTC: p95 460ms2026-08-24 UTC: p95 403ms2026-08-25 UTC: p95 477ms2026-08-26 UTC: p95 503ms2026-08-27 UTC: p95 810ms2026-08-28 UTC: p95 431ms2026-08-29 UTC: p95 389ms2026-08-30 UTC: p95 534ms2026-08-31 UTC: p95 706ms2026-09-01 UTC: p95 352ms2026-09-02 UTC: p95 520ms2026-09-03 UTC: p95 662ms2026-09-04 UTC: p95 793ms2026-09-05 UTC: p95 686ms2026-09-06 UTC: p95 488ms
Aug 8Aug 22Sep 6
Europe
924msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 1.0s2026-08-23 UTC: p95 1.1s2026-08-24 UTC: p95 1.1s2026-08-25 UTC: p95 1.0s2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 1.0s2026-08-28 UTC: p95 1.0s2026-08-29 UTC: p95 1.0s2026-08-30 UTC: p95 1.1s2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 1.1s2026-09-02 UTC: p95 1.1s2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 1.2s2026-09-06 UTC: p95 924ms
Aug 8Aug 22Sep 6
Asia-Pacific
759msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 849ms2026-08-23 UTC: p95 1.1s2026-08-24 UTC: p95 886ms2026-08-25 UTC: p95 1.0s2026-08-26 UTC: p95 986ms2026-08-27 UTC: p95 1.0s2026-08-28 UTC: p95 1.2s2026-08-29 UTC: p95 1.0s2026-08-30 UTC: p95 1.1s2026-08-31 UTC: p95 982ms2026-09-01 UTC: p95 1.2s2026-09-02 UTC: p95 1.3s2026-09-03 UTC: p95 1.4s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 1.1s2026-09-06 UTC: p95 759ms
Aug 8Aug 22Sep 6
US-Central
550msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 546ms2026-09-04 UTC: p95 852ms2026-09-05 UTC: p95 859ms2026-09-06 UTC: p95 550ms
Aug 8Aug 22Sep 6
Canada
619msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 607ms2026-09-04 UTC: p95 804ms2026-09-05 UTC: p95 788ms2026-09-06 UTC: p95 619ms
Aug 8Aug 22Sep 6
UK
979msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 998ms2026-09-06 UTC: p95 979ms
Aug 8Aug 22Sep 6
Southeast Asia
1.2sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.7s2026-09-04 UTC: p95 1.8s2026-09-05 UTC: p95 1.6s2026-09-06 UTC: p95 1.2s
Aug 8Aug 22Sep 6
Australia
1.2sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.8s2026-09-05 UTC: p95 1.7s2026-09-06 UTC: p95 1.2s
Aug 8Aug 22Sep 6
South America
1.6sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.6s2026-09-05 UTC: p95 1.6s2026-09-06 UTC: p95 1.6s
Aug 8Aug 22Sep 6
Why some readings show as awaiting data. 1 of 20 readings for Dwolla came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 406, 429 or 451, a redirect loop, or a timeout we could rule out as a real outage using a second endpoint) rather than a normal success or failure. That tells us about our own probe's reception, not about Dwolla's actual health, so we publish no verdict for those readings rather than guessing in either direction. Read how we tell the difference.

Is it Dwolla, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Dwolla -- it cannot diagnose Dwolla's own systems.

What we measured, function by function

Dwolla answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Awaiting data
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

Open incident

Sep 5, 2026, 9:09 PM UTCOngoing
single regionintermittent
open for 7h 27m so farAustralia: failing from Sep 5, 2026, 9:09 PM UTC, still failing

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 632msstatus code: 401checked: Sep 6, 2026, 4:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Dwolla normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 150msstatus code: 401checked: Sep 6, 2026, 4:10 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Dwolla normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 333msstatus code: 401checked: Sep 6, 2026, 4:00 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Dwolla normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 619msstatus code: 401checked: Sep 6, 2026, 4:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Dwolla normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 1486msstatus code: 401checked: Sep 6, 2026, 3:56 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Dwolla normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 869msstatus code: 401checked: Sep 6, 2026, 4:22 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Dwolla normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 1018msstatus code: 401checked: Sep 6, 2026, 4:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Dwolla normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 695msstatus code: 401checked: Sep 6, 2026, 4:14 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Dwolla normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1080msstatus code: 401checked: Sep 6, 2026, 3:57 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Dwolla normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1193msstatus code: 401checked: Sep 6, 2026, 4:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Dwolla normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Dwolla, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Dwolla yet, which is not evidence that nothing is wrong.

Recent outages

[Sandbox] API and Dashboard Errors, 24mdeclared on their status page2026-09-01
Failures in Instant Payments, 26mdeclared on their status page2026-08-13
[Sandbox] Webhooks and dashboard unavailability, 1mdeclared on their status page2026-07-22
Elevated API 500 errors on Customers, Funding Sources, and Mass Payments, 2h 17mdeclared on their status page2026-07-13
Delayed Operational Notification Statuses in Dwolla Dashboard, 36mdeclared on their status page2026-06-11
Elevated HTTP 500 Errors on Balance Inquiries, 1mdeclared on their status page2026-06-09
Delay in processing ACH transactions and delivery of related webhooks, 1h 36mdeclared on their status page2026-06-02
Delay in Same-Day ACH Clearing, 3h 9mdeclared on their status page2026-05-14

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Dwolla since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Dwolla covering any window you pick, with our measurements and Dwolla's own claim at the time, side by side.

Full availability history for Dwolla: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Dwolla, and again when they can reach it again. That is our own measurement from ten regions, not Dwolla's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Dwolla uptime measured by RealUptimeLive, from this page's own readings.
[![Dwolla uptime measured by RealUptime](https://realuptime.io/outages/dwolla/badge.svg?days=30)](https://realuptime.io/outages/dwolla)
<a href="https://realuptime.io/outages/dwolla"><img src="https://realuptime.io/outages/dwolla/badge.svg?days=30" alt="Dwolla uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Dwolla's SLA implies, from our measurement

At or above your target

We measured none of downtime for Dwolla over the 364h 36m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 21 minutes over that period.

By our measurement there is no shortfall to claim for this period.

Separately, we measured 7h 27m where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.

This is computed from our own probe measurements, not from Dwolla's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.dwolla.com/
secondary
https://www.dwolla.com/
secondary
https://status.dwolla.com/api/v2/status.json
RealUptime is not affiliated with Dwolla; the name identifies what we measured, and nothing here speaks for Dwolla's own team. We send a single web request to Dwolla from 10 regions on our own schedule and time the response. We do not see inside Dwolla's systems, do not use an account or real transaction, and are not the same signal Dwolla's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Dwolla is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.

Related services

AdyenAffirmAfterpayAlipayBinance