​​​​​​​​​​​​​​​​​         

Physical Address

304 North Cardinal St.
Dorchester Center, MA 02124

Polygon suffers hour-long RPC disruption affecting block production; Heimdall hotfix to blame


The polygon The testing network (pos) suffer a Outage One hours on July 30 that disrupted app and users.

According to the CEO and polygon founder Sand nailsthe incident did not stop block production. I am

However, QuickNode Status reported that block production is stopped for an hour at block of block 74.592.238, echo other reports made by users on X…………….. DO YOU. I am

Hiccups Hiccup

In a post on X, nails said many RPC providers “and therefore the corresponding applications and users” in the face of two hours. At the same time, the chain “stuck and continues to produce processing users and processes of processing” for rpc unifjects.

Polyegrann data indicates the network generated a new block Two seconds later Block 74.592.238, as to picture the time, despite the block mistake showing the blocking installment in this height.

Nails tracked the incident to a hotfix and temporary pause in consensus (heimdall) layer attached to a recent update completion. The layer of the execution (bor) continued to run, but certain rpc shoots from synchronous after failure, creating level felony as they feel like a magazine.

I apologize for the final user impact and said polygon works with the suppliers “to bring to all speed,” waiting for no other troubleshooting.

Stock product arrested

Infrastructure operators described the same symptoms. QuickNode stated that the Mainnet has installed by its advantage point in the height of the block 74.592.238 and noticed that the new Heimdall v0.2.16 upgrade I was causing trouble with bor and herigon execution.

The company turns up on updates “up to another notice,” recommended operators, and began to refresh and reset the erigon instances to restore the service.

Page of a polygon state isolate the blame to heimdall-v2 network. The team said the heimdall veinnet devotive, Affecting vitilitility and checkpoint via heimdall apis, but emphasized there were no layer.

The engineers identified the problem and implement a correction before marking of the resident.

The timeline shows as the disruption stretches and spreading in the teams. Polygona open in 09:52 U3 U.TR 30:52 UP, Long, Identify the problem by 09:57, and reported raised at 11:01.

QuickNode has doubles a stall at 11:28, paused the Heimdall at 11:51 in the polygage in the polygage, and by 15:39 DICKE to cross the laws from online.

Nails characterized the episode as a coordination gap between consent and infrastructure rather than a protocol failure.

Mentioned in this item



Source link

Leave a Reply

Your email address will not be published. Required fields are marked *