Sep <var data-var='date'> 9</var>, <var data-var='time'>13:32</var> CDT 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. Sep <var data-var='date'> 9</var>, <var data-var='time'>10:22</var> CDT 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. Sep <var data-var='date'> 9</var>, <var data-var='time'>09:35</var> CDT Update - 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. Sep <var data-var='date'> 9</var>, <var data-var='time'>08:12</var> CDT Update - 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. Sep <var data-var='date'> 9</var>, <var data-var='time'>06:50</var> CDT 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.

Delay in processing ACH transactions, Instant Payments, and delivery of related webhooks in production

Sep <var data-var='date'> 1</var>, <var data-var='time'>17:14</var> CDT Resolved - The fix has been deployed and the incident is resolved. Sep <var data-var='date'> 1</var>, <var data-var='time'>16:50</var> CDT Identified - We have identified an issue causing HTTP 504 errors on Sandbox API endpoints and preventing Sandbox dashboard logins. We have identified the problem and are deploying a fix. We will provide updates as we make progress.

[Sandbox] API and Dashboard Errors

Aug <var data-var='date'>13</var>, <var data-var='time'>09:50</var> CDT Resolved - This incident has been resolved. Instant Payments are now processing normally. The last UR01 error was observed at 9:33 AM CT. Transfers that failed with UR01 during the disruption did not complete and may be retried. We appreciate your patience. Aug <var data-var='date'>13</var>, <var data-var='time'>09:24</var> CDT Investigating - We are currently experiencing an issue affecting Instant Payments submitted through our API. Since approximately 7:35 AM CT, these payments have been failing with error code UR01. We are working with our partners to identify and resolve the issue. ACH transfers and other API functionality are not affected. Note: These transfers did not complete. Please wait to resubmit until we confirm service is restored. We appreciate your patience as we work to restore Instant Payments. Further updates will be provided as soon as they are available.

Failures in Instant Payments

Jul <var data-var='date'>22</var>, <var data-var='time'>13:00</var> CDT Resolved - We experienced an issue affecting webhook delivery and dashboard login functionality in the Sandbox environment between 12:47pm CT and 4:44pm CT. This issue is now resolved.

[Sandbox] Webhooks and dashboard unavailability

Jul <var data-var='date'>13</var>, <var data-var='time'>14:20</var> CDT Resolved - This issue is resolved. Jul <var data-var='date'>13</var>, <var data-var='time'>12:15</var> CDT Monitoring - A fix has been deployed and error rates are returning to normal across the affected endpoints and the Dashboard. We are monitoring to confirm full recovery. Jul <var data-var='date'>13</var>, <var data-var='time'>12:03</var> CDT Investigating - We are currently investigating elevated error rates (HTTP 500) affecting requests to the Customers, Funding Sources, and Mass Payments API endpoints. Some requests to these endpoints may fail or time out. Our engineering team is actively investigating. We will provide an update within as soon as we have more information.

Elevated API 500 errors on Customers, Funding Sources, and Mass Payments

Jun <var data-var='date'>11</var>, <var data-var='time'>14:45</var> CDT Resolved - The issue affecting the dashboard display for Operational Notification statuses has been fully resolved. All delivery statuses within the Dwolla Dashboard are now updating in real-time and accurately reflect historical deliveries. Thank you for your patience. Jun <var data-var='date'>11</var>, <var data-var='time'>14:30</var> CDT Monitoring - A fix has been implemented to resolve the status sync delay. The "Delivery Status" indicators within the Dwolla Dashboard are beginning to catch up and accurately reflect actual delivery states. We are actively monitoring the dashboard queues until all historical notification statuses are fully backfilled and up to date. As a reminder, actual email delivery to end-users was unaffected during this window. Jun <var data-var='date'>11</var>, <var data-var='time'>14:09</var> CDT Investigating - We have identified an issue causing the "Delivery Status" for Operational Notifications within the Dwolla Dashboard to lag or not update correctly. Please note: Outbound emails are successfully delivering to your end-users in real-time. This is strictly an interface reporting delay within the Dashboard "Notifications" tab. Your end-users are receiving their transactional and account alerts normally, and no action is required on your part. We are working to restore real-time status updates to the dashboard view.

Delayed Operational Notification Statuses in Dwolla Dashboard

Jun <var data-var='date'> 9</var>, <var data-var='time'>15:00</var> CDT Resolved - We experienced a brief service disruption in our Production environment between 3:14 PM and 3:35 PM CT. The issue was related to intermittent resource contention which impacted the processing of balance-related requests. This resulted in elevated error rates for: - Balance Inquiries: Retrieving account or funding source balances (/funding-sources/{id}/balance). System performance stabilized at 3:35 PM CT and error rates have returned to normal. This incident has been resolved.

Elevated HTTP 500 Errors on Balance Inquiries

Jun <var data-var='date'> 2</var>, <var data-var='time'>08:14</var> CDT Resolved - This incident has been resolved. All transfers statuses have been updated and webhooks are being delivered. Please note: As a result, this impacts the 9:00 AM CT export of Same-day ACH debit and credit transactions. These transactions will now export at 1:00 PM CT. Jun <var data-var='date'> 2</var>, <var data-var='time'>06:38</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. Due to today being a high processing day, we expect this issue to cause impacts with the 9:00 AM CT Same-day ACH debit and credit transactions.  These transactions will likely be delayed to the 1PM CT Same-day ACH window. Our support team is working as quickly as possible to recover from this. 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

May <var data-var='date'>14</var>, <var data-var='time'>13:17</var> CDT Resolved - The Federal Reserve experienced system issues this morning, causing a delay in Same-Day ACH processing. Same-Day ACH debit and credit transactions that were expected to clear at 12:00 PM CT will now clear at 5:00 PM CT. We apologize for any inconvenience caused by this disruption. May <var data-var='date'>14</var>, <var data-var='time'>10:08</var> CDT Identified - The FED has experienced system issues this morning causing a delay in Same Day ACH processing. Same-Day ACH debit and credit transactions that were expected to clear at 12:00 PM CT will be delayed. We are monitoring the situation and working with our partners, and will update this status when we have more information about when those transfers will be processed. We apologize for any inconvenience caused by this disruption.

Delay in Same-Day ACH Clearing

Apr <var data-var='date'>28</var>, <var data-var='time'>14:10</var> CDT Resolved - This incident has been resolved. Apr <var data-var='date'>28</var>, <var data-var='time'>11:55</var> CDT Monitoring - We experienced a service disruption in our Production environment between 11:25 AM and 11:36 AM CT. The issue was related to intermittent resource contention which impacted the processing of balance-related requests. This resulted in elevated error rates for: - Balance Inquiries: Retrieving account or funding source balances. - Transfer Requests: Initiating transfers, particularly those involving balance sources. System performance stabilized at 11:36 AM CT and error rates have returned to normal. We are continuing to monitor our systems to ensure sustained stability while we complete our internal review. Apr <var data-var='date'>28</var>, <var data-var='time'>11:43</var> CDT Investigating - We are currently investigating reports of intermittent failures and elevated error rates (500 Internal Server Errors) affecting balance checks and balance-sourced transfers within our Production API. Our engineering team is actively working to identify the root cause. We will provide an update as soon as more information is available.

Elevated HTTP 500 Errors on Balance Inquiries and Transfers

Apr <var data-var='date'>23</var>, <var data-var='time'>14:30</var> CDT Resolved - We experienced a temporary outage that impacted the /customers endpoint. Between 2:22:57 PM and 2:32:38 PM CT, the system was returning HTTP 500 errors due to a brief disruption in service. The issue has been resolved, and the system is stable. We apologize for any inconvenience this may have caused.

Elevated HTTP 500 Errors on Customers

Apr <var data-var='date'>13</var>, <var data-var='time'>10:38</var> CDT Resolved - We experienced a delay in Same-Day ACH processing. Same-Day ACH debit and credit transactions that were expected to clear at 12:00 PM CT will now clear at 5:00 PM CT. We apologize for any inconvenience caused by this disruption.

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.

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.

Is Dwolla down?

Dwolla status is UP

Lastest published events

Delay in processing ACH transactions, Instant Payments, and delivery of related webhooks in production

[Sandbox] API and Dashboard Errors

Failures in Instant Payments

Dwolla Services, Components and Regions

Recent Dwolla events

Delay in processing ACH transactions, Instant Payments, and delivery of related webhooks in production

[Sandbox] API and Dashboard Errors

Failures in Instant Payments

[Sandbox] Webhooks and dashboard unavailability

Elevated API 500 errors on Customers, Funding Sources, and Mass Payments

Delayed Operational Notification Statuses in Dwolla Dashboard