Dfns had 26 outages in the last 2 years totaling 1795h 19m of downtime — averaging 1.1 incidents per month.
There were 26 Dfns outages since July 12, 2024 totaling 1795h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are seeing balances not update and are investigating the issue
We've identified the issue and are implementing a fix
A fix has been implemented
This incident has been resolved.
AWS UAE is having power disruptions impacting our services out of app.uae.dfns.io. If you use this region our services may be impacted as they work to restore power. https://health.aws.amazon.com/health/status
This incident has been resolved.
The Polygon network has identified issues with Bor causing potential halts in the network. https://status.polygon.technology/incidents/9ysh9zczb8ml
This incident has been resolved.
API requests are taking longer than normal and may result in a timeout
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating an issue preventing some customers to create new Canton wallets on the Dfns shared validator. Impacted customers get an "Internal Error" response.
The issue has been identified. A fix is now being developed and should be deployed in the next hours.
We are continuing to work on a fix for this issue. Tests are ongoing.
A fix has been implemented and will be deployed soon.
A fix has been implemented. We are monitoring the results.
This incident has been resolved.
Dfns is experiencing scaling issues impacting transactions signatures.
We are continuing to work on a fix for this issue.
We identified the issue and are working on a fix.
- New transactions processing is now back to normal. - Retried transfers backlog processing is still ongoing. We have identified mitigation scenarios to accelerate recovery
We are still experiencing difficulties with processing the signatures backlog. We are applying new mitigations to accelerate recovery. Some raw signature requests may still fail. New transactions with no policy approval required will process normally. Transactions currently Executing will be delayed but will be processed eventually. Transactions pending approval still need to be approved and then will fall into the backlog and be delayed. Transactions that are in a "Failed" status will not be processed and should be retried.
We have now fully processed the pending backlog. The system is now stable.
All systems have been running properly since 11am UTC.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Some users are having issues logging in. We are currently investigating the issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The polygon team is actively working on mainnet production patches. We will try to keep up as they continue to push out updates. Expect transaction notification delays.
This incident has been resolved.
We are seeing issues related to our authentication system, currently investigating
A fix has been rolled out. We are monitoring the system to make sure the incident is resolved.
This incident has been resolved.
New users who are registering an account and a webauthn credentials can't login
we are rolling back the environment until we have a fix ready
This is fixed.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have identified an issue with btc transaction broadcast. We are working on a fix
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Native Tron transfers are failing, we've identified the issue and are working on a fix.
We are continuing to work on a fix for this issue.
A fix has been implemented and we're monitoring for any further issues.
We are continuing to monitor for any further issues.
This incident has been resolved.
A RPC node provider issue affects Algorand, Bitcoin, Litecoin, and Celo chains
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we're monitoring for any further issues.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
One RPC provider experienced issues as a result the blockchain engine became unreliable. This got fixed after 69 minutes. Time started: 7/18/2024 - 10:30 AM Time ended: 7/18/2024 - 11:39 AM