
Chainalysis Status
Real-time updates of Chainalysis issues and outages
Chainalysis status is Operational
KYT API
KYT UI
Sentinel
You're checking on Chainalysis - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
No active incidents
Recently Resolved Incidents
We are investigating reports of an issue in KYT where the “Open in Reactor” button is greyed out for some users, preventing certain mature transfers from being opened in Reactor.
We will share another update as soon as we have more information.
Between 22:00 UTC and 23:30 UTC, KYT experienced an error in processing some Solana transfers. The issue is now resolved, and we are checking the number of affected transfers. No action is required from customers as the transfers will be reprocessed from our end.
If you experience any further issues or have any questions, please reach out to [email protected].
We are currently investigating an issue where Alerts for Sentinel are not generating correctly. A fix has been put in place, and we will continue to monitor this over the next 12 hours.
Next update at 10:00 UTC
Chainalysis Outage Survival Guide
Chainalysis Components
Chainalysis Crypto Compliance
KYT API
Between 22:00 UTC and 23:30 UTC, KYT experienced an error in processing some Solana transfers. The issue is now resolved, and we are checking the number of affected transfers. No action is required from customers as the transfers will be reprocessed from our end.
If you experience any further issues or have any questions, please reach out to [email protected].
KYT UI
We are investigating reports of an issue in KYT where the “Open in Reactor” button is greyed out for some users, preventing certain mature transfers from being opened in Reactor.
We will share another update as soon as we have more information.
Entities
Sentinel
We are currently investigating an issue where Alerts for Sentinel are not generating correctly. A fix has been put in place, and we will continue to monitor this over the next 12 hours.
Next update at 10:00 UTC