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
Feb 11, 2025

No incidents reported today.

Feb 10, 2025

No incidents reported.

Feb 9, 2025

No incidents reported.

Feb 8, 2025

No incidents reported.

Feb 7, 2025
Resolved - We have resolved the issue causing elevated API error rates and 500 errors that began at approximately 3 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.

Feb 7, 17:42 CST
Identified - We are currently investigating elevated API error rates resulting in 500 errors. This began at approximately 3 PM CT.
Feb 7, 16:10 CST
Feb 6, 2025

No incidents reported.

Feb 5, 2025

No incidents reported.

Feb 4, 2025

No incidents reported.

Feb 3, 2025

No incidents reported.

Feb 2, 2025

No incidents reported.

Feb 1, 2025

No incidents reported.

Jan 31, 2025

No incidents reported.

Jan 30, 2025

No incidents reported.

Jan 29, 2025
Resolved - This incident has been resolved.
Jan 29, 17:55 CST
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 29, 17:45 CST
Investigating - We're aware of the issue affecting Funding Sources pages in the Production Dashboard and are actively investigating. We'll provide an update as soon as we have more information.
Jan 29, 16:40 CST
Jan 28, 2025

No incidents reported.