Close Menu
    What's Hot

    Ethereum Leverage Reset Complete, Time For Market Re-Accumulation?

    November 30, 2025

    Ethereum price forms rare pattern ahead of Fusaka upgrade

    November 30, 2025

    Ethereum Fusaka Will Be ‘The Most Bullish Upgrade’ Ever

    November 29, 2025
    Facebook X (Twitter) Instagram
    • Home
    • About Us
    • Get In Touch
    • Privacy Policy
    Facebook X (Twitter) Instagram
    Digicoinvision.com
    • Altcoin
    • Bitcoin
    • Blockchain
    • Crypto News
    • Ethereum
    Digicoinvision.com
    Home»Blockchain»Polygon Experiences Finality Disruption Due to Bor/Erigon Node Bug
    Polygon Experiences Finality Disruption Due to Bor/Erigon Node Bug
    Blockchain

    Polygon Experiences Finality Disruption Due to Bor/Erigon Node Bug

    DigicoinvisionBy DigicoinvisionSeptember 10, 2025No Comments1 Min Read
    Share
    Facebook Twitter LinkedIn Pinterest Email

    Polygon is experiencing a temporary delay in consensus finality because of a bug affecting the Bor and Erigon nodes, according to an official incident report on its status page. 

    The issue, which began early on Wednesday, disrupted some Remote Procedure Call (RPC) services and caused apps built on the network to encounter access issues. While the Polygon blockchain remains live and continues producing blocks, a number of RPC providers and validators were forced to rewind to the last finalized block and resynchronize. 

    The Polygon team confirmed that the bug is preventing node progress for certain configurations. However, restarting the affected nodes has resolved the issue for some participants. “We see that a restart of nodes has fixed the issues for many validators and RPC providers,” Polygon said. 

    Engineers are collaborating with infrastructure providers to accelerate the debugging efforts and full functionality. The team clarified that the incident does not affect core chain operations and assured users of a swift recovery. 

    Cointelegraph reached out to Polygon Labs for comments but did not get a response by publication. 

    This is a developing story, and further information will be added as it becomes available.