FROM ALL SOURCES
No sign of a widespread Dwolla problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: API - Production
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 73 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Delay in processing ACH transactions, Instant Payments, and delivery of related webhooks in production”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Dwolla's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
We don't map other services that depend on Dwolla. Dependency chains are where single points of failure hide.
Identity & trust lens
When Dwolla has trouble, people see failed logins, MFA prompts that don't arrive and sessions that drop. That's when phishing pages and “verify your account” texts show up. Only sign in through the official app or site, and don't re-enter credentials from a link someone sends you.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Dwolla, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Dwolla may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Dwolla. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Delay in processing ACH transactions, Instant Payments, and delivery of related webhooks in production
minor resolved · started · resolved
5 updates
- identified
We are experiencing delays in the morning processing of ACH transactions on the platform. This impacts the webhook delivery and API transfer status updates for ACH credit and debit transactions that were expected to update today. Instant Payments are also impacted and are failing during this time. This is the result of a connectivity interruption with our bank partner. The partner has confirmed the issue and is actively working toward resolution. We do not have an ETA at this time. Please note: the 9:00 AM CT export of Same-day ACH debit and credit transactions may be impacted. We will confirm in a follow-up update.
- identified
This issue is ongoing. We are continuing to work with our bank partner toward resolution and do not have an ETA at this time. Please note: As a result, this impacts the 9:00 AM CT export of Same-day ACH debit and credit transactions. The 9:00 AM CT Same-day window will be missed, and these transactions are now expected to export in the 1:00 PM CT file. We will continue to provide updates as more information becomes available.
- identified
Instant Payments have recovered. We have seen Instant Payments processing successfully since approximately 9:12 AM CT. Instant Payments that failed earlier during this disruption did not complete and may be retried. The delay in ACH processing is ongoing. Webhook delivery and API transfer status updates for ACH credit and debit transactions remain delayed, and we are continuing to work with our bank partner toward resolution. Please note: the 9:00 AM CT Same-day window was missed. Those transactions are now expected to export in the 1:00 PM CT file. We will continue to provide updates as more information becomes available.
- monitoring
Funds are beginning to clear and transfer related webhooks are being delivered for the day. We are monitoring the results as ACH transfer statuses continue to update. Instant Payments continue to process normally.
- resolved
This incident has been resolved. All ACH transfer statuses have been updated and related webhooks have been delivered. Instant Payments have been processing normally since approximately 9:12 AM CT. Please note: The 9:00 AM CT export of Same-day ACH debit and credit transactions was missed. These transactions exported in the 1:00 PM CT file and are expected to settle by 5:00 PM CT. We apologize for any inconvenience caused by this disruption.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.