Skip to content

Outage tracker / Dwolla

Is Dwolla down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Dwolla from all 10 regions we check.

As of Oct 5, 2026, 8:15 PM UTC, Dwolla answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

our independent probeslive · checked Oct 5, 2026, 8:15 PM UTC
US-East206 msOperational
US-West138 msOperational
Europe887 msOperational
Asia-Pacific748 msOperational
US-Central225 msOperational
Canada345 msOperational
UK834 msOperational
Southeast Asia963 msOperational
Australia1150 msOperational
South America1092 msOperational
their status pagetheir claim, not our reading

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

from Dwolla's own status page, checked Oct 5, 2026, 7:52 PM UTC
Our probes and Dwolla's own status page agree: both show Dwolla as reachable right now.

Dwolla's own component breakdown, as they publish it

  • API - ProductionOperational
  • CloudflareOperational
  • PlaidOperational
  • API - SandboxOperational
  • Amazon Web Services EC2Operational
  • 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
383msp95 · latest
500ms250ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 337ms2026-09-07 UTC: p95 362ms2026-09-08 UTC: p95 368ms2026-09-09 UTC: p95 358ms2026-09-10 UTC: p95 317ms2026-09-11 UTC: p95 448ms2026-09-12 UTC: p95 274ms2026-09-13 UTC: p95 465ms2026-09-14 UTC: p95 316ms2026-09-15 UTC: p95 405ms2026-09-16 UTC: p95 412ms2026-09-17 UTC: p95 287ms2026-09-18 UTC: p95 254ms2026-09-19 UTC: p95 236ms2026-09-20 UTC: p95 229ms2026-09-21 UTC: p95 308ms2026-09-22 UTC: p95 484ms2026-09-23 UTC: p95 332ms2026-09-24 UTC: p95 342ms2026-09-25 UTC: p95 232ms2026-09-26 UTC: p95 329ms2026-09-27 UTC: p95 327ms2026-09-28 UTC: p95 317ms2026-09-29 UTC: p95 444ms2026-09-30 UTC: p95 458ms2026-10-01 UTC: p95 452ms2026-10-02 UTC: p95 393ms2026-10-03 UTC: p95 449ms2026-10-04 UTC: p95 433ms2026-10-05 UTC: p95 383ms
Sep 6Sep 20Oct 5
US-West
382msp95 · 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-09-06 UTC: p95 471ms2026-09-07 UTC: p95 494ms2026-09-08 UTC: p95 585ms2026-09-09 UTC: p95 354ms2026-09-10 UTC: p95 236ms2026-09-11 UTC: p95 328ms2026-09-12 UTC: p95 816ms2026-09-13 UTC: p95 747ms2026-09-14 UTC: p95 327ms2026-09-15 UTC: p95 353ms2026-09-16 UTC: p95 235ms2026-09-17 UTC: p95 363ms2026-09-18 UTC: p95 233ms2026-09-19 UTC: p95 243ms2026-09-20 UTC: p95 264ms2026-09-21 UTC: p95 544ms2026-09-22 UTC: p95 695ms2026-09-23 UTC: p95 502ms2026-09-24 UTC: p95 301ms2026-09-25 UTC: p95 758ms2026-09-26 UTC: p95 674ms2026-09-27 UTC: p95 279ms2026-09-28 UTC: p95 586ms2026-09-29 UTC: p95 300ms2026-09-30 UTC: p95 378ms2026-10-01 UTC: p95 448ms2026-10-02 UTC: p95 322ms2026-10-03 UTC: p95 491ms2026-10-04 UTC: p95 388ms2026-10-05 UTC: p95 382ms
Sep 6Sep 20Oct 5
Europe
1.0sp95 · 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-09-06 UTC: p95 948ms2026-09-07 UTC: p95 971ms2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 1s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 919ms2026-09-15 UTC: p95 980ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 902ms2026-09-23 UTC: p95 913ms2026-09-24 UTC: p95 946ms2026-09-25 UTC: p95 942ms2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 918ms2026-10-01 UTC: p95 951ms2026-10-02 UTC: p95 958ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.0s
Sep 6Sep 20Oct 5
Asia-Pacific
1.0sp95 · 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-09-06 UTC: p95 954ms2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 838ms2026-09-09 UTC: p95 922ms2026-09-10 UTC: p95 854ms2026-09-11 UTC: p95 956ms2026-09-12 UTC: p95 936ms2026-09-13 UTC: p95 943ms2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 916ms2026-09-16 UTC: p95 971ms2026-09-17 UTC: p95 912ms2026-09-18 UTC: p95 961ms2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 992ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 923ms2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 976ms2026-09-28 UTC: p95 936ms2026-09-29 UTC: p95 870ms2026-09-30 UTC: p95 960ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 999ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.0s
Sep 6Sep 20Oct 5
US-Central
424msp95 · 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-06 UTC: p95 664ms2026-09-07 UTC: p95 567ms2026-09-08 UTC: p95 440ms2026-09-09 UTC: p95 452ms2026-09-10 UTC: p95 672ms2026-09-11 UTC: p95 639ms2026-09-12 UTC: p95 434ms2026-09-13 UTC: p95 633ms2026-09-14 UTC: p95 606ms2026-09-15 UTC: p95 699ms2026-09-16 UTC: p95 534ms2026-09-17 UTC: p95 405ms2026-09-18 UTC: p95 436ms2026-09-19 UTC: p95 442ms2026-09-20 UTC: p95 423ms2026-09-21 UTC: p95 388ms2026-09-22 UTC: p95 746ms2026-09-23 UTC: p95 651ms2026-09-24 UTC: p95 493ms2026-09-25 UTC: p95 451ms2026-09-26 UTC: p95 552ms2026-09-27 UTC: p95 385ms2026-09-28 UTC: p95 407ms2026-09-29 UTC: p95 591ms2026-09-30 UTC: p95 529ms2026-10-01 UTC: p95 503ms2026-10-02 UTC: p95 371ms2026-10-03 UTC: p95 501ms2026-10-04 UTC: p95 356ms2026-10-05 UTC: p95 424ms
Sep 6Sep 20Oct 5
Canada
582msp95 · 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-06 UTC: p95 619ms2026-09-07 UTC: p95 587ms2026-09-08 UTC: p95 478ms2026-09-09 UTC: p95 543ms2026-09-10 UTC: p95 566ms2026-09-11 UTC: p95 409ms2026-09-12 UTC: p95 468ms2026-09-13 UTC: p95 617ms2026-09-14 UTC: p95 456ms2026-09-15 UTC: p95 638ms2026-09-16 UTC: p95 676ms2026-09-17 UTC: p95 405ms2026-09-18 UTC: p95 600ms2026-09-19 UTC: p95 391ms2026-09-20 UTC: p95 394ms2026-09-21 UTC: p95 512ms2026-09-22 UTC: p95 442ms2026-09-23 UTC: p95 426ms2026-09-24 UTC: p95 607ms2026-09-25 UTC: p95 613ms2026-09-26 UTC: p95 438ms2026-09-27 UTC: p95 508ms2026-09-28 UTC: p95 644ms2026-09-29 UTC: p95 583ms2026-09-30 UTC: p95 598ms2026-10-01 UTC: p95 588ms2026-10-02 UTC: p95 446ms2026-10-03 UTC: p95 640ms2026-10-04 UTC: p95 450ms2026-10-05 UTC: p95 582ms
Sep 6Sep 20Oct 5
UK
1.2sp95 · 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-06 UTC: p95 1.1s2026-09-07 UTC: p95 814ms2026-09-08 UTC: p95 790ms2026-09-09 UTC: p95 864ms2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 862ms2026-09-12 UTC: p95 949ms2026-09-13 UTC: p95 883ms2026-09-14 UTC: p95 919ms2026-09-15 UTC: p95 845ms2026-09-16 UTC: p95 910ms2026-09-17 UTC: p95 918ms2026-09-18 UTC: p95 894ms2026-09-19 UTC: p95 824ms2026-09-20 UTC: p95 806ms2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 993ms2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 900ms2026-09-26 UTC: p95 826ms2026-09-27 UTC: p95 832ms2026-09-28 UTC: p95 823ms2026-09-29 UTC: p95 978ms2026-09-30 UTC: p95 936ms2026-10-01 UTC: p95 916ms2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
Southeast Asia
1.6sp95 · 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-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 2.0s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 1.8s2026-09-22 UTC: p95 1.9s2026-09-23 UTC: p95 2.0s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.6s
Sep 6Sep 20Oct 5
Australia
2.0sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.9s2026-09-08 UTC: p95 1.8s2026-09-09 UTC: p95 1.8s2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.7s2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 1.8s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 2.2s2026-10-01 UTC: p95 1.9s2026-10-02 UTC: p95 2.1s2026-10-03 UTC: p95 2.0s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 2.0s
Sep 6Sep 20Oct 5
South America
1.6sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.7s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 1.7s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.7s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.6s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 1.6s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.9s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 2.1s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.9s2026-10-03 UTC: p95 2.3s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.6s
Sep 6Sep 20Oct 5

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: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Dwolla go down, and when it is back

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.

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.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 206msstatus code: 401checked: Oct 5, 2026, 7:57 PM 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: 138msstatus code: 401checked: Oct 5, 2026, 7:47 PM 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: 225msstatus code: 401checked: Oct 5, 2026, 8:10 PM 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: 345msstatus code: 401checked: Oct 5, 2026, 8:12 PM 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: 1092msstatus code: 401checked: Oct 5, 2026, 8:15 PM 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: 887msstatus code: 401checked: Oct 5, 2026, 7:53 PM 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: 834msstatus code: 401checked: Oct 5, 2026, 7:24 PM 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: 748msstatus code: 401checked: Oct 5, 2026, 7:50 PM 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: 963msstatus code: 401checked: Oct 5, 2026, 7:24 PM 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: 1150msstatus code: 401checked: Oct 5, 2026, 7:30 PM 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

Delay in processing ACH transactions, Instant Payments, and delivery of related webhooks in production, 6h 43mdeclared on their status page2026-09-09
[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

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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

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

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.