blog

Deprecation of the Insecure Hedera Consensus Service (HCS) Mirror Node Endpoints

June 7, 2024
Michiel Mulders
Michiel Mulders
Developer Relations

Warning: This blog has been updated with a new deprecation timeline. Read the full details here.


Hedera is announcing the deprecation of the insecure Hedera Consensus Service (HCS) mirror node endpoints. This change is part of our ongoing commitment to enhance security and ensure the reliability of our services.

What’s the Change?

The APIs have transitioned from the legacy hcs.<env>.mirrornode.hedera.com:5600 endpoints to the new <env>.mirrornode.hedera.com:443 endpoints. Older SDK versions are also affected by this change as they use the legacy HCS mirror node endpoints.

  • Old: hcs.previewnet.mirrornode.hedera.com:5600
    New:
     previewnet.mirrornode.hedera.com:443
  • Old: hcs.testnet.mirrornode.hedera.com:5600
    New: testnet.mirrornode.hedera.com:443
  • Old: hcs.mainnet.mirrornode.hedera.com:5600
    New: mainnet.mirrornode.hedera.com:443

Who’s Affected?

The deprecation will impact the following groups:

  • Developers on Previewnet or Testnet: This change will affect you if you use proxies to access the HCS mirror node endpoints.
  • Exchanges and Wallets on Mainnet: Those utilizing the gRPC port 5600 to access the endpoints must transition to the new secure TLS ports.
  • SDK Users: Users of SDK versions lower than those listed below need to update to ensure continued functionality.

In general, anyone relying on the gRPC port 5600 to access HCS mirror node endpoints should prepare for this change.

Deprecation Timeline

  • Initial Notifications: Week of June 10th

  • Mid-cycle Reminder: Week of September 9th

  • Actual Deprecation: Week of November 11th (6 months from the initial notification)

Positive Impact of Deprecation

The deprecation of the HCS mirror node endpoints is a positive step towards:

  • Enhanced Security: Deprecating the insecure gRPC port and domain in favor of secure TLS domains and ports.

  • Improved Reliability: Ensuring all traffic is routed through secure and reliable channels.

By upgrading to the new endpoints, users will benefit from increased security and stability, ensuring a better overall experience when interacting with Hedera services.

We appreciate your cooperation and understanding during this transition period. If you have any questions or need support, please reach out on Discord.

Back to Blog

discover

See more articles

June 5, 2026

Block Streams replace the Record Stream by default starting September 2026: Action required by Mirror Node operators

Block streams replace record streams as the canonical network output format. Mirror node operators and consumers of record files must deploy v0.155.1 of the hiero-mirror-node, or a later cutover-compatible release,
Read More
June 1, 2026

Why MEV-resistance is not optional for institutional blockchain infrastructure

From FX collateral to wholesale CBDC pilots, institutions need provable ordering integrity. How Hedera’s MEV-resistant architecture meets the demands of regulated markets.
Read More
May 29, 2026

Invisible ubiquity is here

HederaCon 2026, findings from the Bank of England’s DLT Innovation Project, Project Acacia, CLPR, HashSphere GA, strategic investments, and final reports on Hedera usage and adoption.
Read More