Dwolla Outage History

Started Apr 22, 2025, 09:30 PM UTC· resolved Apr 22, 2025, 09:30 PM UTC

1. resolved Apr 22, 2025, 10:29 PM UTC

   We experienced a temporary outage that impacted the /customers endpoint. Between 4:29:45 AM and 4:34:16 AM CT, the system was returning HTTP 500 errors due to a brief disruption in service. The total duration of the impact was 4 minutes and 29 seconds. The issue has been resolved, and the system has been stable since 4:34:16 AM CT. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Mar 27, 2025, 09:53 PM UTC· resolved Mar 27, 2025, 10:27 PM UTC

1. identified Mar 27, 2025, 09:53 PM UTC

   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.

2. resolved Mar 27, 2025, 10:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 21, 2025, 09:32 PM UTC· resolved Mar 21, 2025, 10:24 PM UTC

1. investigating Mar 21, 2025, 09:32 PM UTC

   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.

2. monitoring Mar 21, 2025, 09:50 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 21, 2025, 10:24 PM UTC

   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 [email protected]. We apologize for the inconvenience.

Read the full incident report →

Started Mar 18, 2025, 01:15 PM UTC· resolved Mar 18, 2025, 02:56 PM UTC

1. identified Mar 18, 2025, 01:15 PM UTC

   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.

2. identified Mar 18, 2025, 02:16 PM UTC

   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.

3. resolved Mar 18, 2025, 02:56 PM UTC

   This incident has been resolved. All transfers statuses have been updated and webhooks are being delivered.

Read the full incident report →

Started Feb 07, 2025, 10:10 PM UTC· resolved Feb 07, 2025, 11:42 PM UTC

1. identified Feb 07, 2025, 10:10 PM UTC

   We are currently investigating elevated API error rates resulting in 500 errors. This began at approximately 3 PM CT.

2. resolved Feb 07, 2025, 11:42 PM UTC

   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 [email protected]. We apologize for the inconvenience.

Read the full incident report →

Started Jan 29, 2025, 10:40 PM UTC· resolved Jan 29, 2025, 11:55 PM UTC

1. investigating Jan 29, 2025, 10:40 PM UTC

   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.

2. monitoring Jan 29, 2025, 11:45 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jan 29, 2025, 11:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 16, 2024, 03:34 PM UTC· resolved Dec 17, 2024, 02:59 PM UTC

1. investigating Dec 16, 2024, 03:34 PM UTC

   At approximately 8pm Central Time on 12/14/2024, we began experiencing issues processing RTP transfers. RTP Transfer attempts in the API are failing with an HTTP 400 error. This issue only impacts users creating RTP transfers. We are currently actively investigating the issue. We apologize for any inconvenience this may cause and appreciate your patience as we work to resolve this issue.

2. identified Dec 16, 2024, 07:14 PM UTC

   The issue has been identified and a fix is being implemented.

3. identified Dec 16, 2024, 11:36 PM UTC

   We are continuing to roll out the fix that will restore RTP functionality for all funding sources created at Dwolla. The rollout is in progress and we will continue to monitor its progress until it completes.

4. monitoring Dec 17, 2024, 04:50 AM UTC

   RTP transfer functionality has been restored to all Dwolla funding sources.

5. resolved Dec 17, 2024, 02:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 04, 2024, 07:03 PM UTC· resolved Dec 04, 2024, 10:34 PM UTC

1. investigating Dec 04, 2024, 07:03 PM UTC

   We are observing elevated 500 error rates originating from our Cloudflare edge. We are actively working to identify the root cause of this issue and restore full API availability. A subset of Dwolla API consumers may experience intermittent failures when making requests. We apologize for any inconvenience this may cause and appreciate your patience as we work to resolve this issue.

2. resolved Dec 04, 2024, 10:34 PM UTC

   This incident has been resolved.

Read the full incident report →