Is Chainalysis Down Right Now? Check if there is a current outage ongoing.

XRP transfers are delayed in Reactor and KYT. We will provide further updates as soon as more information becomes available. Next update at 15:00 UTC

We are investigating an issue where users are unable to log in to their accounts. We’ll provide further updates as soon as more information becomes available. Next update at 04:00 UTC

Due to an issue with our TRON node providers. TRON transactions are delayed in Reactor. We’ll provide further updates as soon as more information becomes available. Next update at 18:00 UTC

Between 2025-06-04 13:50 UTC and 15:00 UTC, direct and indirect exposure data were not populated for a subset of transfers registered to KYT across all networks. As a result, some alerts were missed. This applies to both the V1 and V2 workflows. The issue is now resolved, and we are working to re-process the impacted transfers, which we expect to complete in the next few hours. Next update 22:00 UTC.

This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require further assistance.

KYT users are experiencing a 404 error while attempting to open behavioural alerts. We recommend for users to click on the "View transfers" button to see the alert-related transfers. We are investigating the issue, which appears to be isolated to KYT UI. Next update at 14:00 UTC.

This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require further assistance.

KYT users are experiencing a 404 error while attempting to open behavioural alerts. We recommend for users to click on the "View transfers" button to see the alert-related transfers. We are investigating the issue, which appears to be isolated to KYT UI.Next update at 14:00 UTC.

The POST /v2/withdrawal-attempts endpoint returned 500 errors between 14:46 and 14:52 UTC today. The issue is now resolved, however, any customers without automatic retries in place will need to re-screen any withdrawal attempts that were affected by the issue. Please reach out to support@chainalysis.com if you have any questions or require further assistance.

The POST /v2/withdrawal-attempts endpoint returned 500 errors between 14:46 and 14:52 UTC today. The issue is now resolved, however, any customers without automatic retries in place will need to re-screen any withdrawal attempts that were affected by the issue.Please reach out to support@chainalysis.com if you have any questions or require further assistance.

This incident has been resolved. Please contact support@chainalysis.com if you have any questions or require further assistance.

All blockchain networks are up to date in Reactor. We are actively working on backfilling any blocks that may be missing since the start of the incident. Next update at 18:00 UTC on May 23rd.

We are continuing to work on a fix for Soneium in Reactor. Tron is up to date. We are actively working on backfilling any blocks that may be missing since the start of the incident. Next update at 10:00 UTC on May 23rd.

We are continuing to work on a fix for Tron and Soneium in Reactor. Bitcoin Cash and Solana are up to date. We are actively working on backfilling any blocks that may be missing since the start of the incident. Next update at 15:00 UTC on May 22nd.

We are continuing to work on a fix for this issue. Please reach out to support@chainalysis.com if you have any questions or require further assistance. Next update at 14:00 UTC on May 22nd.

We are continuing to work on a fix for the remaining networks. Next update at 22:00 UTC.

We are continuing to work on a fix for the Bitcoin Cash, Solana, Tron and Soneium data delays in Reactor. KYT was not impacted by the data delays. We are actively working on backfilling any blocks that may be missing since the start of the incident. Next update at 18:00 UTC.

A fix has been implemented and the data delays have recovered apart from Bitcoin Cash, Solana, Tron and Soneium. We will continue to fix the remaining delays and monitor our systems to ensure stability. Next update at 18:00 UTC.

We are continuing to work on a fix for the data delay issue. Currently, data for all UTXO blockchain networks are up to date apart from BCH. Next update at 18:00 UTC.

We have identified a data delay issue for BCH, BTC, TON, Zcash, Solana, Ethereum, Linea and Tron in Reactor. We are working on a fix for this issue. Next update at 14:00 UTC.

This incident has been resolved.Please contact support@chainalysis.com if you have any questions or require further assistance.

All blockchain networks are up to date in Reactor. We are actively working on backfilling any blocks that may be missing since the start of the incident. Next update at 18:00 UTC on May 23rd.

We are continuing to work on a fix for Soneium in Reactor. Tron is up to date. We are actively working on backfilling any blocks that may be missing since the start of the incident. Next update at 10:00 UTC on May 23rd.

We are continuing to work on a fix for Tron and Soneium in Reactor. Bitcoin Cash and Solana are up to date. We are actively working on backfilling any blocks that may be missing since the start of the incident. Next update at 15:00 UTC on May 22nd.

We are continuing to work on a fix for this issue. Please reach out to support@chainalysis.com if you have any questions or require further assistance.Next update at 14:00 UTC on May 22nd.

We are continuing to work on a fix for the remaining networks.Next update at 22:00 UTC.

We are continuing to work on a fix for the Bitcoin Cash, Solana, Tron and Soneium data delays in Reactor. KYT was not impacted by the data delays. We are actively working on backfilling any blocks that may be missing since the start of the incident. Next update at 18:00 UTC.

A fix has been implemented and the data delays have recovered apart from Bitcoin Cash, Solana, Tron and Soneium. We will continue to fix the remaining delays and monitor our systems to ensure stability.Next update at 18:00 UTC.

We are continuing to work on a fix for the data delay issue. Currently, data for all UTXO blockchain networks are up to date apart from BCH.Next update at 18:00 UTC.

We have identified a data delay issue for BCH, BTC, TON, Zcash, Solana, Ethereum, Linea and Tron in Reactor. We are working on a fix for this issue.Next update at 14:00 UTC.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing routine maintenance to Entity Risking products infrastructure, expecting a downtime of no longer than 5 minutes. Please retry in a few minutes if you receive any errors.

The Entity Risking product was impacted by a brief disruption earlier today from 11PM UTC - 11.35 PM UTC (2025-05-20). This has now been resolved, and all products are operational. If you have any other questions, please feel free to contact Support@chainalysis.com.

The Entity Risking product was impacted by a brief disruption earlier today from 11PM UTC - 11.35 PM UTC (2025-05-20). This has now been resolved, and all products are operational.If you have any other questions, please feel free to contact Support@chainalysis.com.

This incident has been resolved.

A fix has been implemented, and the data delays in KYT and Reactor have recovered. We will continue to monitor our systems to ensure stability. No action is required for customers. Please reach out to support@chainalysis.com if you have any questions or require further assistance. Next update at 10:00 UTC.

We are investigating an issue with XRP (Ripple) data delays in both KYT and Reactor. We’ll provide further updates as soon as more information becomes available. Next update at 10:00 UTC

This incident has been resolved.

A fix has been implemented, and the data delays in KYT and Reactor have recovered. We will continue to monitor our systems to ensure stability. No action is required for customers. Please reach out to support@chainalysis.com if you have any questions or require further assistance. Next update at 22:00 UTC.

We are investigating an issue with BCH and LTC data delays in both KYT and Reactor. We’ll provide further updates as soon as more information becomes available. Next update at 18:00 UTC

This incident is now resolved. If you have any questions, please let us know at support@chainalysis.com.

The issue has been fixed and we are monitoring the results. Please reach out to support@chainalysis.com if you have any questions or require further assistance. Next update will be at 17:00 UTC.

Storyline is currently experiencing data ingestion delays. The root cause has been identified as an issue with a data provider. Please reach out to support@chainalysis.com if you have any questions or require further assistance. Next update will be at 17:00 UTC.

This incident is now resolved. We will be correcting transactions with wrong output addresses in the coming days. No action is needed from customers. If you have any questions, please let us know at support@chainalysis.com

We are continuing to monitor for any further issues.

A fix has been implemented, and we will continue monitoring for further disruption. If you have any issues, please reach out to support@chainalysis.com

The team are confident they have identified the issue and are now working on confirming this and implementing a fix. We will share more details once we have more information. Next update at 17:00 UTC

We are still verifying that the fix is working and investigating the root cause of this issue. Next update at 13:00 UTC on April 10th.

We are still verifying that the fix is working and investigating the root cause of this issue. Next update at 01:00 UTC on April 10th.

We have implemented a fix which we believe will mitigate the issue, but we are still investigating the root cause. Once we verify the fix is working, we will begin updating any transactions that had the incorrect output_address. Next update at 22:00 UTC.

We are receiving reports that the output_address returned in the KYT API does not match the expected output_address based on the submitted index for some Bitcoin transfers. We are still investigating the root cause. No action is required from customers at this time. Next update at 22:00 UTC.

Recent KYT alerts were unavailable on the v1/alerts endpoint and the KYT UI for approximately an hour from 16:00 and 17:00 UTC. In addition, a number of 5XX errors occurred on the KYT API between 16:04 and 16:06 UTC. Both issues have since recovered. Customers who do not have retry measures in place for 5XX errors will need to manually re-register any transfers and withdrawals that encountered errors during this time. Please reach out to support@chainalysis.com if you require assistance or have any questions.

This incident has been fully resolved. If you experience any issues with the UI of KYT or our API, please get in touch with support@chainalysis.com for an investigation.

A fix has been implemented to resolve the issue of generated alerts not being displayed on the KYT UI and users not being able to assign alerts. Our team continues to monitor the issue and address any additional API call issues. If you have any issues at all related to this incident, please reach out to support@chainalysis.com Next update at 17:00 UTC

We have identified the issue in which new alerts have been generated but are not being displayed in KYT, and users are unable to assign alerts. We are working on a fix and will provide more information when it becomes available. Next update at 10:00 UTC

We are continuing to investigate the issue. We'll provide more information as soon it becomes available. Next update at 07:00 UTC

We are continuing to investigate the issue and will provide updates as soon as more information becomes available. Next update at 05:00 UTC

We are investigating an error with the V1 alerts endpoint in which new alerts are generated but not being shown. We will provide an update once we have more information. Next update at 03:00 UTC

KYT was down between 03:52 and 03:57 UTC, and the API was returning 5XX errors. The 5XX error is now resolved. Customers who do not have retry measures in place for 5XX errors will need to manually re-register any transfers and withdrawals that encountered errors during this time. Please reach out to support@chainalysis.com if you require assistance or have any questions

The KYT API was returning 5XX errors between 20:36 and 20:38 UTC. The issue is now resolved. Customers who do not have retry measures in place for 5XX errors will need to manually re-register any transfers and withdrawals that encountered errors during this time. Please reach out to support@chainalysis.com if you require assistance or have any questions.

This incident is now resolved. If you have any issues at all, please let us know at support@chainalysis.com

A fix has been implemented, and users should no longer have to ensure the correct capitalization of email addresses. We will continue monitoring this issue to ensure users have full access to their accounts. If you do have any issues logging in, please reach out to support@chainalysis.com

We continue to investigate login issues and will update this page as soon as we have more details. Please ensure your email address is entered accurately, including case sensitivity. If you're having trouble logging in, contact Support@chainalysis.com from your registered email for assistance. Next update at 17:00 UTC

We are investigating reports that users are having issues logging in with their correct credentials. While our team investigates this issue, please ensure you enter your email address correctly, including using case-sensitive characters. If you are unsure of how your email was registered and are having problems logging in, please get in touch with Support@chainalysis.com from your registered email address, and our team will be happy to help. We will update this page as soon as we have more details to share. Next update at 14:00 UTC

This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require further assistance.

We are now only a couple of hours behind with ingesting Solana data in Reactor. However, given that we are still working on processing a backlog of transactions, we will continue monitoring this until the data has caught up. Next update will be at 15:00 UTC on 14th February.

We are 1 and a half days behind with the data ingestion for Solana, but we have been able to implement further improvements to speed up the ingestion going forward. We have effectively seen an improved processing throughout and we will continue monitoring this until the data has caught up. Next update will be at 15:00 UTC on 13th February.

We are experiencing a 2 day delay with ingesting Solana data. We anticipate that it will still take some time for Reactor to catch up, therefore we will continue to monitor progress and provide an update within 24 hours. Next update at 15:00 UTC on Wednesday 12th February

We are still ingesting the delayed data and will continue monitoring the issue. Please reach out to support@chainalysis.com if you have any questions or require further assistance. Next update will be at 15:00 UTC

We are currently experiencing data ingestion delays for Solana in Reactor. The root cause has been identified, and mitigations are in place, which we monitor as we ingest all the delayed blocks. Please reach out to support@chainalysis.com if you have any questions or require further assistance. Next update will be at 11:00 UTC

This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require further assistance.

A fix has been implemented and BTC transfers are processing again. Data in KYT and Reactor are both currently catching up. We will monitor the situation to ensure stability. No action is required for customers; any affected KYT transfers will be reprocessed automatically. Next update at 14:00 UTC.

We are continuing to investigate the issue and will provide updates as soon as more information becomes available. Next update at 10:00 UTC

We are investigating an issue with BTC data delays in both KYT and Reactor. We’ll provide further updates as soon as more information becomes available. Next update at 09:00 UTC

Between 18:20 to 20:32 UTC, some customers integrated with the KYT API experienced up to 10% error rate on the /api/kyt/v1/users/{userId}/transfers/received endpoint, predominantly when registering Solana transfers. The issue is now resolved and no action is required from customers. Please reach out to support@chainalysis.com if you have any questions or require further assistance.

This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require further assistance.

A fix has been implemented and the “Exposure tab” is now working as intended again. We are monitoring the results. Next update at 17:30 UTC.

We are investigating an issue with the “Exposure tab” in Entity Risking generating an error message: “Sorry, something went wrong. Please contact support@chainalysis.com if the problem persists.” For some users, the “Exposure tab” is not displaying at all. Next update at 17:00 UTC.

This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require further assistance.

We are continuing to monitor for any further issues.

A fix has been implemented, and we are monitoring the results. Next update at 00:00 UTC on January 24th.

The KYT API withdrawal-attempts endpoint is currently returning 500 errors for some tokens. We have identified the issue and are currently working on a fix. Next update at 22:00 UTC.

This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require assistance.

We are continuing to work on a fix. Please reach out to support@chainalysis.com if you have any questions or require assistance. Next update at 23:30 UTC.

We are continuing to work on a fix for the issue. We’ll provide further updates as soon as more information becomes available. Next update at 19:30 UTC.

We have identified an issue where KYT is having errors processing Solana transfers when customers register using the Token Address and are working on a fix. We will update this page when the fix has been implemented. In the meantime, the workaround is to register Solana transfers with the System Address. Next update at 15:00 UTC

This incident has been resolved.

A fix has been implemented and the KYT API withdrawal-attempts endpoint should now be working as intended. We will continue to monitor to ensure stability. Please reach out to support@chainalysis.com if you need any further assistance. Next update at 00:00 on Saturday, December 21st.

The KYT API withdrawal-attempts endpoint is currently returning empty responses for the Tron network. We have identified the issue and are currently working on a fix. Next update at 19:00 UTC.

This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require assistance.

A fix has been implemented, and Solana data in KYT and Reactor are both currently catching up. We will monitor the situation to ensure stability. No action is required for customers; any affected KYT transfers will be reprocessed automatically. Next update at 12:00 UTC.

We are currently experiencing data delays for Solana in both KYT and Reactor. This issue is related to one of our external vendors, and we are actively working with them to resolve it. We’ll provide further updates as soon as more information becomes available. Next update at 24:00 UTC

This incident has been resolved. Please reach out to support@chainalysis.com if you need any further assistance.

We are currently investigating a higher number of errors and increased latency with Entity Risking API. We will post an update as soon as we have more information. Next update at 19:00 UTC

This incident has been resolved. Please reach out to support@chainalysis.com if you need any further assistance.

We have implemented a fix and are monitoring it to ensure stability. Please reach out to support@chainalysis.com if you continue experiencing any issues. Thank you!

We are aware of degraded performance in KYT and are investigating the issue. We will post an update as soon as we have more information. Next update at 08:00 UTC

We can confirm that all watcher emails in our backlog have been sent and notifications are now up to date. Please reach out to support@chainalysis.com if you experience any further issues. Thank you!

A fix has been implemented, and we continue monitoring the situation. We are sending out all watcher emails in our backlog. When all notifications are up to date, we will update this page again. The next scheduled update is at 20:00 UTC

We are investigating and have identified an issue that is preventing our Watcher emails from correctly triggering. No emails have been sent since 2024-11-27 T11:56:11.324 +00:00 We will update this page with the relevant information as we learn more. We do not currently have a workaround for this issue.

This incident has been resolved.

We are continuing to work on a full fix for this issue. KYT alert status can be updated by providing a mandatory comment. Please add a supporting comment when changing an alert's status in the alerts panel. In all other areas where you manage alerts, the functionality is working as expected and allows status changes without requiring a comment. The next scheduled update is at 20:00 UTC

Our team has made progress towards a full resolution but is still investigating some aspects of the issue. However, we can confirm that customers can now make comments. We continue to investigate all solutions that will allow status updates to be made at will. In the meantime, we have a workaround. To change the status of an alert, users will need to add a comment. This will allow the status update to be applied.

We are currently investigating this issue.

This incident has now been fully resolved. If you continue to have any issues at all, please reach out to support@chainalysis.com

We will continue to monitor the situation to ensure stability through the weekend. Please contact support@chainalysis.com if you need any assistance. Next update at 10:00 UTC on October 28.

Our team has made progress in identifying the root cause, and the withdrawal attempt endpoint has recovered. We’ll continue to monitor our systems to ensure stability. If you are still experiencing any issues, please contact us at support@chainalysis.com. Next update at 21:00 UTC.

The KYT withdrawal attempt endpoint is returning 500 errors in some instances. We are currently investigating this issue. For further questions, contact support@chainalysis.com. Next update at 17:00 UTC.

The incident has been resolved. If you experience any difficulties, please reach out to support@chainalysis.com.

A fix has been implemented, and we are monitoring the results. Next update at 24:00 UTC

The root cause has been identified. We are working on a resolution. The next update will be at 14:00 UTC.

We are continuing to investigate this issue.

We’re observing intermittent errors for the GET endpoint on the KYT API, our team is investigating the root cause. Some customers using the GET /api/kyt/v1/users/userid and GET /api/kyt/v1/transfers/received have received intermittent 500 error response. Customers experiencing this error should retry running the API calls to workaround the problem. For further questions contact support support@chainalysis.com. Next update at 22:00 UTC

This incident has been resolved.

We have implemented a fix to address the issue. Our teams will continue closely observing the system to ensure stability. We will provide further updates as needed. If you have any questions, please reach out to us at support@chainalysis.com.

We are continuing to work on restoring service to the EOS network alongside our providers following the unexpected hard fork. While the issue remains unresolved, we are making steady progress. We will provide further updates as we move forward. If you have any questions, please reach out to us at support@chainalysis.com. Next update at 22:00 UTC

We are working to restore service to the EOS network and working closely with our providers following an unexpected hard fork. Our current expectation is that we will be back at tip by 11:30am EST. We’ll continue to provide updates as we progress. If you have any questions, please reach out to us at support@chainalysis.com. Next update at 16:00 UTC

We are currently addressing issues with adding new EOS data across all products following the Spring 1.0 Hard Fork. We expect to be fully recovered in about a day and will provide updates as we progress. If you have any questions, please reach out to us at support@chainalysis.com. Next update at 14:00 UTC on September 27th.

This issue was identified as maintenance from one of our external vendors that we use to support a component of our login system. As this was a planned disruption by our vendor, we don’t anticipate any further issues. We apologize for any issue logging in during this maintenance window. If you have any additional questions or issues, please reach out to our Support team any time at support@chainalysis.com.

We are seeing no issues with user logins at this time. The duration of the reported intermittent login issues was approximately 30 minutes. We are continuing to investigate root cause.

We are currently receiving reports of intermittent login issues. Users who experience this issue may receive an error when trying to log in. We are working to identify the root cause and implement a solution and will provide more information within the hour.

This incident has been resolved.

We are aware of an issue with KYT's chat functionality and are working to implement a fix. For inquiries contact support via email support@chainalysis.com. Next update at 16:30 UTC.

This incident has been resolved. Please contact support@chainalysis.com if you continue experiencing any issues.

Corrective measures have been applied and we are continuing to monitor the results to ensure ongoing stability. Next update at 17:00 UTC.

The issue has been identified and we will provide more information as it becomes available. Next update at 17:00 UTC.

We are currently receiving reports of some customers having issues with receiving or using their OTP when logging in. We are working on identifying the issue and will provide more information as it becomes available. Next update at 11:00 UTC.

This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require further assistance.

The issue has been identified and a fix is being implemented. If you have any questions, please reach out to us at support@chainalysis.com. Next update at 17:00 UTC.

Solana is currently experiencing delays in Reactor. We are currently investigating the issue. If you have any questions, please reach out to us at support@chainalysis.com. Next update at 12:00 UTC.

This incident has been resolved. Please contact support@chainalysis.com if you continue experiencing any issues.

Corrective measures have been applied, and we are continuing to monitor the results to ensure ongoing stability. Please reach out to support@chainalysis.com if you have any questions or require assistance.

We have reopened this incident due to additional reports: To clarify, this update is due to an outage on a third-party service; search address, spotlight search and address details functionalities are not working for storyline customers. Users can still open their stories and add transactions as usual. Our team is back in contact with the third-party service and working together to bring back the functionality. Next update at 14:00 UTC

This incident has been resolved. Please contact support@chainalysis.com if you continue experiencing any issues.

Corrective measures have been applied and we are continuing to monitor the results of this to ensure ongoing stability. Please reach out to support@chainalysis.com if you have any questions or require assistance. Next update at 12:00 UTC on Sep 2nd.

Due to an outage on a third party service, search address, spotlight search and address details functionalities are not working for storyline customers. Users can still open their stories and add transactions as usual. Our team is in contact with the third-party service and working together to bring back the functionality. Next update at 12:00 UTC.

This incident has been resolved. Please reach out to support@chainalysis.com if you have any questions or require further assistance.

We have identified the issue and are monitoring the results of the implemented fix to ensure stability. Please reach out to support@chainalysis.com if you have any questions. Next update at 12:00 UTC on August 29th.

We are currently receiving reports of some customers having issues with receiving or using their OTP when logging in. We are working on identifying the issue and will provide more information as it becomes available. Next update at 23:00 UTC.

Between 00:00 and 00:52 UTC on 2024-08-27, a subset of withdrawal attempts for Pre-growth networks experienced an error. The issue is resolved. Please re-register any withdrawal attempts made during this time. Please reach out to support@chainalysis.com if you have any questions or require further assistance.

This incident has been resolved.

We were receiving reports of intermittent service disruptions for Reactor. We identified the cause and implemented a solution. Please reach out to support@chainalysis.com if you need any further assistance.

This incident has been resolved.

A fix has been fully processed for any new alert updates. Customers should not experience any issues updating new alerts. Regarding older alerts that were reverted to their original state, some may still need to be processed due to the volume of the affected alerts. We found approximately ~3% of alerts that might reflect the incorrect status. The backfill is completed and should reflect the correct status as of 07/17. We are updating the dependent systems, which will avoid reverting the statuses in future, which was observed on 7/18 for a small % of alerts. We expect this % to be very low but want to ensure it does not happen again. We are actively working on this. Until then, please follow the workaround if you notice an incorrect status. In the meantime, if you notice it again, a workaround is available. Please feel free to use bulk action/dismissal for the alerts. Avoiding bulk assignments on the older alerts also helps. Please reach out to support@chainalysis.com if you need any further assistance.

We are receiving reports that some Alert Statuses in KYT still show their original state despite customers dismissing them. We will continue to investigate, and we will have more to share as soon as possible. The next scheduled update is at 13:00 UTC

Algorand data is now up to date and this issue is resolved. Please reach out to support@chainalysis.com if you have any questions or require further assistance.

We are continuing to monitoring the results of the fix. Please reach out to support@chainalysis.com if you have any questions or require assistance. Next update time at 00:00 UTC on July 30th.

Algorand is currently experiencing delays in all Chainalysis products. A fix is in place and we expect it to catch up within the next hour or so. Please reach out to support@chainalysis.com if you have any questions or require assistance. Next update time at 00:00 UTC on July 30th.

This incident has been resolved.

We experienced a brief service disruption with KYT UI between 19:00 - 19:30 UTC. The issue is currently resolved. We are monitoring actively.

Between 17:20 and 18:20 UTC on 2024-07-24, a subset of transfers registered to Transaction Monitoring (KYT) experienced an increased processing time of up to an hour. The issue is now resolved and all transfers are processed. No action is required from customers at this time. Please reach out to support@chainalysis.com if you have any questions or require further assistance.

This incident has been resolved. If you experience any issues, please reach out to support@chainalysis.com

We are continuing to monitor the results of the implemented fix to ensure ongoing stability. Please reach out to support@chainalysis.com if you have any questions or require assistance. Next update at 23:00 UTC on July 19th.

We are continuing to monitor the results of the implemented fix to ensure ongoing stability. If you experience any issues, please contact support@chainalysis.com. Next update at 24:00 UTC

We are continuing to monitor the results of the implemented fix to ensure stability. Please reach out to support@chainalysis.com if you have any questions. Next update at 20:00 UTC on July 18th.

A fix for the identified issue has been implemented. We are currently monitoring the results to ensure stability. If you experience any issues, please contact support@chainalysis.com. Next update at 22:00 UTC

We have identified the root cause affecting the Entities UI and as a result, we have temporarily paused storing counterparties in the database. Counterparties won’t appear in the Counterparties tab for new screening activity. However, users can still see counterparties in the Entity Profile via the Activity tab. Our team is working on a solution for this issue and will monitor the situation to ensure stability. Please reach out to support@chainalysis.com if you have any questions or need further assistance. Next update at 18:00 UTC

Our team is still actively investigating the issue and exploring several potential causes. We have implemented measures to improve the performance of the Entities API. However, user interface issues persist. We will continue to provide updates as we make progress. Please reach out to support@chainalysis.com if you have any questions. Next Update at 12:00 UTC.

Entities is currently experiencing service degradation. As a result, some users might encounter loading errors in the Entities UI and 5xx errors when attempting to use the Entities API endpoint. Our team is actively investigating the issue to identify the root cause and implement a fix. Please reach out to support@chainalysis.com if you have any questions. Next update at 21:00 UTC.

Between 2024-07-16 21:04 and 21:20 UTC, some transfers submitted to KYT via the POST /v2/transfers workflow did not have the updatedAt field populated and related alerts generated, even if they were accessible via the UI. All impacted transfers are now processed, and the issue is resolved. Please contact support@chainalysis.com if you have any questions or require further assistance.

We have finished correcting all the old alerts that were affected. This issue is now resolved. Please reach out to support@chainalysis.com if you have any questions or need further assistance.

To reiterate, a fix has been fully processed for any new alert updates. Customers should not experience any issues updating new alerts. Regarding older alerts that were reverted to their original state; due to the volume of the affected alerts, some may not have been processed. We found approximately ~3% of alerts that might reflect the incorrect status. We are currently working to correct these remaining alert statuses, which could take up to a week to process. We will provide an update once it is completed. In the meantime, a workaround is available for affected customers; filtering the unreviewed tab with the creation date set to any time after July 11th, 2024, 1:00 UTC will allow you to view only the correct set of new unreviewed alerts and continue your investigations. Please reach out to support@chainalysis.com if you have any questions or need further assistance.

The fix has been fully processed for new alert updates. Customers should not experience issues in updating any new alerts now. As for the older alerts that were reverted to the original state, due to the volume of the affected alerts, some may not have been processed. We are working to move them to the correct status in the backend, and we will provide an update as soon as this is completed. We appreciate your patience while this is being corrected. If you have any questions, please reach out to support@chainalysis.com.

We know that the Alert Statuses in KYT are being reverted to their original state despite customers dismissing them. A fix has been implemented, and once the fix is processed, the alerts should return to the correct status. This could take a couple of hours; we will update this StatusPage once the fix is fully processed. No action is required from customers, but we appreciate your patience while this fix is being processed. If you have any questions, please reach out to support@chainalysis.com

A fix has been implemented. If you have any questions, please reach out to support@chainalysis.com.

We are continuing to work on a fix for this issue. If you have any questions or need further assistance in the meantime, please reach out to support@chainalysis.com. Next update at 10:00 UTC on July 17th.

Some Ethereum transfers may be missing in Graphs (Reactor), including some transfers from block range 18346098 - 19485118 and some transfers that occurred in the past 24 hours. We have identified the cause and are working on a fix. Next update at 22:00 UTC.

This incident has been resolved. Please contact support@chainalysis.com if you have any questions or need any further assistance.

We are continuing to monitor the implemented fix to ensure stability. If you experience any issues, please contact support@chainalysis.com. Next update at 17:00 UTC (27th June)

A fix has been implemented, and we continue monitoring it to ensure stability. If you experience any issues, please reach out to support@chainalysis.com Next update at 17:00 UTC (26th June)

We are experiencing a recurring intermittent service disruption that is impacting all products. We are working to identify the root cause and implement a stable solution. At this time, we do not have a workaround. We will share more updates as soon as we have them. Next update at 17:00 UTC

Reactor and KYT are functioning as expected. We will continue to monitor the situation to ensure stability. Please reach out to support@chainalysis.com if you have any questions or require further assistance. Next update at 14:00 UTC on June 25th, 2024.

Reactor and KYT service has resumed. We are currently working to identify the root cause. Next update at 17:00 UTC

We are currently experiencing a service disruption and are working to identify the root cause and implement a solution. Next update at 17:00 UTC

A fix has been implemented. If you experience any issues, please reach out to support@chainalysis.com

A fix has been implemented, and we continue monitoring it to ensure stability. If you experience any issues, please reach out to support@chainalysis.com

KYT UI is currently down due to an infrastructure issue, and we are actively investigating. Customers are unable to log in to KYT.

The incident is now resolved; all transfers that did not go through during the incident were re-processed. Customers do not need to take any action.

We are seeing processing delays for Bitcoin, Tron, Solana, XRP, and UTXOs. We have identified the issue and working on a fix. Next update at 18:00 UTC

We identified an issue today that resulted in errors with withdrawal requests, which subsequently failed between June 11 11:38 UTC and 12:22 UTC This has been resolved, and no further errors should be expected. If you have any questions, please reach out to support@chainalysis.com