Argyle had 26 outages in the last 2 years totaling 34h 40m of downtime — averaging 1.1 incidents per month.
There were 26 Argyle outages since June 12, 2025 totaling 34h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.
This incident has been resolved. We will continue to monitor the situation for any other potential disruptions.
We are currently investigating this issue.
Our engineers have completed migrating services to another region to avoid further outages from Google Cloud. This has restored our services, and we will continue to monitor the situation for any other potential disruptions.
This incident has been resolved.
Our engineering team have migrated critical services which partially restored functionality. Google Cloud is still facing significant disruptions that can cause slowness and intermittent errors in our services. https://status.cloud.google.com/incidents/4Qvmd4q81VnA9RirCMqV
Google Cloud has an ongoing incident affecting Persistent Disk which has impacted our services. Our engineering team are moving to implement their suggested mitigations. https://status.cloud.google.com/incidents/4Qvmd4q81VnA9RirCMqV
Let your users know once a fix is in place, and keep communication clear and precise.
As you continue to work through the incident, update your customers frequently.
When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.
Empathize with those affected and let them know everything is operating as normal.
We are continuing to monitor for any further issues.
We are currently investigating this issue.
API working again, we're monitoring the situation
This incident has been resolved.
We are continuing to investigate this issue.
We are currently investigating the issue.
Incident has been resolved.
Brief disruption to API was detected and fixed.
The fix is working. We will continue to monitor the issue.
This incident has been resolved.
Data latency issue identified for some event types. Root cause has been identified and engineers are working on a fix.
Webhooks are also affected and might be delayed. Fix has already been applied and we are monitoring the recovery process.
API is operational but connecting new accounts is impacted. There is a delay in new data propagation through the systems.
Issue has been identified and we are recovering the system. Some link account connections are successful but MFA authentications are not available.
The API is operational and returning data. However, we are seeing delays in syncing newly connected accounts. The engineering team has identified the issue and is implementing a fix.
Newly connected accounts are syncing, and their data can be retrieved via the API. Webhook delivery remains delayed.
All systems are operating as normal.
All systems have recovered and account connections have resumed.
The issue affecting Link and Console has been resolved.
We have identified and are investigating an outage that is causing issues with Console and Link.
We are currently experiencing elevated error rates. We are actively investigating and working to mitigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have identified and resolved an outage that caused issues with Console
We are observing issues with an external infrastructure vendor. There is no client impact, but we are monitoring the situation closely.
Issues have been resolved.
We're investigating an issue with Link
We have identified a potential issue and applied a fix, monitoring the results.
The issue has been resolved. All systems are operational.
We have identified the root cause, rolled out the fix, and are continuing to monitor previously affected components.
Issue has been solved.
Authentication failures for myadp
We are currently experiencing report generation delays of up to several minutes. We are actively investigating and working to mitigate this issue.
Underlying issue has been identified and fixed. Report generation proceeds in standard timeline again.
The account connection issues have been resolved.
We are currently experiencing issues connecting accounts. We are actively investigating and working to mitigate this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We are currently experiencing delays with file upload processing, it might take longer for users to upload files and for file synchronizations to complete.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing elevated error rates in link items endpoints. We are actively investigating and working to mitigate this issue.
We are seeing an increased error rate on the /v2/open-banking endpoints. Requests are failing at a rate above normal baseline, impacting open banking account connections and data retrieval for affected users.
We have identified the issue and deployed a fix via a new release. Error rates on /v2/open-banking have returned to baseline and requests are succeeding normally. We are moving this incident to monitoring while we confirm the fix holds. No further customer impact is expected. We will resolve the incident if metrics remain stable
This incident has been resolved.
Paystubs endpoint is currently unavailable. We have identified the cause as a vendor incident. We are working on potential fixes.
We are continuing to work on a fix for this issue.
The paystubs endpoint has been restored by shifting traffic to unaffected zones. The underlying vendor incident is still ongoing, but at this point the only remaining impact is slightly elevated data processing latency. We will continue to monitor and provide updates as the vendor incident progresses.
The vendor has confirmed the incident is resolved for the region we operate in. All affected endpoints, including paystubs, are back to normal error rates and data processing latency has recovered. We are monitoring to confirm full stability before closing this incident.
All affected endpoints are fully operational and the vendor incident is resolved for our region. This incident is now resolved. Thank you for your patience.
We are experiencing elevated error rates for orders submitted through the Encompass integration due to an upstream incident affecting the Encompass platform. Orders may fail or be delayed until service is restored.
Encompass services have been restored, and orders are processing successfully. We are monitoring results to confirm full recovery.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified as UI rendering limitation. The underlying data is synchronizing normally. We are working on a fix.
Fix has been implemented and released. Encompass plugin application might need a refresh of the page for new version to load and display documents again.
Incident has been resolved.
We experienced elevated errors rates in the Account Owner details in Argyle Banking. This was resolved on July 6th at 2:05pm EST.
We are currently experiencing delay on webhooks. We are actively investigating and working to mitigate this issue.
We have identified report generation is also presenting a higher error rate than usual. We are still actively investigating and working to mitigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.