Hedera Sets Timeline To Deprecate Insecure HCS Mirror Endpoints

HomeNews* Hedera will permanently shut down insecure Hedera Consensus Service (HCS) Mirror Node endpoints by August 20, 2025.

• Two scheduled brownout periods on June 18 and July 23, 2025, will cause temporary service disruptions to affected endpoints.
• Users and projects must switch to the new .mirrornode.hedera.com:443 endpoint to maintain access.
• SDKs must be updated to at least Java v2.20.0, JS v2.22.0, or Go v2.23.0 for continued functionality.
• The mainnet-public.mirrornode.hedera.com address is unaffected and will remain active as an alias. Hedera has announced it will permanently deprecate its insecure Hedera Consensus Service (HCS) Mirror Node endpoints by August 20, 2025.

• Advertisement - The change aims to improve security standards for all users relying on these endpoints. The company will conduct a series of scheduled brownouts before the final shutdown to ensure users have time to adapt.

According to the company’s published timeline, the first brownout will start on June 18, 2025, lasting one hour from 10:00 AM Central Standard Time. A second brownout is scheduled for July 23, 2025, extending for 12 hours.

Users should expect significant service interruptions during these windows. After the brownouts, Hedera will permanently remove access to the insecure endpoints on August 20, 2025.

“The APIs have transitioned from the legacy hcs..mirrornode.hedera.com:5600 endpoints to the new .mirrornode.hedera.com:443 endpoints. Older SDK versions are also affected by this change as they use the legacy HCS mirror node endpoints.” stated the company in its official communication. The affected users must update their SDKs or configurations to continue using the service.

SDK users working with Hedera systems must upgrade to at least Java SDK v2.20.0, JS SDK v2.22.0, or Go SDK v2.23.0. Projects using older endpoint formats like hcs..mirrornode.hedera.com:5600 should shift to the new .mirrornode.hedera.com:443 endpoint immediately. The address mainnet-public.mirrornode.hedera.com will remain functional and acts as an alias for mainnet.mirrornode.hedera.com.

By making these changes, Hedera aims to increase both stability and security for its users. For help or questions, the company directs users to its Discord channel.

• Advertisement - These updates are part of Hedera’s continuing efforts to maintain operational security and reliability for developers and organizations utilizing its network.

Previous Articles:

• Strategy Launches STRD Preferred Stock With 10% Yield, No Fees
• Google Chrome to Distrust Chunghwa Telecom, Netlock Certificates
• Ethereum Foundation Restructures R&D Teams With “Protocol” Division
• AUSTRAC Imposes $5,000 Limit on Crypto ATM Cash Transactions
• Ethereum Foundation Lays Off R&D Staff Amid Protocol Restructuring

• Advertisement -