Historical record of incidents for Dfns
Report: "API requests erroring with 500 status"
Last updateThis incident has been resolved.
A fix has been rolled out. We are monitoring the system to make sure the incident is resolved.
We are seeing issues related to our authentication system, currently investigating
Report: "New users can't login with webauthn"
Last updateThis incident has been resolved.
This is fixed.
we are rolling back the environment until we have a fix ready
New users who are registering an account and a webauthn credentials can't login
Report: "Polygon Indexing"
Last updateThis incident has been resolved.
The issue has been identified and a fix is being implemented.
Report: "Intermitent request failures"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
Report: "Btc broadcast is failing"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue.
We have identified an issue with btc transaction broadcast. We are working on a fix
Report: "Tron Transfers Failing"
Last updateThis incident has been resolved.
We are continuing to monitor for any further issues.
A fix has been implemented and we're monitoring for any further issues.
We are continuing to work on a fix for this issue.
Native Tron transfers are failing, we've identified the issue and are working on a fix.
Report: "blockchain RPC provider down"
Last updateThis incident has been resolved.
A RPC node provider issue affects Algorand, Bitcoin, Litecoin, and Celo chains
Report: "Degraded Signing Services"
Last updateThis incident has been resolved.
A fix has been implemented and we're monitoring for any further issues.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
Report: "TON Indexing Paused"
Last updateThis incident has been resolved.
The issue has been identified and a fix is being implemented.
Report: "Blockchain Engine unreliable"
Last updateOne 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
Report: "Signing Engine 500s"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Report: "Elevated 500 rates"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
Report: "Alchemy DDoS Attack"
Last updateThis incident has been resolved.
One of vendors, Alchemy, is experiencing a DDoS attack which may delay blockchain indexing for some networks. More details from Alchemy are here https://status.alchemy.com/
Report: "This is an example incident"
Last updateWhen 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.
As you continue to work through the incident, update your customers frequently.
Let your users know once a fix is in place, and keep communication clear and precise.