Dwolla Status

Dwolla

All Systems Operational

API - Production Operational

API - Sandbox Operational

Dashboard - Production Operational

Dashboard - Sandbox Operational

Website - Production Operational

Website - Sandbox Operational

Developer Portal Operational

API Docs Operational

Open Banking Providers Operational

Visa Operational

Infrastructure Providers Operational

Cloudflare Operational

Amazon Web Services EC2 Operational

Federal Reserve Services - FedACH Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Mar 28, 2025

No incidents reported today.

Mar 27, 2025

Experiencing issues retrieving some Customer resources

Resolved - This incident has been resolved.
Mar 27, 17:27 CDT

Identified - Since 103/27/2025 1:27pm CT, we have been experiencing an issue where retrieving customers by ID for Business Verified Customer Records in the Retry, Document, or Suspended statuses is failing. This issue affects both the Dashboard and API in Sandbox and Production environments. Our team is actively working on a fix, and we will provide updates as soon as possible. We appreciate your patience and apologize for any inconvenience.
Mar 27, 16:53 CDT

Mar 26, 2025

No incidents reported.

Mar 25, 2025

No incidents reported.

Mar 24, 2025

No incidents reported.

Mar 23, 2025

No incidents reported.

Mar 22, 2025

No incidents reported.

Mar 21, 2025

[Production] Elevated API Errors Creating New Transfers

Resolved - We have resolved the issue causing elevated API error rates and 500 errors that began at approximately 4:09 PM CT. Some transfer requests during this period resulted in a 500 status code. For clients using idempotency-keys, retrying these requests might initially return a ‘409 Conflict’ error. This is due to Dwolla’s 24-hour idempotency key lock.

To ensure your transfers were processed correctly:
1. Check the Dashboard/API: Verify if the affected transfers were successfully created. If they weren’t, proceed to the next step.
2. Retry with a New Idempotency Key: If the original request resulted in a 500 and subsequently a 409, retry the request using a new idempotency key. This is the recommended approach.
3. Retry with Original Idempotency Key (After 24 Hours): Alternatively, you can retry the original request (with the same idempotency key) after the 24-hour lock expires. This will eventually return a ‘201 Created’ response if the transfer was ultimately successful.

If you continue to experience issues or have any further questions, please reach out to us at support@dwolla.com. We apologize for the inconvenience.
Mar 21, 17:24 CDT

Monitoring - A fix has been implemented and we are monitoring the results.
Mar 21, 16:50 CDT

Investigating - Beginning 03/21/2025 04:09 PM CT, we began experiencing an elevated level of API errors on the creation of new Transfers in the Dwolla API. Our engineering team is actively investigating the cause and working towards a resolution. We apologize for the inconvenience and will provide an update shortly.
Mar 21, 16:32 CDT

Mar 20, 2025

No incidents reported.

Mar 19, 2025

No incidents reported.

Mar 18, 2025

Delay in processing ACH transactions and delivery of related webhooks in production

Resolved - This incident has been resolved. All transfers statuses have been updated and webhooks are being delivered.
Mar 18, 09:56 CDT

Update - The scheduled 9:00 AM CT Same Day ACH processing completed successfully. While the core ACH processing is functioning, there are still delays in webhook delivery. We will post another update as soon as the issue is resolved.
Mar 18, 09:16 CDT

Identified - We have experienced a delay 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 are expected to update today.

Our support team is working as quickly as possible to recover from this and avoid downstream impacts with the 9:00 AM CT export of Same-day ACH debit and credit transactions.

We will provide an update when the process completes, and we apologize for any inconvenience caused by this disruption.
Mar 18, 08:15 CDT

Mar 17, 2025

No incidents reported.

Mar 16, 2025

No incidents reported.

Mar 15, 2025

No incidents reported.

Mar 14, 2025

No incidents reported.