Chainalysis Outage History

Chainalysis is up right now

Chainalysis had 46 outages in the last 2 years totaling 152h 40m of downtime — averaging 1.9 incidents per month.

There were 46 Chainalysis outages since June 20, 2025 totaling 152h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.chainalysis.com

Minor November 13, 2025

KYT API Errors on Withdrawal Attempts Endpoint

Detected by Pingoru
Nov 13, 2025, 10:12 PM UTC
Resolved
Nov 13, 2025, 10:54 PM UTC
Duration
41m
Affected: KYT API
Timeline · 2 updates
  1. monitoring Nov 13, 2025, 10:12 PM UTC

    The KYT withdrawal attempts endpoint experienced an increased 500s error rate between 21:36 UTC and 21:53 UTC today. We have implemented a solution that has reduced the error rate. We will monitor the situation to ensure stability. Next update at 10:00 UTC on November 14th.

  2. resolved Nov 13, 2025, 10:54 PM UTC

    This incident has been resolved. Please reach out to [email protected] if you require assistance or have any questions.

Read the full incident report →

Notice November 5, 2025

Intermittent Service Disruption

Detected by Pingoru
Nov 05, 2025, 09:22 AM UTC
Resolved
Nov 05, 2025, 11:22 AM UTC
Duration
1h 59m
Timeline · 2 updates
  1. monitoring Nov 05, 2025, 09:22 AM UTC

    Reactor + KYT products were impacted by a brief disruption today from UTC 09:09 - UTC 09:20. Currently, all products are operational. If you are having trouble accessing the products, please try clearing the browser cache. If you have any other questions, please feel free to contact [email protected].

  2. resolved Nov 05, 2025, 11:22 AM UTC

    This incident has been resolved and all services are fully operational. Customers may have experienced KYT API interruptions during UTC 09:09 and UTC 09:20. Please resubmit any transfers or withdrawals that did not go through during this time. If you require further assistance, please reach out to [email protected].

Read the full incident report →

Major October 31, 2025

KYT UI and API Outage

Detected by Pingoru
Oct 31, 2025, 02:29 PM UTC
Resolved
Oct 31, 2025, 04:27 PM UTC
Duration
1h 57m
Affected: KYT UI
Timeline · 4 updates
  1. investigating Oct 31, 2025, 02:29 PM UTC

    We are currently investigating a KYT outage affecting both the UI and API. We will provide more details as soon as we have them. We have no workaround to share at this time. Next update at 15:00 UTC

  2. identified Oct 31, 2025, 03:02 PM UTC

    We’ve identified the root cause of this issue and are actively working to implement a fix. Whilst the KYT UI is still down, some services have returned to normal (alerts APIs), and it appears that transfer APIs were unaffected by this incident. Other services are actively coming back online, and we expect all APIs to be back up and running momentarily. We will continue to monitor this and work to ensure services are restored to a healthy state. Next update at 17:00 UTC

  3. monitoring Oct 31, 2025, 03:42 PM UTC

    The issue has been resolved, and the KYT UI and APIs are now fully operational. We will continue to monitor the system performance, but if you are still experiencing any issues, please contact us at [email protected] Next update at 18:00 UTC

  4. resolved Oct 31, 2025, 04:27 PM UTC

    This incident has been resolved. We have confirmed that all services are fully operational. Should you continue to experience any issues, please contact the Support Team at [email protected].

Read the full incident report →

Minor October 5, 2025

Polygon data delay - Reactor

Detected by Pingoru
Oct 05, 2025, 11:38 AM UTC
Resolved
Oct 05, 2025, 12:48 PM UTC
Duration
1h 9m
Affected: Reactor
Timeline · 2 updates
  1. investigating Oct 05, 2025, 11:38 AM UTC

    We are investigating reports of Polygon data being around 8 hours delayed in Reactor. We have no workaround at this time. More details will be shared once we have them.

  2. resolved Oct 05, 2025, 12:48 PM UTC

    Polygon is now back to tip and customers should see no further delays in Polygon data in Reactor. If you experience any further issues please reach out to [email protected]

Read the full incident report →

Critical September 30, 2025

Errors on KYT UI and API

Detected by Pingoru
Sep 30, 2025, 10:28 AM UTC
Resolved
Sep 30, 2025, 03:19 PM UTC
Duration
4h 50m
Affected: KYT APIKYT UI
Timeline · 4 updates
  1. investigating Sep 30, 2025, 10:28 AM UTC

    We are currently investigating reports of a KYT outage. We will provide more details as soon as we have them, we have no workaround to share at this time.

  2. investigating Sep 30, 2025, 10:32 AM UTC

    We are currently investigating reports of a KYT outage. We will provide more details as soon as we have them, we have no workaround to share at this time. Next scheduled update at 13:00 UTC

  3. monitoring Sep 30, 2025, 11:13 AM UTC

    A fix has been implemented and all product features should be fully functioning once again. Our team will continue to monitor the platform to ensure stability. If you see any issues, please reach out to our support team at [email protected]

  4. resolved Sep 30, 2025, 03:19 PM UTC

    This incident is now classed as resolved. If you see any further issues please reach out to [email protected]

Read the full incident report →

Notice September 24, 2025

Error in opening KYT alerts in Reactor

Detected by Pingoru
Sep 24, 2025, 02:24 AM UTC
Resolved
Sep 24, 2025, 02:47 AM UTC
Duration
23m
Affected: KYT UI
Timeline · 2 updates
  1. investigating Sep 24, 2025, 02:24 AM UTC

    We have received reports of customers experiencing errors when opening KYT alerts in Reactor, and are currently investigating this. We will provide more information as it becomes available. Next Update at 04:00 UTC

  2. resolved Sep 24, 2025, 02:47 AM UTC

    The incident has been resolved. If you continue experiencing any issues, please reach out to [email protected]

Read the full incident report →

Minor September 16, 2025

API V1 Timeouts reported

Detected by Pingoru
Sep 16, 2025, 09:43 AM UTC
Resolved
Sep 17, 2025, 07:00 PM UTC
Duration
1d 9h
Affected: KYT API
Timeline · 3 updates
  1. investigating Sep 16, 2025, 09:43 AM UTC

    We have received reports of customers receiving timeout errors when calling v1/users/{user_id} we are actively investigating this and will have more to share as soon as we have the full details of the issue. Please be aware we do not have a workaround in place at this time.

  2. monitoring Sep 16, 2025, 04:09 PM UTC

    The response latency for v1/users/{user_id} is normal at this time. There was a rise in P99 response latency from Sep 16, 2:15 ET - 3:50 ET for KYT V2 APIs, which has since subsided to normal levels. While there are no ongoing issues, further investigation is taking place to identify the root cause and next steps.

  3. resolved Sep 17, 2025, 07:00 PM UTC

    API latencies have remained at normal levels since the earlier spike. We will continue working with our cloud providers to understand the root cause, but no further impact is expected. Please contact [email protected] if you have any questions or need further assistance.

Read the full incident report →

Notice September 11, 2025

KYT API errors

Detected by Pingoru
Sep 11, 2025, 04:00 PM UTC
Resolved
Sep 11, 2025, 04:00 PM UTC
Duration
—
Affected: KYT API
Timeline · 1 update
  1. resolved Sep 11, 2025, 04:00 PM UTC

    Between 14:58 UTC and 15:14 UTC, some requests to the KYT API returned 502 errors. The issue has since been resolved. Please contact [email protected] if you have any questions or need further assistance.

Read the full incident report →

Minor September 4, 2025

KYT API and UI Errors

Detected by Pingoru
Sep 04, 2025, 09:36 PM UTC
Resolved
Sep 05, 2025, 03:08 AM UTC
Duration
5h 32m
Affected: KYT APIKYT UI
Timeline · 6 updates
  1. investigating Sep 04, 2025, 09:36 PM UTC

    The KYT API and UI are experiencing higher error rates, starting at 21:13 UTC. We are investigating the root cause. Next update at 22:15 UTC.

  2. investigating Sep 04, 2025, 10:15 PM UTC

    We are continuing to investigate this issue. Next update at 00:00 UTC on September 5th.

  3. identified Sep 04, 2025, 10:39 PM UTC

    The issue has been identified, and we are working on a fix. Next update at 00:00 UTC on September 5th.

  4. identified Sep 05, 2025, 12:20 AM UTC

    We are still working on a fix for this issue. We will provide further updates as soon as more information becomes available. Please reach out to [email protected] if you need further assistance. Next update at 10:00 UTC on Sept 5th.

  5. monitoring Sep 05, 2025, 02:04 AM UTC

    We have released a fix, and we will continue to monitor our systems to ensure stability. Please contact [email protected] if you have any questions or need further assistance. Next update at 10:00 UTC on Sept 5th.

  6. resolved Sep 05, 2025, 03:08 AM UTC

    The incident has been resolved. If you require further assistance, please reach out to [email protected]

Read the full incident report →

Minor August 22, 2025

BSC on Storyline

Detected by Pingoru
Aug 22, 2025, 10:59 AM UTC
Resolved
Aug 23, 2025, 03:57 PM UTC
Duration
1d 4h
Affected: Stories
Timeline · 4 updates
  1. identified Aug 22, 2025, 10:59 AM UTC

    We have identified an issue where you may experience errors in Storyline when loading Binance Smart Chain transactions in the address panel. The root cause has been traced to an issue with the data provider for BSC. We’ll provide further updates as soon as more information becomes available

  2. identified Aug 22, 2025, 03:04 PM UTC

    The root cause has been identified and we are working on a resolution with the data provider. The next update will be at 19:00 UTC.

  3. identified Aug 22, 2025, 06:58 PM UTC

    We are continuing to work on a fix for this issue. Next update at 10:00 UTC on August 25th.

  4. resolved Aug 23, 2025, 03:57 PM UTC

    This incident has been resolved. If you require further assistance, please reach out to [email protected]

Read the full incident report →

Minor August 19, 2025

XLayer Data Delay

Detected by Pingoru
Aug 19, 2025, 10:02 PM UTC
Resolved
Aug 20, 2025, 11:12 PM UTC
Duration
1d 1h
Affected: KYT APIReactor
Timeline · 6 updates
  1. identified Aug 19, 2025, 10:02 PM UTC

    XLayer data is delayed in both Reactor and KYT due to node provider issues. Any KYT transfers registered in the past hour will be affected. We will provide further updates as soon as more information becomes available. Next update at 2:00 UTC on August 20th.

  2. identified Aug 20, 2025, 02:55 AM UTC

    We are still investigating the cause of this issue with our Node provider. We will provide further updates as soon as more information becomes available. Next update at 10:00 UTC on August 20th, 2025.

  3. identified Aug 20, 2025, 09:52 AM UTC

    We are still investigating the cause of this issue with our Node provider. We will provide further updates as soon as more information becomes available. Next update at 15:00 UTC on August 20th, 2025.

  4. identified Aug 20, 2025, 03:03 PM UTC

    We are still investigating this issue with our Node provider. We will provide further updates as soon as more information becomes available. Next update at 21:00 UTC on August 20th, 2025.

  5. identified Aug 20, 2025, 06:27 PM UTC

    We are continuing to work with our Node provider to fix the issue. Please reach out to [email protected] if you have any questions or require further assistance. Next update at 4:00 UTC on August 21st, 2025.

  6. resolved Aug 20, 2025, 11:12 PM UTC

    This incident has been resolved, and XLayer data is no longer delayed in Reactor and KYT. Please reach out to [email protected] if you have any questions or require further assistance.

Read the full incident report →

Minor August 7, 2025

TON Data Delay

Detected by Pingoru
Aug 07, 2025, 02:22 PM UTC
Resolved
Aug 07, 2025, 05:28 PM UTC
Duration
3h 5m
Affected: KYT APIReactor
Timeline · 2 updates
  1. investigating Aug 07, 2025, 02:22 PM UTC

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

  2. resolved Aug 07, 2025, 05:28 PM UTC

    The TON data delay in Reactor and KYT has been resolved. Any affected KYT transfers have been reprocessed. Please reach out to [email protected] if you have any questions or require further assistance.

Read the full incident report →

Notice August 5, 2025

Base Mainnet Stalled at Blockheight 33792346

Detected by Pingoru
Aug 05, 2025, 06:42 AM UTC
Resolved
Aug 05, 2025, 08:30 AM UTC
Duration
1h 47m
Affected: KYT APIReactor
Timeline · 2 updates
  1. identified Aug 05, 2025, 06:42 AM UTC

    We have been alerted to an ongoing issue with the Base Mainnet; it’s stalled at block height 33792346. This is affecting the Deposits, Withdrawals, Block Production, Flashbocks of the Base network operations. Customers should expect that this will impact interaction with Base on Chainalysis products such as Reactor and KYT for the affected Blocks. Existing blocks will not be impacted. This is out of the control of the Chainalysis team. We are monitoring the situation. Customers can follow the StatusPage for Base here: https://status.base.org/incidents/kdq3t8s13gfs We will continue to monitor the situation and provide updates as we get them.

  2. resolved Aug 05, 2025, 08:30 AM UTC

    This incident has been resolved. If you require further assistance, please reach out to [email protected]

Read the full incident report →

Notice July 30, 2025

Polygon Mainnet stall at block height 74,592,238

Detected by Pingoru
Jul 30, 2025, 12:22 PM UTC
Resolved
Jul 30, 2025, 07:02 PM UTC
Duration
6h 39m
Affected: KYT APIReactorStoriesKYT UIEntitiesInvestigations APIRapid Lookup
Timeline · 2 updates
  1. identified Jul 30, 2025, 12:22 PM UTC

    We have been alerted to an ongoing issue with the Polygon Mainnet; it's stalled at block height 74,592,238. This is affecting all Polygon network operations. Customers should expect that this will impact interactions with Polygon with Chainalysis products such as Reactor and KYT. This is out of the control of the Chainalysis team. We are monitoring the situation. Customers can follow the StatusPage for Polygon here: https://status.quicknode.com/incidents/cjqf5klxfbdh We will continue to monitor the situation and provide updates as we get them.

  2. resolved Jul 30, 2025, 07:02 PM UTC

    This incident has been resolved. If you require further assistance, please reach out to [email protected]

Read the full incident report →

Notice July 16, 2025

Chainalysis Academy not loading

Detected by Pingoru
Jul 16, 2025, 01:23 PM UTC
Resolved
Jul 16, 2025, 04:27 PM UTC
Duration
3h 3m
Affected: KYT APIReactorStoriesKYT UIEntitiesInvestigations APIRapid Lookup
Timeline · 3 updates
  1. investigating Jul 16, 2025, 01:23 PM UTC

    We are currently investigating reports that users are not able to access the Chainalysis Academy. Our team is investigating a solution, and we will keep you updated as soon as we have more information. We do not currently have a workaround to share. No other Chainalysis services are impacted. Next Scheduled updated at: 17:00 UTC

  2. monitoring Jul 16, 2025, 02:08 PM UTC

    A fix has been implemented, and users should now be able to access the Academy once again. We will continue to monitor the performance and will announce any further impacts here on the StatusPage. If you experience any issues, please reach out to [email protected]

  3. resolved Jul 16, 2025, 04:27 PM UTC

    This incident has now been fully resolved. If you have any issues accessing Academy, please reach out to [email protected]

Read the full incident report →

Notice July 15, 2025

Delayed Information on Reactor Transaction Explorer

Detected by Pingoru
Jul 15, 2025, 01:47 AM UTC
Resolved
Jul 15, 2025, 03:04 AM UTC
Duration
1h 16m
Affected: Reactor
Timeline · 2 updates
  1. investigating Jul 15, 2025, 01:47 AM UTC

    We are investigating an issue where the data in the “spent” column of the Reactor’s transaction explorer (TEX) for BTC is not being updated. We will provide further information when they become available. Next update at 05:00 UTC

  2. resolved Jul 15, 2025, 03:04 AM UTC

    This incident has been resolved. If you require further assistance, please reach out to [email protected]

Read the full incident report →

Notice July 3, 2025

KYT Service Disruption - Withdrawal Attempts API

Detected by Pingoru
Jul 03, 2025, 02:47 PM UTC
Resolved
Jul 03, 2025, 02:47 PM UTC
Duration
—
Affected: KYT API
Timeline · 1 update
  1. resolved Jul 03, 2025, 02:47 PM UTC

    The KYT Withdrawal Attempts API endpoint experienced elevated 500 errors between 2025-07-03 14.05-14.23 UTC. 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 [email protected] if you have any questions or require further assistance.

Read the full incident report →

Notice July 3, 2025

Error loading Graphs in Reactor & KYT API endpoint errors.

Detected by Pingoru
Jul 03, 2025, 09:47 AM UTC
Resolved
Jul 03, 2025, 12:56 PM UTC
Duration
3h 8m
Affected: KYT APIReactor
Timeline · 2 updates
  1. monitoring Jul 03, 2025, 09:47 AM UTC

    Due to a disruption in service from our cloud provider, some customers may have experienced errors when attempting to access graphs in Reactor. We also recorded elevated error rates for KYT API. These issues have been resolved, and no further errors should be displayed. We will continue to monitor the stability of the service and provide a further update when we are confident in the long-term stability. Next scheduled update at 14:00 UTC

  2. resolved Jul 03, 2025, 12:56 PM UTC

    This incident has now been resolved. If you experience any interruptions with your workflows, please reach out to [email protected] and we will support you.

Read the full incident report →

Notice June 25, 2025

KYT Service Disruption - UI and API

Detected by Pingoru
Jun 25, 2025, 09:35 PM UTC
Resolved
Jun 25, 2025, 09:35 PM UTC
Duration
—
Affected: KYT APIKYT UI
Timeline · 1 update
  1. resolved Jun 25, 2025, 09:35 PM UTC

    The KYT API and UI experienced elevated 500 errors across endpoints between 2025-06-25 20:13 - 20:23 UTC. The issue is now resolved. However, any customers without automatic retries in place will need to re-screen any withdrawal attempts and transfers that were affected by the issue. Please reach out to [email protected] if you have any questions or require further assistance.

Read the full incident report →