Scorechain had 19 outages in the last 2 years totaling 214h 21m of downtime — averaging 0.8 incidents per month.
There were 19 Scorechain outages since November 13, 2024 totaling 214h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.
The Dogecoin blockchain synchronization is currently blocked. We are currently working on a fix, we'll keep you updated.
We have implemented a fix in our Dogecoin block parser. All Dogecoin servers have been fully restored and are up-to-date on the chain.
Hello, Due to an incident at one of our service providers, the TON blockchain synchronization is blocked at since Saturday, 21 February 2026 08:01 GMT. We are currently working on a workaround. Regards
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are now synced again with TON blockchain, Thanks for your patience.
We have identified an outage impacting access to Solana blockchain related components. We are actively working on a fix to restore access to Solana blockchain scoring. We will keep you updated.
A fix has been applied and Solana access is restored. We are currently monitoring stability.
This incident has been resolved.
Hello, Due to an incident at one of our service providers, the TON blockchain synchronization is blocked at block 1763470762. We are currently working on a workaround. Regards
The problem is now resolved. We apologize for the inconvenience.
Custom scores for entities and entity types are currently not applied in the scoring algorithm. Default scores have been used since a few hours ago. Our team is working to fix this as soon as possible. We will keep your informed
The issue has been resolved. Services are now back to normal. We apologize for any inconvenience caused.
We are currently monitoring the situation as Polygon node operators work to resolve an issue causing the blockchain to halt. At this time, no new blocks are being produced. We will provide updates as more information becomes available.
This incident has been resolved.
We are currently experiencing a delay of approximately 6 hours in importing blocks from the TRON blockchain. The issue has been identified, and a fix is currently being deployed. We are closely monitoring the situation and will provide updates as progress is made. Thank you for your patience and understanding.
A fix has been implemented, and the backlog is now being processed. We estimate that the delay will be fully resolved within approximately 3 hours. We are continuing to monitor the situation and will provide updates as needed. Thank you for your patience and understanding.
The issue causing a delay of approximately 6 hours in importing blocks from the TRON blockchain has been fully resolved. A fix was successfully implemented, and the backlog has been cleared. The system is now fully operational and up to date. Thank you for your patience during this incident.
We would like to inform you that we are currently experiencing issues with the risk scoring of UTXO-based assets such as Bitcoin, Litecoin, and similar blockchains. Please do not rely on the scoring and amounts for these assets at this time. Our technical team is actively working on resolving the issue, and we will notify you as soon as the situation is restored. We apologize for the inconvenience and thank you for your understanding.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
The incident has been resolved.
We’re currently experiencing a production issue affecting the search functionality. We sincerely apologize for the inconvenience and are actively working to resolve the issue as quickly as possible. In the meantime, the scoring feature is still fully operational. You can continue using it directly via the following link: - https://app.scorechain.com/address/{BLOCKCHAIN}/{ADDRESS_HASH} - https://app.scorechain.com/transaction/{BLOCKCHAIN}/{TRANSACTION_HASH}
The root cause have been identified and fully resolved. We apologize for the inconvenience.
At 11:20 PM CEST, we experienced a loss of connectivity to our primary database due to a network issue at one of our hosting providers. Our monitoring systems promptly alerted us, and our team began investigating immediately. Connectivity was restored at 11:50 PM CEST. During the outage, all services were impacted. This led to API call errors and delays in alert processing. The incident is now fully resolved, and all services have been restored. We are actively monitoring the situation to ensure continued stability. We apologize for the inconvenience and thank you for your patience.
We are currently experiencing an increase in 500 errors due to issues with an underlying provider. Our team is actively monitoring the situation and working on a resolution.
The situation has now returned to normal. We are continuing to monitor to ensure stability. Thank you for your patience.
We are experiencing slowness in Tron scoring analysis due to an unusually high volume on the Tron blockchain. We're investigating the cause of the delays.
We have implemented a fix that improves response times on TRON. We continue to monitor the platform's stability.
This incident has been resolved.
We are currently investigating slowness in the platform and API.
A recently deployed data importer has been identified as the cause and has been shut down to mitigate the issue. We are now working on a fix for the data importer.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Dear customers, We identified an issue causing slowness in our API, impacting performance for some users. Our team has implemented a fix, and we are actively monitoring the results to ensure full resolution. We appreciate your patience and will provide further updates if necessary. If you continue to experience issues, please reach out to our support team. Thank you for your understanding.
This incident has been resolved.
On February 10th, at 15:41 CET, our Bitcoin transaction scoring service experienced a total outage due to an orphan block on the Bitcoin blockchain. At 15:51 CET, we mitigated the issue by switching to a backup infrastructure, fully restoring the service. After resolving the underlying issue, we transitioned back to our primary production infrastructure. We apologize for any inconvenience and appreciate your understanding.
We are currently experiencing a major outage across the entire application due to an external service provider. We will keep you informed of further developments.
All components are fully operational again. We are continuing to monitor the situation.
This incident has been resolved.
Postmortem from our underlying provider : To meet the growing demands of our customers for bandwidth, we have successfully commissioned a new higher-capacity interconnection with one of our transit providers. The decommissioning of older, lower-capacity links caused an unforeseen routing loop on Monday, January 13, at 10:00 a.m. Our technical teams were immediately alerted. The incident was identified, and a corrective measure was implemented at 10:24 a.m. to enhance the reliability of this process and prevent any recurrence. Since this intervention, all services have been restored and are fully operational.
We are currently investigating timeouts impacting the Ripple blockchain on our infrastructure.
a fix has been implemented and we are monitoring the results.
Ripple component is stable since the fix. We'll implement improvements soon to enhance redundancy for Ripple blockchain.
We are currently experiencing a delay in importing blocks from the Solana blockchain. The current delay is approximately 4 days. We have implemented measures to catch up, but due to the high number of blocks generated per second on the Solana blockchain, it will take an estimated 48 hours to fully resolve the delay.
Catching up on the blockchain delay is taking longer than initially expected. A new strategy has been implemented to accelerate the process. As a first step, we have resumed live synchronization starting from block 304403632, which is proceeding as expected. Meanwhile, the import of missing blocks, from 303603887 to 304403632, is running in parallel and is expected to be fully completed over the weekend.
All missing blocks have been successfully imported, and the incident is now fully resolved. We apologize for any inconvenience caused and for the time it took to complete the resolution.
On November 13 at 21:25 UTC, a brief network interruption between components of our infrastructure triggered an automatic failover of our systems to a backup component. The time required for propagation to this component caused a 10-minute service interruption for the Login and Scoring components. Alerts from the Transaction Monitoring System were not interrupted but may have been delayed by 10 minutes. By 21:35 UTC, all services were fully restored.