Dwolla 中断历史

1. 2026年9月9日 UTC 11:50identified

   平台上ACH交易的晨处理出现延误. 这影响了网上交易交付和API的转账状况更新,用于ACH信用和借记交易,这些交易预计在今天更新。 即时付款也受到影响,而且在此期间正在失败。 这是与我们的银行伙伴连接中断的结果。 该伙伴确认了这一问题并正在积极努力加以解决。 目前我们没有ETA 请注意:9:00AM CT出口同日ACH的借项和信用交易可能受到影响. 我们将在后续最新情况中确认.

2. 2026年9月9日 UTC 13:12identified

   这个问题还在继续。 我们正在继续与我们的银行伙伴合作,争取解决,目前没有埃塔。 请注意:因此,这影响到9:00AM CT出口同日ACH借方和信用交易. 9:00 AM CT同日窗口会被错过,这些交易现在预计将以 1:00 PM CT 文件导出. 我们将继续在获得更多信息后提供最新情况.

3. 2026年9月9日 UTC 14:35identified

   即时付款已经收回。 自大约9:12AM CT以来,我们看到即时付款的处理成功。 早些时候在中断期间失败的即时付款没有完成,可能要重新审理。 ACH处理的拖延仍在继续。 Webhook 交付和API 转账状态更新 ACH 信用和借项交易仍然被推迟,我们正在继续与我们的银行伙伴合作解决。 请注意:9:00AM CT同一天的窗口被错过. 这些交易现在有望以 PM CT 文件导出 。 我们将继续在获得更多信息后提供最新情况.

4. 2026年9月9日 UTC 15:22monitoring

   资金开始清空,相关的网络呼号正在提供。 我们正在监测结果,因为澳大利亚儿童保健中心的转让状况不断得到更新。 即时付款继续正常进行.

5. 2026年9月9日 UTC 18:32resolved

   这一事件已经得到解决。 所有 ACH 传输状态已经更新,相关的网络用户已经发送。 从大约9:12AM CT开始,即时付款通常得到处理。 请注意:9:00AM CT出口同日ACH借方和信用交易被错过. 这些交易以 1: 00 PM CT 文件出口,预计在5:00 PM CT 结算. 我们为这种干扰所造成的任何不便而道歉.

自动翻译自官方事件更新。

1. 2026年9月1日 UTC 21:50identified

   我们发现一个导致HTTP 504在Sandbox API端点上出错并阻止了Sandbox仪表板登录的问题. 我们已经查明了问题,正在部署一个解决办法。 我们将在我们取得进展时提供最新情况.

2. 2026年9月1日 UTC 22:14resolved

   固定装置已经部署,事故已经解决.

自动翻译自官方事件更新。

1. 2026年8月13日 UTC 14:24investigating

   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.

2. 2026年8月13日 UTC 14:50resolved

   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.

1. 2026年7月22日 UTC 22:42resolved

   我们在沙盒环境中经历了一个影响webhook发送和仪表板登录功能的问题,时间在12:47pm CT到4:44pm CT之间. 这个问题现已得到解决.

自动翻译自官方事件更新。

1. 2026年7月13日 UTC 17:03investigating

   我们目前正在调查高误差率(HTTP 500),这些误差影响到对客户、资金来源和大规模付款API终点的要求。 对这些终点的一些请求可能失败或暂停。 我们的工程组正在积极调查 一旦掌握了更多信息,我们将立即提供最新情况.

2. 2026年7月13日 UTC 17:15monitoring

   已安装了固定装置,在受影响的终点和Dashboard上,误差率正恢复正常。 我们正在监测 以确认完全恢复.

3. 2026年7月13日 UTC 19:20resolved

   这个问题已经解决了.

自动翻译自官方事件更新。

1. 2026年6月11日 UTC 19:09investigating

   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.

2. 2026年6月11日 UTC 19:30monitoring

   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.

3. 2026年6月11日 UTC 19:45resolved

   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.

1. 2026年6月9日 UTC 21:04resolved

   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.

1. 2026年6月2日 UTC 11:38identified

   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.

2. 2026年6月2日 UTC 13:14resolved

   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.

1. 2026年5月14日 UTC 15:08identified

   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.

2. 2026年5月14日 UTC 18:17resolved

   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.

1. 2026年4月28日 UTC 16:43investigating

   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.

2. 2026年4月28日 UTC 16:55monitoring

   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.

3. 2026年4月28日 UTC 19:10resolved

   This incident has been resolved.

1. 2026年4月23日 UTC 20:25resolved

   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.

1. 2026年4月13日 UTC 15:38resolved

   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.

1. 2026年4月3日 UTC 21:21investigating

   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.

2. 2026年4月3日 UTC 21:44resolved

   A fix has been deployed and the errors have stopped occurring.

1. 2026年3月26日 UTC 12:51investigating

   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. 2026年3月26日 UTC 14:34resolved

   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.

1. 2026年3月25日 UTC 22:05identified

   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.

2. 2026年3月25日 UTC 22:38identified

   A fix has been identified and is being deployed.

3. 2026年3月26日 UTC 00:14resolved

   The fix is deployed and sandbox transfer search in the dashboard and api are functioning normally.

1. 2026年3月18日 UTC 14:58resolved

   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.

1. 2026年3月8日 UTC 18:23investigating

   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.

2. 2026年3月8日 UTC 18:57monitoring

   A fix has been applied, and the team is processing the backlog of status updates. We will provide an update when this is completed.

3. 2026年3月8日 UTC 22:00resolved

   This incident is resolved. All pending instant payment statuses have been updated.

1. 2026年3月3日 UTC 13:23identified

   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.

2. 2026年3月3日 UTC 14:07monitoring

   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.

3. 2026年3月3日 UTC 17:11monitoring

   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.

4. 2026年3月3日 UTC 17:57monitoring

   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.

5. 2026年3月3日 UTC 21:05monitoring

   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.

6. 2026年3月3日 UTC 22:30monitoring

   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.

7. 2026年3月3日 UTC 23:58resolved

   ACH transfer statuses that were expected to update at 5pm have all been updated, and related webhooks are being delivered. This incident is resolved.

1. 2026年2月5日 UTC 23:19resolved

   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.

1. 2026年1月29日 UTC 22:42identified

   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.

2. 2026年1月30日 UTC 00:36identified

   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.

3. 2026年1月30日 UTC 23:47identified

   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.

4. 2026年2月2日 UTC 23:54identified

   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.

5. 2026年2月4日 UTC 15:51resolved

   The team has completed the Form 1099K corrections and filed them with the appropriate tax agencies. This incident is resolved.