- Detected by Pingoru
- May 14, 2026, 03:08 PM UTC
- Resolved
- May 14, 2026, 06:17 PM UTC
- Duration
- 3h 8m
Affected: Federal Reserve Services - FedACH
Timeline · 2 updates
-
identified May 14, 2026, 03:08 PM UTC
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.
-
resolved May 14, 2026, 06:17 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 04:43 PM UTC
- Resolved
- Apr 28, 2026, 07:10 PM UTC
- Duration
- 2h 27m
Affected: API - Production
Timeline · 3 updates
-
investigating Apr 28, 2026, 04:43 PM UTC
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.
-
monitoring Apr 28, 2026, 04:55 PM UTC
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 PDT and error rates have returned to normal. We are continuing to monitor our systems to ensure sustained stability while we complete our internal review.
-
resolved Apr 28, 2026, 07:10 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 08:25 PM UTC
- Resolved
- Apr 23, 2026, 07:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 23, 2026, 08:25 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Apr 03, 2026, 09:21 PM UTC
- Resolved
- Apr 03, 2026, 09:44 PM UTC
- Duration
- 22m
Affected: API - ProductionDashboard - Production
Timeline · 2 updates
-
investigating Apr 03, 2026, 09:21 PM UTC
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.
-
resolved Apr 03, 2026, 09:44 PM UTC
A fix has been deployed and the errors have stopped occurring.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 12:51 PM UTC
- Resolved
- Mar 26, 2026, 02:34 PM UTC
- Duration
- 1h 43m
Affected: API - Production
Timeline · 2 updates
-
investigating Mar 26, 2026, 12:51 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.
-
resolved Mar 26, 2026, 02:34 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 10:05 PM UTC
- Resolved
- Mar 26, 2026, 12:14 AM UTC
- Duration
- 2h 9m
Affected: API - SandboxDashboard - Sandbox
Timeline · 3 updates
-
identified Mar 25, 2026, 10:05 PM UTC
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.
-
identified Mar 25, 2026, 10:38 PM UTC
A fix has been identified and is being deployed.
-
resolved Mar 26, 2026, 12:14 AM UTC
The fix is deployed and sandbox transfer search in the dashboard and api are functioning normally.
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 02:58 PM UTC
- Resolved
- Mar 18, 2026, 02:58 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 18, 2026, 02:58 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 08, 2026, 06:23 PM UTC
- Resolved
- Mar 08, 2026, 10:00 PM UTC
- Duration
- 3h 37m
Affected: API - Production
Timeline · 3 updates
-
investigating Mar 08, 2026, 06:23 PM UTC
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.
-
monitoring Mar 08, 2026, 06:57 PM UTC
A fix has been applied, and the team is processing the backlog of status updates. We will provide an update when this is completed.
-
resolved Mar 08, 2026, 10:00 PM UTC
This incident is resolved. All pending instant payment statuses have been updated.
Read the full incident report →
- Detected by Pingoru
- Feb 05, 2026, 11:19 PM UTC
- Resolved
- Feb 05, 2026, 11:19 PM UTC
- Duration
- —
Affected: Federal Reserve Services - FedACH
Timeline · 1 update
-
resolved Feb 05, 2026, 11:19 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jan 29, 2026, 10:42 PM UTC
- Resolved
- Feb 04, 2026, 03:51 PM UTC
- Duration
- 5d 17h
Affected: Tax forms
Timeline · 5 updates
-
identified Jan 29, 2026, 10:42 PM UTC
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.
-
identified Jan 30, 2026, 12:36 AM UTC
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.
-
identified Jan 30, 2026, 11:47 PM UTC
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.
-
identified Feb 02, 2026, 11:54 PM UTC
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.
-
resolved Feb 04, 2026, 03:51 PM UTC
The team has completed the Form 1099K corrections and filed them with the appropriate tax agencies. This incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 05, 2026, 05:56 PM UTC
- Resolved
- Jan 06, 2026, 02:21 AM UTC
- Duration
- 8h 25m
Affected: API - Production
Timeline · 4 updates
-
identified Jan 05, 2026, 05:56 PM UTC
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.
-
monitoring Jan 05, 2026, 06:00 PM UTC
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.
-
monitoring Jan 06, 2026, 12:35 AM UTC
The team is currently processing the backlog of webhooks. We will provide an update when this is complete.
-
resolved Jan 06, 2026, 02:21 AM UTC
All delayed webhooks and customer notifications have been successfully sent. This incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 01:22 PM UTC
- Resolved
- Nov 18, 2025, 06:26 PM UTC
- Duration
- 5h 3m
Affected: API - ProductionDashboard - Production
Timeline · 5 updates
-
identified Nov 18, 2025, 01:22 PM UTC
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.
-
monitoring Nov 18, 2025, 02:54 PM UTC
Cloudflare has implemented a fix. We're seeing API and dashboard activity returning to normal. We will continue to monitor the systems.
-
monitoring Nov 18, 2025, 04:24 PM UTC
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.
-
monitoring Nov 18, 2025, 05:35 PM UTC
The issue on Cloudflare's end appears to be resolved and API traffic is back to normal. We're continuing to monitor.
-
resolved Nov 18, 2025, 06:26 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 17, 2025, 04:36 PM UTC
- Resolved
- Nov 17, 2025, 08:33 PM UTC
- Duration
- 3h 56m
Affected: API - Production
Timeline · 3 updates
-
monitoring Nov 17, 2025, 04:36 PM UTC
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.
-
monitoring Nov 17, 2025, 08:32 PM UTC
We are continuing to monitor for any further issues.
-
resolved Nov 17, 2025, 08:33 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 26, 2025, 02:23 PM UTC
- Resolved
- Aug 26, 2025, 06:10 PM UTC
- Duration
- 3h 47m
Affected: API - Production
Timeline · 3 updates
-
investigating Aug 26, 2025, 02:23 PM UTC
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.
-
monitoring Aug 26, 2025, 02:32 PM UTC
We have identified the cause of the degraded performance and have implemented a fix. Response times across the API are now improving.
-
resolved Aug 26, 2025, 06:10 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2025, 02:51 PM UTC
- Resolved
- Aug 14, 2025, 01:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 14, 2025, 02:51 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 16, 2025, 10:00 PM UTC
- Resolved
- May 17, 2025, 03:27 AM UTC
- Duration
- 5h 26m
Affected: API - Production
Timeline · 3 updates
-
identified May 16, 2025, 10:00 PM UTC
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.
-
identified May 17, 2025, 01:58 AM UTC
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.
-
resolved May 17, 2025, 03:27 AM UTC
Our team has processed all pending notifications. The incident is resolved. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- May 13, 2025, 06:02 AM UTC
- Resolved
- May 13, 2025, 02:42 PM UTC
- Duration
- 8h 40m
Affected: API - Production
Timeline · 2 updates
-
monitoring May 13, 2025, 02:26 PM UTC
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.
-
resolved May 13, 2025, 02:42 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 12, 2025, 03:01 PM UTC
- Resolved
- May 12, 2025, 09:05 PM UTC
- Duration
- 6h 3m
Affected: API - Production
Timeline · 5 updates
-
identified May 12, 2025, 03:01 PM UTC
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.
-
monitoring May 12, 2025, 04:26 PM UTC
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.
-
monitoring May 12, 2025, 05:59 PM UTC
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.
-
monitoring May 12, 2025, 07:29 PM UTC
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.
-
resolved May 12, 2025, 09:05 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2025, 10:29 PM UTC
- Resolved
- Apr 22, 2025, 09:30 PM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Mar 27, 2025, 09:53 PM UTC
- Resolved
- Mar 27, 2025, 10:27 PM UTC
- Duration
- 34m
Affected: API - ProductionAPI - SandboxDashboard - ProductionDashboard - Sandbox
Timeline · 2 updates
-
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.
-
resolved Mar 27, 2025, 10:27 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 21, 2025, 09:32 PM UTC
- Resolved
- Mar 21, 2025, 10:24 PM UTC
- Duration
- 52m
Affected: API - Production
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2025, 01:15 PM UTC
- Resolved
- Mar 18, 2025, 02:56 PM UTC
- Duration
- 1h 40m
Affected: API - Production
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Feb 07, 2025, 10:10 PM UTC
- Resolved
- Feb 07, 2025, 11:42 PM UTC
- Duration
- 1h 32m
Affected: API - Production
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Jan 29, 2025, 10:40 PM UTC
- Resolved
- Jan 29, 2025, 11:55 PM UTC
- Duration
- 1h 15m
Affected: Dashboard - Production
Timeline · 3 updates
-
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.
-
monitoring Jan 29, 2025, 11:45 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 29, 2025, 11:55 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 16, 2024, 03:34 PM UTC
- Resolved
- Dec 17, 2024, 02:59 PM UTC
- Duration
- 23h 24m
Affected: API - Production
Timeline · 5 updates
-
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.
-
identified Dec 16, 2024, 07:14 PM UTC
The issue has been identified and a fix is being implemented.
-
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.
-
monitoring Dec 17, 2024, 04:50 AM UTC
RTP transfer functionality has been restored to all Dwolla funding sources.
-
resolved Dec 17, 2024, 02:59 PM UTC
This incident has been resolved.
Read the full incident report →