Störungsverlauf von Dwolla

1. 1. September 2026 um 21:50 UTCidentified

   Wir haben ein Problem identifiziert, das HTTP 504-Fehler bei Sandbox-API-Endpunkten verursacht und Sandbox-Dashboard-Anmeldungen verhindert. Wir haben das Problem erkannt und stellen einen Fix bereit. Wir werden Updates bereitstellen, wenn wir Fortschritte machen.

2. 1. September 2026 um 22:14 UTCresolved

   Der Fix wurde bereitgestellt und der Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 13. August 2026 um 14:24 UTCinvestigating

   Wir haben derzeit ein Problem mit Instant Payments, die über unsere API eingereicht werden. Seit ca. 7:35 Uhr CT scheitern diese Zahlungen mit dem Fehlercode UR01. Wir arbeiten mit unseren Partnern zusammen, um das Problem zu identifizieren und zu lösen. ACH-Transfers und andere API-Funktionalitäten sind nicht betroffen. Hinweis: Diese Transfers wurden nicht abgeschlossen. Bitte warten Sie auf die erneute Einreichung, bis wir bestätigen, dass der Service wiederhergestellt ist. Wir schätzen Ihre Geduld, während wir daran arbeiten, Instant Payments wiederherzustellen. Weitere Updates werden bereitgestellt, sobald sie verfügbar sind.

2. 13. August 2026 um 14:50 UTCresolved

   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.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Juli 2026 um 22:42 UTCresolved

   Wir haben zwischen 12:47 Uhr CT und 16:44 Uhr CT ein Problem mit der Webhook-Zustellung und der Dashboard-Anmeldefunktion in der Sandbox-Umgebung festgestellt. Dieses Problem ist nun gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 13. Juli 2026 um 17:03 UTCinvestigating

   Wir untersuchen derzeit erhöhte Fehlerquoten (HTTP 500), die sich auf Anfragen an Kunden, Finanzierungsquellen und Massenzahlungen auswirken API-Endpunkte. Einige Anfragen an diese Endpunkte können fehlschlagen oder Timeout. Unser Ingenieurteam untersucht aktiv. Wir werden ein Update zur Verfügung stellen, sobald wir mehr Informationen haben.

2. 13. Juli 2026 um 17:15 UTCmonitoring

   Ein Fix wurde bereitgestellt und die Fehlerraten kehren über die betroffenen Endpunkte und das Dashboard hinweg wieder normal zurück. Wir überwachen die vollständige Erholung.

3. 13. Juli 2026 um 19:20 UTCresolved

   Dieses Problem ist gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 11. Juni 2026 um 19:09 UTCinvestigating

   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. 11. Juni 2026 um 19:30 UTCmonitoring

   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. 11. Juni 2026 um 19:45 UTCresolved

   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. 9. Juni 2026 um 21:04 UTCresolved

   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. 2. Juni 2026 um 11:38 UTCidentified

   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. 2. Juni 2026 um 13:14 UTCresolved

   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. 14. Mai 2026 um 15:08 UTCidentified

   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. 14. Mai 2026 um 18:17 UTCresolved

   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. 28. April 2026 um 16:43 UTCinvestigating

   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. 28. April 2026 um 16:55 UTCmonitoring

   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. 28. April 2026 um 19:10 UTCresolved

   This incident has been resolved.

1. 23. April 2026 um 20:25 UTCresolved

   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. 13. April 2026 um 15:38 UTCresolved

   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. 3. April 2026 um 21:21 UTCinvestigating

   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. 3. April 2026 um 21:44 UTCresolved

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

1. 26. März 2026 um 12:51 UTCinvestigating

   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. 26. März 2026 um 14:34 UTCresolved

   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. 25. März 2026 um 22:05 UTCidentified

   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. 25. März 2026 um 22:38 UTCidentified

   A fix has been identified and is being deployed.

3. 26. März 2026 um 00:14 UTCresolved

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

1. 18. März 2026 um 14:58 UTCresolved

   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. 8. März 2026 um 18:23 UTCinvestigating

   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. 8. März 2026 um 18:57 UTCmonitoring

   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. 8. März 2026 um 22:00 UTCresolved

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

1. 3. März 2026 um 13:23 UTCidentified

   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. 3. März 2026 um 14:07 UTCmonitoring

   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. 3. März 2026 um 17:11 UTCmonitoring

   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. 3. März 2026 um 17:57 UTCmonitoring

   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. 3. März 2026 um 21:05 UTCmonitoring

   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. 3. März 2026 um 22:30 UTCmonitoring

   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. 3. März 2026 um 23:58 UTCresolved

   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. 5. Februar 2026 um 23:19 UTCresolved

   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. 29. Januar 2026 um 22:42 UTCidentified

   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. 30. Januar 2026 um 00:36 UTCidentified

   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. 30. Januar 2026 um 23:47 UTCidentified

   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. 2. Februar 2026 um 23:54 UTCidentified

   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. 4. Februar 2026 um 15:51 UTCresolved

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

1. 5. Januar 2026 um 17:56 UTCidentified

   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.

2. 5. Januar 2026 um 18:00 UTCmonitoring

   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.

3. 6. Januar 2026 um 00:35 UTCmonitoring

   The team is currently processing the backlog of webhooks. We will provide an update when this is complete.

4. 6. Januar 2026 um 02:21 UTCresolved

   All delayed webhooks and customer notifications have been successfully sent. This incident is resolved.