Apr <var data-var='date'> 3</var>, <var data-var='time'>16:44</var> CDT Resolved - A fix has been deployed and the errors have stopped occurring.Apr <var data-var='date'> 3</var>, <var data-var='time'>16:21</var> CDT Investigating - We're investigating increased API 500 errors on the customers/{accoundId}/transfers and accounts/{accountId}/transfers endpoints. This affects the API and the Dashboard. We will provide updates as they are available.

Errors on the customers/{accoundId}/transfers endpoint

Mar <var data-var='date'>26</var>, <var data-var='time'>09:34</var> CDT Resolved - This incident has been resolved. All transfers statuses have been updated and webhooks have been delivered. There was no impact to the 9:00 AM CT export of Same-day ACH debit and credit transactions. All Same-day transfers have exported.Mar <var data-var='date'>26</var>, <var data-var='time'>07:51</var> CDT Investigating - 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.

Delay in processing ACH transactions and delivery of related webhooks

Mar <var data-var='date'>25</var>, <var data-var='time'>19:14</var> CDT Resolved - The fix is deployed and sandbox transfer search in the dashboard and api are functioning normally.Mar <var data-var='date'>25</var>, <var data-var='time'>17:38</var> CDT Update - A fix has been identified and is being deployed.Mar <var data-var='date'>25</var>, <var data-var='time'>17:05</var> CDT Identified - We have identified an issue impacting sandbox transfer searches via the dashboard and api. The team is working on a fix and will provide updates as they become available. This impacts the sandbox environment only.

Sandbox Transfer Searches Degraded

Mar <var data-var='date'>18</var>, <var data-var='time'>09:58</var> CDT Resolved - We experienced a brief disruption with the Sandbox API that impacted funding source creation and retrieval, as well as transfer creation and retrieval for all Sandbox users. The issue occurred between 9:06 AM CT and 9:27 AM CT and has since been resolved.

[Sandbox] Experienced degraded performance

Mar <var data-var='date'> 8</var>, <var data-var='time'>17:00</var> CDT Resolved - This incident is resolved. All pending instant payment statuses have been updated.Mar <var data-var='date'> 8</var>, <var data-var='time'>13:57</var> CDT Monitoring - A fix has been applied, and the team is processing the backlog of status updates. We will provide an update when this is completed.Mar <var data-var='date'> 8</var>, <var data-var='time'>13:23</var> CDT Investigating - We are currently investigating an issue with instant payments status updates. The Dwolla platform is currently able to successfully create and process instant payments, but their statuses are not being updated in our system. Clients using instant payments will see these statuses marked as "pending". We are actively investigating and will provide updates as we make progress.

Instant Payments Status Updates

Mar <var data-var='date'> 3</var>, <var data-var='time'>17:58</var> CST Resolved - ACH transfer statuses that were expected to update at 5pm have all been updated, and related webhooks are being delivered. This incident is resolved.Mar <var data-var='date'> 3</var>, <var data-var='time'>16:30</var> CST Update - The Federal Reserve is continuing to experience delays. This will delay the webhook delivery and API transfer status updates for ACH credit and debit transactions that are expected to update at 5pm today. The Dwolla team is monitoring this closely and will initiate the process as soon as possible.Mar <var data-var='date'> 3</var>, <var data-var='time'>15:05</var> CST Update - All affected ACH transfer statuses from this morning have been updated, and related webhooks are being delivered. Same-day ACH debit and credit transactions originally scheduled to settle at 11:00 AM CT are now expected to settle at 5:00 PM CT. The Dwolla team continues to monitor the systems and will provide an update later this afternoon.Mar <var data-var='date'> 3</var>, <var data-var='time'>11:57</var> CST Update - The Dwolla team has initiated the process to update ACH credit and debit transactions and send webhooks. Webhooks should begin arriving at client endpoints in the near future.Mar <var data-var='date'> 3</var>, <var data-var='time'>11:11</var> CST Update - The issues at the Federal Reserve continue to impact the Dwolla platform. The Dwolla team is monitoring this closely and will initiate internal processes to update ACH credit and debit transactions and send webhooks as soon as possible.Mar <var data-var='date'> 3</var>, <var data-var='time'>08:07</var> CST Monitoring - The issue is ongoing due to a disruption with Federal Reserve ACH processing. 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 will now export in the 1:00 PM CT file. We will continue to provide updates as more information becomes available.Mar <var data-var='date'> 3</var>, <var data-var='time'>07:23</var> CST 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. This may have an impact on the 9:00 AM CT export of Same-day ACH debit and credit transactions. We will provide an update as we have more information to share. We apologize for any inconvenience caused by this disruption.

Feb <var data-var='date'> 5</var>, <var data-var='time'>17:19</var> CST Resolved - The Fed experienced a delay processing our Same-Day ACH transactions that should have exported today at 3:00 PM CT. This impacts the webhook delivery and API transfer status updates for Same-Day ACH credit and debit transactions that were expected to process at 5:00 PM CT today. As a result, these transfers are now expected be processed tomorrow morning 02/06/2026. We apologize for the inconvenience.

Delay in processing Same-Day ACH transactions

Feb <var data-var='date'> 4</var>, <var data-var='time'>09:51</var> CST Resolved - The team has completed the Form 1099K corrections and filed them with the appropriate tax agencies. This incident is resolved.Feb <var data-var='date'> 2</var>, <var data-var='time'>17:54</var> CST Update - Most of the incorrect 1099K forms that were sent to end users were stopped before they were filed with tax agencies. These 1099K forms have been updated and filed. A small number of 1099K forms were filed with tax agencies and require corrections. The team is working through the corrections process. We will provide an update when this is complete.Jan <var data-var='date'>30</var>, <var data-var='time'>17:47</var> CST Update - We have resolved the issue that caused incorrect amounts. We intend to file the updated 1099K forms with the appropriate tax authorities on Monday morning to avoid any operational impact over the weekend. We will provide an update when this is complete.Jan <var data-var='date'>29</var>, <var data-var='time'>18:36</var> CST Update - We have sent an email to all affected end users explaining what happened and informing them that corrected Form 1099-K will be issued, sent to them, and filed with the appropriate tax authorities. We are working through the process to send the corrected 1099-K forms to end users, and we will get those sent and filed by the February 2, 2026 deadline. Note that Dwolla's payment platform and API are not impacted by this issue.Jan <var data-var='date'>29</var>, <var data-var='time'>16:42</var> CST Identified - Dwolla has issued some 1099k forms to end users with the amounts higher than expected. If your business has customers who are receiving a 1099k from Dwolla, they may have received a form 1099k with the wrong amount. The Dwolla team is aware of the issue and is taking steps to correct it. We will provide more information on the steps taken as it becomes available. Note that Dwolla's payment platform and API are not impacted by this issue.

Issued 1099K forms with inflated amounts

Jan <var data-var='date'> 5</var>, <var data-var='time'>20:21</var> CST Resolved - All delayed webhooks and customer notifications have been successfully sent. This incident is resolved.Jan <var data-var='date'> 5</var>, <var data-var='time'>18:35</var> CST Update - The team is currently processing the backlog of webhooks. We will provide an update when this is complete.Jan <var data-var='date'> 5</var>, <var data-var='time'>12:00</var> CST Monitoring - We are currently monitoring system health to ensure continued stability. Our team is now working through the recovery process for webhooks that were delayed or missed during the service interruption. We will provide an update once the backlog has been fully processed and all events have been delivered.Jan <var data-var='date'> 5</var>, <var data-var='time'>11:56</var> CST Identified - We have identified an issue causing a subset of webhooks to remain in a "Queued" or "Pending" state rather than being delivered to API consumer endpoints. Our engineering team has traced the issue to performance degradation within our processing infrastructure that began at approximately 1:30 AM UTC on Saturday, January 3rd. We have taken steps to isolate the affected components and have restored normal processing for new events. Impact: Webhooks generated between Saturday, Jan 3rd and Monday, Jan 5th may experience significant delays or may not have been sent yet. Current webhook traffic is processing normally.

Delay in delivery of webhooks and operational notifications

Nov <var data-var='date'>18</var>, <var data-var='time'>12:26</var> CST Resolved - This incident has been resolved.Nov <var data-var='date'>18</var>, <var data-var='time'>11:35</var> CST Update - The issue on Cloudflare's end appears to be resolved and API traffic is back to normal. We're continuing to monitor.Nov <var data-var='date'>18</var>, <var data-var='time'>10:24</var> CST Update - We are investigating a small percentage of traffic that is still being returned as errors by Cloudflare's system. While API functionality is largely back to normal, clients may still experience some errors. We will continue to work with Cloudflare to resolve this as soon as possible.Nov <var data-var='date'>18</var>, <var data-var='time'>08:54</var> CST Monitoring - Cloudflare has implemented a fix. We're seeing API and dashboard activity returning to normal. We will continue to monitor the systems.Nov <var data-var='date'>18</var>, <var data-var='time'>07:22</var> CST Identified - We are currently experiencing an issue with our API traffic related to the ongoing Cloudflare outage, being tracked at cloudflarestatus.com. A significant portion of requests to Dwolla's API are being returned by Cloudflare as errors. We are monitoring this situation closely and will provide updates as soon as possible.

API Errors from Upstream Provider

Nov <var data-var='date'>17</var>, <var data-var='time'>14:33</var> CST Resolved - This incident has been resolved.Nov <var data-var='date'>17</var>, <var data-var='time'>14:32</var> CST Update - We are continuing to monitor for any further issues.Nov <var data-var='date'>17</var>, <var data-var='time'>10:36</var> CST Monitoring - We are currently experiencing an issue affecting Instant Payments submitted through our API. Since approximately 7:58 AM CT, these payments have been processed as expected — meaning that funds are being successfully transferred to the intended bank accounts. However, their transfer status remains "pending" in our system, creating a discrepancy between the actual fund movement and the reported transaction state. The root cause has been identified, and we are actively implementing a fix to resolve the underlying issue. Note: To avoid unintended duplicate payments, please refrain from resubmitting these transactions, as the transfers are still being processed correctly. We appreciate your patience as we work to restore normal transfer status updates. Further updates will be provided as soon as they are available.

Delays in Instant Payments (RTP/FedNow) Status Updates

Oct <var data-var='date'>27</var>, <var data-var='time'>09:43</var> CDT Resolved - Due to this incident, some of the usual 9:00 AM CT export of Same-day ACH debit and credit transactions might have been delayed. The affected transactions, if any, will now be exported at 1:00 PM CT. All of the transfer related webhooks from this morning have now been delivered.Oct <var data-var='date'>27</var>, <var data-var='time'>09:09</var> CDT Monitoring - We have experienced a delay in the morning processing of ACH transactions on the platform. This impacted the webhook delivery and API transfer status updates for ACH credit and debit transactions that were expected to update this morning. Webhooks are currently being delivered and we are monitoring the results.

Aug <var data-var='date'>26</var>, <var data-var='time'>13:10</var> CDT Resolved - This incident has been resolved.Aug <var data-var='date'>26</var>, <var data-var='time'>09:32</var> CDT Monitoring - We have identified the cause of the degraded performance and have implemented a fix. Response times across the API are now improving.Aug <var data-var='date'>26</var>, <var data-var='time'>09:23</var> CDT Investigating - We are currently experiencing higher than normal response times on the /customers and /transfers endpoints and are working to resolve this issue. We'll update again when this issue has been resolved.

Intermittent high response times and timeouts on /customers and /transfers

Aug <var data-var='date'>13</var>, <var data-var='time'>20:30</var> CDT Resolved - Last night, beginning approximately at 8:27 PM CT. A recent change resulted in a temporary outage of our RTP service. This caused a backlog of transactions to accumulate and delayed the processing of some payments. Our engineering team identified the root cause and took immediate action. We successfully restored the service at approximately 8:45 AM CT. All affected payments have now been successfully processed, and the system is operating as expected. We have implemented a permanent fix to address the underlying issue and prevent a recurrence. We apologize for any inconvenience this may have caused and appreciate your patience.

Issues processing Real-Time Payment (RTP) transfers

Jul <var data-var='date'>29</var>, <var data-var='time'>09:15</var> CDT Resolved - This incident has been resolved. All transfer statuses have updated and related webhooks are being delivered.Jul <var data-var='date'>29</var>, <var data-var='time'>08:33</var> CDT Update - Due to this incident, the usual 9:00 AM CT export of Same-day ACH debit and credit transactions has been delayed. These transactions will now be exported at 1:00 PM CT.Jul <var data-var='date'>29</var>, <var data-var='time'>07:42</var> 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.

May <var data-var='date'>16</var>, <var data-var='time'>22:27</var> CDT Resolved - Our team has processed all pending notifications. The incident is resolved. Thank you for your patience.May <var data-var='date'>16</var>, <var data-var='time'>20:58</var> CDT Update - A fix has been deployed, and new notifications are being processed normally. Our team is working through a process to send the pending notifications that were generated from approximately 3:20pm through 7pm CT. We will update the incident when that is completed.May <var data-var='date'>16</var>, <var data-var='time'>17:00</var> CDT Identified - We are currently experiencing delays in sending certain operational notifications. This impacts only the email notifications themselves and does not affect the underlying transaction processing or any other parts of the platform. Affected Operational Notification: - MassPay completed emails - Some transfer completion and transfer failed emails Our team is actively investigating the cause, and we will provide further updates as we work to resolve this issue. Thank you for your patience.

[Production] Delays in Operational Notifications related to Transfers and Masspays

May <var data-var='date'>13</var>, <var data-var='time'>09:42</var> CDT Resolved - This incident has been resolved.May <var data-var='date'>13</var>, <var data-var='time'>01:02</var> CDT Monitoring - We are currently monitoring an issue in Production affecting several endpoints that power Secure Exchange, Open Banking, and Virtual Account Number (VAN) Creation. These endpoints were returning 500 Server Error responses between 1:02 AM CT and 9:11 AM CT, but are now showing signs of recovery after applying a fix. Affected endpoints include: /exchange-sessions /exchanges /exchange-partners POST /funding-sources (for token exchanges and VANs creation only) Note: Sandbox environments are not impacted, and testing continues to function as expected. We will continue to monitor the fix closely and provide further updates as needed. Thank you for your patience.

[Production] Secure Exchange, Open Banking, and VAN Creation API Errors

May <var data-var='date'>12</var>, <var data-var='time'>16:05</var> CDT Resolved - The status of all previously affected RTP transfers has been successfully updated to reflect the correct status. Webhooks have also been sent to notify of these status changes. Thank you for your patience and understanding as we worked to resolve this issue.May <var data-var='date'>12</var>, <var data-var='time'>14:29</var> CDT Update - Our team is now executing the status updates for the affected RTP transfers that remain in a pending state. This process is underway, and we will provide a final update once it is complete.May <var data-var='date'>12</var>, <var data-var='time'>12:59</var> CDT Update - We are continuing to work on updating the status of the previous RTP transfers that remain in a pending state. These transfers were affected before our recent fix, which has been successfully processing new RTP transfers since deployment. While we don’t have a precise ETA for when these status updates will be fully resolved, this is our top priority, and our team is actively working to correct the status of these affected transfers. Thank you for your continued patience and understanding as we work to fully resolve this issue.May <var data-var='date'>12</var>, <var data-var='time'>11:26</var> CDT Monitoring - We have implemented a fix for the RTP status issue. All new RTP transfers submitted are processing correctly and are reflecting the appropriate status. We are now working on updating the status of the 508 previously affected RTP transfers that remain in a "pending" state. We will provide further updates as this effort progresses. Thank you for your patience and understanding.May <var data-var='date'>12</var>, <var data-var='time'>10:01</var> CDT Identified - We are currently experiencing an issue affecting Real-Time Payments (RTP) submitted through our API. Since approximately 5:00 AM CT, these payments have been processing as expected — meaning that funds are being successfully transferred to the intended bank accounts. However, their transfer status remains "pending" in our system, creating a discrepancy between the actual fund movement and the reported transaction state. The root cause has been identified, and we are actively implementing a fix to resolve the underlying issue. Note: To avoid unintended duplicate payments, please refrain from resubmitting these transactions, as the transfers are still being processed correctly. We appreciate your patience as we work to restore normal transfer status updates. Further updates will be provided as soon as they are available.

[Production] Delays in Real-Time Payment (RTP) Status Updates

Apr <var data-var='date'>22</var>, <var data-var='time'>16:30</var> CDT Resolved - 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.

Experiencing elevated HTTP 500 Errors on Customers

Mar <var data-var='date'>27</var>, <var data-var='time'>17:27</var> CDT Resolved - This incident has been resolved.Mar <var data-var='date'>27</var>, <var data-var='time'>16:53</var> 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.

Experiencing issues retrieving some Customer resources

Mar <var data-var='date'>21</var>, <var data-var='time'>17:24</var> CDT 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 <var data-var='date'>21</var>, <var data-var='time'>16:50</var> CDT Monitoring - A fix has been implemented and we are monitoring the results.Mar <var data-var='date'>21</var>, <var data-var='time'>16:32</var> 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.

[Production] Elevated API Errors Creating New Transfers

Mar <var data-var='date'>18</var>, <var data-var='time'>09:56</var> CDT Resolved - This incident has been resolved. All transfers statuses have been updated and webhooks are being delivered.Mar <var data-var='date'>18</var>, <var data-var='time'>09:16</var> 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 <var data-var='date'>18</var>, <var data-var='time'>08:15</var> 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.

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

Feb <var data-var='date'>21</var>, <var data-var='time'>17:30</var> CST Resolved - On 2/21/2025, at approximately 5:28 PM CT, we identified an issue affecting RTP transfers, causing them to remain in a pending state longer than expected. The issue was resolved by 6:59 PM CT, and all impacted RTP transfers were successfully processed by 7:40 PM CT.

Feb <var data-var='date'> 7</var>, <var data-var='time'>17:42</var> CST 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 <var data-var='date'> 7</var>, <var data-var='time'>16:10</var> CST Identified - We are currently investigating elevated API error rates resulting in 500 errors. This began at approximately 3 PM CT.

[Production] Elevated API Errors

Jan <var data-var='date'>29</var>, <var data-var='time'>17:55</var> CST Resolved - This incident has been resolved.Jan <var data-var='date'>29</var>, <var data-var='time'>17:45</var> CST Monitoring - A fix has been implemented and we are monitoring the results.Jan <var data-var='date'>29</var>, <var data-var='time'>16:40</var> 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.

Is Dwolla down?

Dwolla status is UP

Lastest published events

Errors on the customers/{accoundId}/transfers endpoint

Delay in processing ACH transactions and delivery of related webhooks

Sandbox Transfer Searches Degraded

Dwolla Services, Components and Regions

Recent Dwolla events

Errors on the customers/{accoundId}/transfers endpoint

Delay in processing ACH transactions and delivery of related webhooks

Sandbox Transfer Searches Degraded

[Sandbox] Experienced degraded performance

Instant Payments Status Updates

Delay in processing ACH transactions and delivery of related webhooks

Get your FREE account now,
5 monitors included!

Is Dwolla down?

Dwolla status is UP

Lastest published events

Errors on the customers/{accoundId}/transfers endpoint

Delay in processing ACH transactions and delivery of related webhooks

Sandbox Transfer Searches Degraded

Dwolla Services, Components and Regions

Recent Dwolla events

Errors on the customers/{accoundId}/transfers endpoint

Delay in processing ACH transactions and delivery of related webhooks

Sandbox Transfer Searches Degraded

[Sandbox] Experienced degraded performance

Instant Payments Status Updates

Delay in processing ACH transactions and delivery of related webhooks

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!