Skip to content

Outage tracker / Dwolla

Is Dwolla down?

I'm having a problem

Vendor reports no incidentWhat Dwolla reports

Dwolla reports no incident on its status page.

As of the last successful poll, 2026-10-22 21:50 UTC.

Dwolla's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

Our checks of Dwolla pass from all 10 regions we check.

As of Oct 22, 2026, 9:51 PM UTC, RealUptime's checks of Dwolla passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 9:51 PM UTC
US-East1120 msChecks passing
US-West1010 msChecks passing
Europe217 msChecks passing
Asia-Pacific1618 msChecks passing
US-Central172 msChecks passing
Canada330 msChecks passing
UK1082 msChecks passing
Southeast Asia2276 msChecks passing
Australia2336 msChecks passing
South America2656 msChecks passing
their status pagetheir claim, not our reading

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

from Dwolla's own status page, checked Oct 22, 2026, 9:33 PM UTC
Dwolla's own status page shows no incident, and our checks of Dwolla pass 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
1.3sp95 · 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-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 381ms2026-10-06 UTC: p95 371ms2026-10-07 UTC: p95 411ms2026-10-08 UTC: p95 398ms2026-10-09 UTC: p95 398ms2026-10-10 UTC: p95 494ms2026-10-11 UTC: p95 416ms2026-10-12 UTC: p95 339ms2026-10-13 UTC: p95 446ms2026-10-14 UTC: p95 371ms2026-10-15 UTC: p95 476ms2026-10-16 UTC: p95 456ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22
US-West
1.3sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 404ms2026-10-06 UTC: p95 314ms2026-10-07 UTC: p95 390ms2026-10-08 UTC: p95 381ms2026-10-09 UTC: p95 339ms2026-10-10 UTC: p95 401ms2026-10-11 UTC: p95 414ms2026-10-12 UTC: p95 455ms2026-10-13 UTC: p95 483ms2026-10-14 UTC: p95 458ms2026-10-15 UTC: p95 429ms2026-10-16 UTC: p95 498ms2026-10-17 UTC: p95 571ms2026-10-18 UTC: p95 470ms2026-10-19 UTC: p95 592ms2026-10-20 UTC: p95 547ms2026-10-21 UTC: p95 600ms2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22
Europe
979msp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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.1s2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 2.0s2026-10-09 UTC: p95 1.8s2026-10-10 UTC: p95 2.0s2026-10-11 UTC: p95 2.2s2026-10-12 UTC: p95 1.9s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 920ms2026-10-18 UTC: p95 899ms2026-10-19 UTC: p95 993ms2026-10-20 UTC: p95 991ms2026-10-21 UTC: p95 955ms2026-10-22 UTC: p95 979ms
Sep 23Oct 7Oct 22
Asia-Pacific
1.7sp95 · 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-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.1s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 1.9s2026-10-11 UTC: p95 1.9s2026-10-12 UTC: p95 1.8s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 1.7s
Sep 23Oct 7Oct 22
US-Central
483msp95 · 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-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 413ms2026-10-06 UTC: p95 439ms2026-10-07 UTC: p95 424ms2026-10-08 UTC: p95 628ms2026-10-09 UTC: p95 565ms2026-10-10 UTC: p95 532ms2026-10-11 UTC: p95 489ms2026-10-12 UTC: p95 492ms2026-10-13 UTC: p95 443ms2026-10-14 UTC: p95 540ms2026-10-15 UTC: p95 522ms2026-10-16 UTC: p95 587ms2026-10-17 UTC: p95 834ms2026-10-18 UTC: p95 586ms2026-10-19 UTC: p95 472ms2026-10-20 UTC: p95 887ms2026-10-21 UTC: p95 723ms2026-10-22 UTC: p95 483ms
Sep 23Oct 7Oct 22
Canada
575msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 566ms2026-10-06 UTC: p95 816ms2026-10-07 UTC: p95 515ms2026-10-08 UTC: p95 510ms2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 630ms2026-10-14 UTC: p95 515ms2026-10-15 UTC: p95 623ms2026-10-16 UTC: p95 639ms2026-10-17 UTC: p95 541ms2026-10-18 UTC: p95 517ms2026-10-19 UTC: p95 391ms2026-10-20 UTC: p95 472ms2026-10-21 UTC: p95 589ms2026-10-22 UTC: p95 575ms
Sep 23Oct 7Oct 22
UK
1.3sp95 · 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-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.2s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 1.9s2026-10-11 UTC: p95 1.9s2026-10-12 UTC: p95 1.8s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 916ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22
Southeast Asia
2.9sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.5s2026-10-06 UTC: p95 1.4s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 2.0s2026-10-10 UTC: p95 2.9s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 2.0s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.8s2026-10-15 UTC: p95 1.9s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.6s2026-10-18 UTC: p95 2.9s2026-10-19 UTC: p95 2.7s2026-10-20 UTC: p95 2.9s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 2.9s
Sep 23Oct 7Oct 22
Australia
2.6sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.0s2026-10-06 UTC: p95 1.8s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 2.5s2026-10-11 UTC: p95 2.4s2026-10-12 UTC: p95 2.5s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.9s2026-10-20 UTC: p95 2.7s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 2.6s
Sep 23Oct 7Oct 22
South America
3.2sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.6s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 2.0s2026-10-10 UTC: p95 2.9s2026-10-11 UTC: p95 2.2s2026-10-12 UTC: p95 2.2s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.9s2026-10-16 UTC: p95 2.0s2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 2.8s2026-10-21 UTC: p95 3.2s2026-10-22 UTC: p95 3.2s
Sep 23Oct 7Oct 22

Check your own site while you wait on Dwolla

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Dwolla reports an incident on its status page, and again when it reports it resolved.

Get an email when Dwolla reports an incident

Email me when Dwolla reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Dwolla's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1120msstatus code: 401checked: Oct 22, 2026, 9:51 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
      Checks passinglatency: 1010msstatus code: 401checked: Oct 22, 2026, 9:28 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
      Checks passinglatency: 172msstatus code: 401checked: Oct 22, 2026, 9:19 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
      Checks passinglatency: 330msstatus code: 401checked: Oct 22, 2026, 9:20 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
    Checks passinglatency: 2656msstatus code: 401checked: Oct 22, 2026, 8:53 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 217msstatus code: 401checked: Oct 22, 2026, 9:23 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
      Checks passinglatency: 1082msstatus code: 401checked: Oct 22, 2026, 9:46 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1618msstatus code: 401checked: Oct 22, 2026, 9:37 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
      Checks passinglatency: 2276msstatus code: 401checked: Oct 22, 2026, 9:39 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
      Checks passinglatency: 2336msstatus code: 401checked: Oct 22, 2026, 9:40 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 probe events

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

check 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 check readings and Dwolla's own claim at the time, side by side.

Full check history for Dwolla: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 by RealUptime's checksLive, from this page's own readings.
[![Dwolla uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Dwolla down?", https://realuptime.io/outages/dwolla. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://api.dwolla.com/
secondary
https://www.dwolla.com/
secondary
https://status.dwolla.com/api/v2/status.json

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.dwolla.com

RealUptime is not affiliated with Dwolla; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.