CINXE.COM

<?xml version="1.0" encoding="UTF-8"?> <feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom"> <id>tag:status.optimism.io,2005:/history</id> <link rel="alternate" type="text/html" href="https://status.optimism.io"/> <link rel="self" type="application/atom+xml" href="https://status.optimism.io/history.atom"/> <title>Optimism Status - Incident history</title> <updated>2024-12-05T19:32:00.000+00:00</updated> <author> <name>Optimism</name> </author> <entry> <id>tag:status.optimism.io,2005:Incident/cm4bu5mvp000j3nmwwtix69ao</id> <published>2024-12-05T19:32:00.000+00:00</published> <updated>2024-12-05T19:32:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/cm4bu5mvp000j3nmwwtix69ao"/> <title>OP Mainnet Safe Head Stall</title> <content type="html"> Dec <var data-var='date'> 5</var>, <var data-var='time'>19:32:00</var> GMT+0 Identified - OP Mainnet experienced a safe head stall from \~19:30- 21:00 UTC. The incident is already resolved and the safe head has caught up.. Dec <var data-var='date'> 5</var>, <var data-var='time'>21:00:00</var> GMT+0 Resolved - This incident has been resolved.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/cm16xpn0900291jmnwtzesibp</id> <published>2024-09-17T21:30:00.000+00:00</published> <updated>2024-09-17T21:30:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/cm16xpn0900291jmnwtzesibp"/> <title>sepolia.optimism.io - public endpoint maintenance</title> <content type="html"> Sep <var data-var='date'> 17</var>, <var data-var='time'>21:30:00</var> GMT+0 Identified - We are doing maintenance on the OP Sepolia public endpoint. No downtime is expected but be aware in case of intermittent issues.. Sep <var data-var='date'> 17</var>, <var data-var='time'>21:30:01</var> GMT+0 Identified - Maintenance is now in progress. Sep <var data-var='date'> 17</var>, <var data-var='time'>22:30:00</var> GMT+0 Completed - Maintenance has completed successfully. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/cm0q0669w0031kb13uae3jju1</id> <published>2024-09-06T00:53:38.620+00:00</published> <updated>2024-09-06T00:53:38.620+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/cm0q0669w0031kb13uae3jju1"/> <title>OP Sepolia Unsafe Head Stall</title> <content type="html"> Sep <var data-var='date'> 6</var>, <var data-var='time'>00:53:38</var> GMT+0 Investigating - We are currently investigating this incident.. Sep <var data-var='date'> 6</var>, <var data-var='time'>00:59:12</var> GMT+0 Resolved - False alarm, no network degradation occurred. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/cm0mqh72p002t1e0wu6h27icq</id> <published>2024-09-03T17:58:58.119+00:00</published> <updated>2024-09-03T18:08:06.879+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/cm0mqh72p002t1e0wu6h27icq"/> <title>OP Mainnet Unsafe Head Stall</title> <content type="html"> Sep <var data-var='date'> 3</var>, <var data-var='time'>18:08:06</var> GMT+0 Identified - We have identified the cause of the stall, and are deploying a mitigation. Nodes may need to wait for the next safe head increase before they resume syncing.. Sep <var data-var='date'> 3</var>, <var data-var='time'>17:58:58</var> GMT+0 Investigating - We are currently investigating this incident.. Sep <var data-var='date'> 3</var>, <var data-var='time'>18:11:28</var> GMT+0 Monitoring - We have deployed the mitigations and the network is syncing again. At this time the network is fully operational.. Sep <var data-var='date'> 3</var>, <var data-var='time'>18:18:22</var> GMT+0 Resolved - This incident has been resolved.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clzsolqtt475023ggodxlu97vt1</id> <published>2024-08-13T17:00:00.000+00:00</published> <updated>2024-08-13T17:00:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clzsolqtt475023ggodxlu97vt1"/> <title>OP Sepolia chain halt</title> <content type="html"> Aug <var data-var='date'> 13</var>, <var data-var='time'>17:00:00</var> GMT+0 Investigating - We are investigating an OP Sepolia chain halt. All users are affected.. Aug <var data-var='date'> 13</var>, <var data-var='time'>17:18:24</var> GMT+0 Monitoring - The sequencer has caught up sequencing and the remaining network should pick up after the next safe head increase. This should resolve within the next few minutes.. Aug <var data-var='date'> 13</var>, <var data-var='time'>17:23:25</var> GMT+0 Resolved - This incident has been resolved, safe and unsafe chain are advancing normally. Thanks for your patience with us!. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clzmwbpb743935hun751rod9ys</id> <published>2024-08-09T16:02:56.369+00:00</published> <updated>2024-08-09T16:03:16.966+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clzmwbpb743935hun751rod9ys"/> <title>Proposals delay on mainnet</title> <content type="html"> Aug <var data-var='date'> 9</var>, <var data-var='time'>16:03:16</var> GMT+0 Identified - We have identified the problem and are working on a fix. . Aug <var data-var='date'> 9</var>, <var data-var='time'>16:15:38</var> GMT+0 Monitoring - We implemented a fix and are currently monitoring the result.. Aug <var data-var='date'> 9</var>, <var data-var='time'>16:02:56</var> GMT+0 Investigating - We are seeing a delay in our mainnet proposer instance submitting proposals on chain. . Aug <var data-var='date'> 9</var>, <var data-var='time'>16:18:28</var> GMT+0 Resolved - This incident has been resolved, proposals have resumed.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clzipmabv224474iyn7o0mr2cno</id> <published>2024-08-06T17:11:00.000+00:00</published> <updated>2024-08-06T17:11:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clzipmabv224474iyn7o0mr2cno"/> <title>OP Sepolia chain halt</title> <content type="html"> Aug <var data-var='date'> 6</var>, <var data-var='time'>17:11:00</var> GMT+0 Investigating - OP Sepolia experienced a halt of the unsafe head for around 6 minutes. We have intervened to bring the network back to health and will continue to monitor the situation. . Aug <var data-var='date'> 6</var>, <var data-var='time'>17:26:00</var> GMT+0 Monitoring - We have intervened to restore network health and will continue to monitor the situation.. Aug <var data-var='date'> 6</var>, <var data-var='time'>18:17:05</var> GMT+0 Resolved - issue has been resolved and network is healthy.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/clz752uf249371hzn1t7e90jiw</id> <published>2024-07-30T20:00:00.000+00:00</published> <updated>2024-07-30T20:00:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/clz752uf249371hzn1t7e90jiw"/> <title>OP Mainnet Infrastructure Maintenance</title> <content type="html"> Jul <var data-var='date'> 30</var>, <var data-var='time'>20:00:00</var> GMT+0 Identified - We are planning for a scheduled maintenance during that time. No downtime is expected.. Jul <var data-var='date'> 30</var>, <var data-var='time'>20:00:01</var> GMT+0 Identified - Maintenance is now in progress. Jul <var data-var='date'> 30</var>, <var data-var='time'>20:37:53</var> GMT+0 Completed - Maintenance was completed successfully. . Aug <var data-var='date'> 6</var>, <var data-var='time'>18:18:03</var> GMT+0 Completed - Maintenance has completed successfully.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clyysuita9049e2ogkidjhmn4</id> <published>2024-07-23T19:19:08.709+00:00</published> <updated>2024-07-23T19:19:08.709+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clyysuita9049e2ogkidjhmn4"/> <title>Sepolia chain halt</title> <content type="html"> Jul <var data-var='date'> 23</var>, <var data-var='time'>19:19:08</var> GMT+0 Investigating - Our team is investigating a chain halt on Sepolia. At this time, all users may experience problems interacting with the chain. We apologize for the inconvenience and will share an update once we have more information.. Jul <var data-var='date'> 23</var>, <var data-var='time'>19:23:02</var> GMT+0 Identified - Our team has identified the cause of the halt and is working on a fix.. Jul <var data-var='date'> 23</var>, <var data-var='time'>19:25:07</var> GMT+0 Monitoring - Our team has identified the cause of the chain halt, and has deployed a fix. We expect the chain to move again shortly. We鈥檒l continue to share updates as we have them.. Jul <var data-var='date'> 23</var>, <var data-var='time'>19:28:59</var> GMT+0 Resolved - Our team has resolved the chain halt, and the chain should now be fully operational for all users. If you continue to experience an issue, please let us know on Discord. Thanks for your patience with us!. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/clynmyyg110996d0n38xq7wa3c</id> <published>2024-07-16T20:00:00.000+00:00</published> <updated>2024-07-16T20:00:01.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/clynmyyg110996d0n38xq7wa3c"/> <title>OP Mainnet Infrastructure Maintenance</title> <content type="html"> Jul <var data-var='date'> 16</var>, <var data-var='time'>20:00:01</var> GMT+0 Identified - Maintenance is now in progress. Jul <var data-var='date'> 16</var>, <var data-var='time'>20:00:00</var> GMT+0 Identified - We are planning for a scheduled maintenance during that time to improve the reliability of our sequencer. No downtime is expected.. Jul <var data-var='date'> 16</var>, <var data-var='time'>17:41:19</var> GMT+0 Identified - maintenance is delayed by 2 hours, will begin 8pm gmt.. Jul <var data-var='date'> 16</var>, <var data-var='time'>20:18:25</var> GMT+0 Identified - Ran into an issue during maintenance resulting in short unsafe head stall. Change has been reverted. Continuing to monitor.. Jul <var data-var='date'> 16</var>, <var data-var='time'>20:31:01</var> GMT+0 Identified - We are experiencing issues with node sync. At this time users my experience degraded performance syncing nodes or processing transactions.. Jul <var data-var='date'> 16</var>, <var data-var='time'>20:36:13</var> GMT+0 Identified - We have completed the rollback, and sync should be back to normal. We will monitor for any further issues.. Jul <var data-var='date'> 16</var>, <var data-var='time'>20:40:48</var> GMT+0 Completed - We will postpone further maintenance until we root cause the issue mentioned earlier. At this time the network is fully operational.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/cly1i7enu105321boonasuz51h0</id> <published>2024-06-29T00:05:00.000+00:00</published> <updated>2024-06-29T00:05:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/cly1i7enu105321boonasuz51h0"/> <title>OP Sepolia: Batcher degraded performance</title> <content type="html"> Jun <var data-var='date'> 29</var>, <var data-var='time'>00:05:00</var> GMT+0 Investigating - Due to heightened L2 block size on OP Sepolia, the batcher is seeing some performance degradation. This is causing the safe head to progress more slowly than usual. We are currently investigating. . Jun <var data-var='date'> 30</var>, <var data-var='time'>14:28:07</var> GMT+0 Monitoring - We have identified and applied a potential fix for the batcher performance issue. We will continue to monitor the situation.. Jun <var data-var='date'> 30</var>, <var data-var='time'>15:54:23</var> GMT+0 Resolved - The safe head has now resumed normal operation. . </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clxwbetqv52458bbn68emxmh69</id> <published>2024-06-26T20:55:48.078+00:00</published> <updated>2024-06-26T20:55:48.078+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clxwbetqv52458bbn68emxmh69"/> <title>sepolia unsafe head stall - fixed</title> <content type="html"> Jun <var data-var='date'> 26</var>, <var data-var='time'>20:55:48</var> GMT+0 Monitoring - We were conducting some cluster maintenance and had unexpected short downtime. We have implemented a fix and are currently monitoring the result.. Jun <var data-var='date'> 26</var>, <var data-var='time'>21:28:08</var> GMT+0 Resolved - This incident has been resolved.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clxnipyv759364bhmsk2dwifoa</id> <published>2024-06-20T17:10:29.360+00:00</published> <updated>2024-06-20T17:10:29.360+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clxnipyv759364bhmsk2dwifoa"/> <title>Elevated Fees on OP Mainnet</title> <content type="html"> Jun <var data-var='date'> 20</var>, <var data-var='time'>17:10:29</var> GMT+0 Identified - We are currently experiencing elevated fees on OP Mainnet due to high blob fees on L1\. We are mitigating the issue by switching batch submission back to calldata. While the switch rolls out, users may experience higher fees than normal and the safe head may increase less often due to L1 congestion.. Jun <var data-var='date'> 20</var>, <var data-var='time'>17:17:06</var> GMT+0 Monitoring - We have performed the switch back to calldata. Users should observe a more stable safe head, as well as lower fees. We will switch back to blobs once the L1 congestion subsides.. Jun <var data-var='date'> 20</var>, <var data-var='time'>18:26:00</var> GMT+0 Monitoring - Blob data availability fees returned to stability. Batch submission is operational and utilizing blobs again. We will continue to monitor the L1 data fees for changes.. Jun <var data-var='date'> 20</var>, <var data-var='time'>21:06:10</var> GMT+0 Resolved - L2 fees are no longer elevated, L1 blob fees are trending down.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clxao33pp71868brn587ng28oo</id> <published>2024-06-11T17:19:40.273+00:00</published> <updated>2024-06-11T18:09:04.328+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clxao33pp71868brn587ng28oo"/> <title>op-sepolia unsafe head stall</title> <content type="html"> Jun <var data-var='date'> 11</var>, <var data-var='time'>18:09:04</var> GMT+0 Resolved - This incident has been resolved.. Jun <var data-var='date'> 11</var>, <var data-var='time'>17:19:40</var> GMT+0 Investigating - Our team is investigating a sequencer outage on op-sepoolia. At this time, nodes will experience an unsafe head stall. We apologize for the inconvenience and will share an update once we have more information.. Jun <var data-var='date'> 11</var>, <var data-var='time'>17:26:39</var> GMT+0 Identified - Our team has identified the cause of the unsafe head stall. The issue is the result of an outage in the L1 nodes used by the sequencer. At this time, users will continue to see a stall in block production and transactions will not be included.. Jun <var data-var='date'> 11</var>, <var data-var='time'>17:30:54</var> GMT+0 Monitoring - Our team has implemented a fix to resolve the unsafe head stall on op-sepolia and is monitoring the situation. Transactions are being included again and op-sepolia nodes should resume following the chain and seeing the unsafe head progress.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/clx0nz8nz6368beo9xslw3hsp</id> <published>2024-06-04T17:18:12.614+00:00</published> <updated>2024-06-04T17:18:12.614+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/clx0nz8nz6368beo9xslw3hsp"/> <title>OP Sepolia Cluster Upgrade</title> <content type="html"> Jun <var data-var='date'> 4</var>, <var data-var='time'>17:18:12</var> GMT+0 Identified - We are upgrading our OP Sepolia cluster. We expect minor service interruptions while the upgrade completes. We expect the upgrade to take approximately 20 minutes.. Jun <var data-var='date'> 4</var>, <var data-var='time'>18:35:37</var> GMT+0 Completed - The cluster upgrade is complete.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clwzeb0j175086b6og85tygcgu</id> <published>2024-06-03T20:00:24.596+00:00</published> <updated>2024-06-03T20:00:24.596+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clwzeb0j175086b6og85tygcgu"/> <title>Unsafe head stall on op-mainnet</title> <content type="html"> Jun <var data-var='date'> 3</var>, <var data-var='time'>20:00:24</var> GMT+0 Investigating - Our team is investigating an unsafe head stall on op-mainnet. At this time, node operators may experience a delay in receiving unsafe blocks. We apologize for the inconvenience and will share an update once we have more information.. Jun <var data-var='date'> 3</var>, <var data-var='time'>20:04:56</var> GMT+0 Monitoring - Our team has implemented a fix to resolve the unsafe head stall, and is monitoring the situation. We鈥檒l post an update as soon as the issue is fully resolved.. Jun <var data-var='date'> 3</var>, <var data-var='time'>20:32:21</var> GMT+0 Resolved - Our team has resolved the unsafe head stall, and op-mainnet should now be fully operational for all users. If you continue to experience an issue, please let us know on Discord. Thanks for your patience with us!. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clwo27pdp48610euoupqudge1u</id> <published>2024-05-26T21:36:27.447+00:00</published> <updated>2024-05-26T21:36:27.447+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clwo27pdp48610euoupqudge1u"/> <title>Unsafe head stall on op-mainnet</title> <content type="html"> May <var data-var='date'> 26</var>, <var data-var='time'>21:36:27</var> GMT+0 Investigating - Our team is investigating an unsafe head stall on op-mainnet. At this time, node operators may see their node's unsafe head stall. We apologize for the inconvenience and will share an update once we have more information.. May <var data-var='date'> 26</var>, <var data-var='time'>21:44:15</var> GMT+0 Identified - Our team has identified the cause of the unsafe head stall, and is actively working on a fix. At this time, node operators will continue to experience a stalled unsafe head. We鈥檒l continue to share updates as we have them.. May <var data-var='date'> 26</var>, <var data-var='time'>22:08:59</var> GMT+0 Identified - Our team is continuing to work on a fix for the unsafe head stall. At this time, node operators may see a stalled or sporadically updating unsafe head. The issue is the result of instability in L1 nodes, causing blob data to be periodically unavailable to the sequencer. We'll continue to update you here.. May <var data-var='date'> 26</var>, <var data-var='time'>22:16:11</var> GMT+0 Monitoring - Our team has implemented a fix to resolve the unsafe head stall, and is monitoring the situation. We'll post an update as soon as the issue is fully resolved.. May <var data-var='date'> 26</var>, <var data-var='time'>22:58:33</var> GMT+0 Resolved - Our team has resolved the unsafe head stall, and op-mainnet should now be fully operational for all users. If you continue to experience an issue, please let us know on Discord. Thanks for your patience with us!. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clwj4q8l355706bdoolwroojx7</id> <published>2024-05-22T20:06:00.000+00:00</published> <updated>2024-05-23T07:54:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clwj4q8l355706bdoolwroojx7"/> <title>OP Mainnet Proposer Downtime</title> <content type="html"> May <var data-var='date'> 23</var>, <var data-var='time'>07:54:00</var> GMT+0 Resolved - This incident has been resolved.. May <var data-var='date'> 22</var>, <var data-var='time'>20:06:00</var> GMT+0 Identified - We have experienced some downtime from the proposer on mainnet. The root cause has been identified and a fix has been applied. Withdrawal proving was affected for several hours but is now operational. Withdrawal finalization was not impacted.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clwctlec5297631ban4c6gbodym</id> <published>2024-05-18T08:10:00.000+00:00</published> <updated>2024-05-18T08:10:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clwctlec5297631ban4c6gbodym"/> <title>OP Mainnet degraded performance</title> <content type="html"> May <var data-var='date'> 18</var>, <var data-var='time'>08:10:00</var> GMT+0 Investigating - We became aware of a slowdown in the unsafe head of our sequencer today at 09:10 UTC. This impacted other nodes in the network, presenting as an unsafe head stall for approximately 9 minutes. The performance issue resolved on its own after approximately 20 minutes. We are aware of the root cause and will be issuing further communications in due course. . May <var data-var='date'> 19</var>, <var data-var='time'>13:31:59</var> GMT+0 Investigating - We continue to see intermittent degraded performance on the sequencer's unsafe head.. May <var data-var='date'> 19</var>, <var data-var='time'>14:07:01</var> GMT+0 Monitoring - The unsafe head is currently performing as normal, however we may still see occasional slow unsafe heads as we roll out performance fixes to the network. We will continue to update this issue if extended periods of slow unsafe heads occur. No action is required from users.. May <var data-var='date'> 21</var>, <var data-var='time'>23:44:48</var> GMT+0 Monitoring - We observed another period (approximately 5 minutes) of slow blocks. Block production has resumed and we are continuing to monitor.. Jun <var data-var='date'> 4</var>, <var data-var='time'>17:21:37</var> GMT+0 Resolved - We have resolved the performance issues on OP Mainnet. The performance issues were a result of transactions with a high I/O cost coinciding with op-geth's automated background compaction. We have implemented multiple mitigations to avoid such scenarios happening in the future. We will also be upgrading the underlying hardware OP Mainnet runs on in order to provide additional buffer.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clw6nq2g19443beoepny7408g</id> <published>2024-05-14T17:18:44.789+00:00</published> <updated>2024-05-14T17:18:44.789+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clw6nq2g19443beoepny7408g"/> <title>OP Sepolia Unsafe Head Stall</title> <content type="html"> May <var data-var='date'> 14</var>, <var data-var='time'>17:18:44</var> GMT+0 Investigating - We are currently investigating this incident.. May <var data-var='date'> 14</var>, <var data-var='time'>17:32:16</var> GMT+0 Identified - We have identified the cause of the issue and have applied a fix. . May <var data-var='date'> 14</var>, <var data-var='time'>17:41:12</var> GMT+0 Monitoring - We implemented a fix and are currently monitoring the result.. May <var data-var='date'> 14</var>, <var data-var='time'>17:43:58</var> GMT+0 Resolved - This incident has been resolved.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clw2p190w1414smojaxd5j9tm</id> <published>2024-05-11T22:44:21.854+00:00</published> <updated>2024-05-11T22:44:21.854+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clw2p190w1414smojaxd5j9tm"/> <title>OP Mainnet Unsafe Head Stall</title> <content type="html"> May <var data-var='date'> 11</var>, <var data-var='time'>22:44:21</var> GMT+0 Investigating - We are investigating reports of an unsafe head stall on OP Mainnet.. May <var data-var='date'> 11</var>, <var data-var='time'>22:49:42</var> GMT+0 Investigating - We have identified that an unsafe head stalled occurred, but has since self-resolved. We are investigating the root cause. At this time the network is fully operational.. May <var data-var='date'> 11</var>, <var data-var='time'>23:28:06</var> GMT+0 Resolved - We have identified the root cause of the unsafe head stall, and will prioritize a fix. At this time the network remains fully operational. No action is required from any user.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clvlxiaes179554lmoqiwnl9oda</id> <published>2024-04-30T05:09:28.741+00:00</published> <updated>2024-04-30T05:09:28.741+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clvlxiaes179554lmoqiwnl9oda"/> <title>Unsafe Head Stall on OP Mainnet</title> <content type="html"> Apr <var data-var='date'> 30</var>, <var data-var='time'>05:09:28</var> GMT+0 Investigating - Our team is investigating reports of unsafe head stalls on OP Mainnet. At this time, all users may experience degraded performance syncing nodes or submitting transactions. We apologize for the inconvenience and will share an update once we have more information.. Apr <var data-var='date'> 30</var>, <var data-var='time'>05:25:54</var> GMT+0 Investigating - Our team continues to investigate reports of unsafe head stalls. At this time, users may continue experience degraded performance syncing nodes or submitting transactions.. Apr <var data-var='date'> 30</var>, <var data-var='time'>05:33:12</var> GMT+0 Identified - Our team has identified the cause of the unsafe head stall, and is actively working on a fix. The issue was related to degraded sync performance of an internal beacon node. At this time, some users may still experience degraded performance syncing nodes or submitting transactions. However, we expect the issue to be resolved for the majority of users.. Apr <var data-var='date'> 30</var>, <var data-var='time'>05:34:27</var> GMT+0 Monitoring - Our team has implemented a fix to resolve the unsafe head stall, and is monitoring the situation. We鈥檒l post an update as soon as the issue is fully resolved.. Apr <var data-var='date'> 30</var>, <var data-var='time'>05:47:39</var> GMT+0 Resolved - Our team has resolved the unsafe head stall. The system should now be fully operational for all users. If you continue to experience an issue, please let us know on Discord. Thanks for your patience with us!. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clspqtmwi69806balh0nlfjp7v</id> <published>2024-02-17T23:00:00.000+00:00</published> <updated>2024-02-17T23:00:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clspqtmwi69806balh0nlfjp7v"/> <title>OP Mainnet RPC Instability</title> <content type="html"> Feb <var data-var='date'> 17</var>, <var data-var='time'>23:00:00</var> GMT+0 Resolved - Start time: 4pm Feb 16th PST End time: 10:44pm Feb 16th PST At 4pm Feb 16th PST we started experiencing downgraded RPC calls on our endpoints. This affected a percentage of traffic to [mainnet.optimism.io](http://mainnet.optimism.io). Users were still able to transact as long as they retried their requests. The issue was localized to one third-party upstream RPC provider. The rest of the network was not impacted. Our team identified the cause of the problem at 10pm Feb 16th PST and started a recovery at 10:10pm. RPC calls should now be operating as expected.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/clsdnly2o339959b8n9iwzjqwbt</id> <published>2024-02-15T14:00:00.000+00:00</published> <updated>2024-02-15T14:01:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/clsdnly2o339959b8n9iwzjqwbt"/> <title>OP Mainnet planned pause (withdraws only)</title> <content type="html"> Feb <var data-var='date'> 15</var>, <var data-var='time'>14:01:00</var> GMT+0 Identified - Withdraws now are paused.. Feb <var data-var='date'> 15</var>, <var data-var='time'>15:01:51</var> GMT+0 Completed - Withdraws now are unpaused.. Feb <var data-var='date'> 15</var>, <var data-var='time'>14:00:00</var> GMT+0 Identified - On Thursday, Feb 15th 9:00am ET (6:00am PT), withdraws from OP Mainnet L2 to L1 will be paused as part of a planned maintenance window lasting one hour. During the pause withdraws to L1 will be rejected. The network will be unpaused at 10:00am ET (7:00am PT).. Feb <var data-var='date'> 15</var>, <var data-var='time'>14:00:01</var> GMT+0 Identified - Maintenance is now in progress. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clsmrawc31448hmlj2ja14ui3</id> <published>2024-02-15T05:04:25.367+00:00</published> <updated>2024-02-15T05:26:28.608+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clsmrawc31448hmlj2ja14ui3"/> <title>Unsafe Head Stall on Mainnet</title> <content type="html"> Feb <var data-var='date'> 15</var>, <var data-var='time'>05:26:28</var> GMT+0 Investigating - We are reopening this incident after reports of additional instability.. Feb <var data-var='date'> 15</var>, <var data-var='time'>05:19:36</var> GMT+0 Resolved - Our team has resolved the unsafe head stall. If you continue to experience an issue, please let us know on Discord.. Feb <var data-var='date'> 15</var>, <var data-var='time'>05:04:25</var> GMT+0 Investigating - We are investigating reports of an unsafe head stall on OP Mainnet.. Feb <var data-var='date'> 15</var>, <var data-var='time'>05:10:05</var> GMT+0 Identified - We have identified the cause of the unsafe head stall and have applied a fix. At this time node operators may observe a single-block reorg of the unsafe chain. Chain sync should be back to normal at this time.. Feb <var data-var='date'> 15</var>, <var data-var='time'>05:14:24</var> GMT+0 Monitoring - We have observed both the safe and unsafe parts of the chain advancing. At this time the network is fully operational. We will continue monitoring the situation.. Feb <var data-var='date'> 15</var>, <var data-var='time'>05:52:32</var> GMT+0 Identified - We have identified a potential root cause of the unsafe head stall. At this time the network is functional, however until the fix is fully rolled out the possibility of continued instability remains. We will continue to update this page as the fix rolls out.. Feb <var data-var='date'> 15</var>, <var data-var='time'>06:13:49</var> GMT+0 Identified - We are continuing to roll out a potential fix for the unsafe head stall. At this time no action is required from users or node operators. We will continue to update this page as the fix rolls out.. Feb <var data-var='date'> 15</var>, <var data-var='time'>06:40:46</var> GMT+0 Identified - We are continuing to roll out a potential fix for the unsafe head stall. At this time, the fix has rolled out across our infrastructure and we are waiting for the sequencer to come back online. No action is required from users or node operators. We will continue to update this page.. Feb <var data-var='date'> 15</var>, <var data-var='time'>07:10:48</var> GMT+0 Monitoring - The fix has been fully rolled out, and the network is fully operational. We will continue monitoring the situation in case any additional instability is observed. No action is required from users or node operators.. Feb <var data-var='date'> 15</var>, <var data-var='time'>07:17:53</var> GMT+0 Resolved - Our team has resolved the unsafe head stall. If you're a node operator and your nodes are still stuck, try restarting op-node and op-geth. If you continue to experience an issue, please let us know on Discord. This issue was in no way related to tomorrow's planned pause of OP Mainnet.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/cls3is0dv11488h0ocg3472ghr</id> <published>2024-02-01T17:58:09.895+00:00</published> <updated>2024-02-01T17:58:09.895+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/cls3is0dv11488h0ocg3472ghr"/> <title>OP Goerli Sync Instability</title> <content type="html"> Feb <var data-var='date'> 1</var>, <var data-var='time'>17:58:09</var> GMT+0 Investigating - We are investigating reports of slow or unstable syncing on OP Goerli.. Feb <var data-var='date'> 1</var>, <var data-var='time'>18:00:16</var> GMT+0 Identified - We have identified an issue with an upstream node provider causing sync instability on OP Goerli. We are rolling out a fix. At this time, node operators may continue to experience slow or unstable sync until the fix is fully deployed.. Feb <var data-var='date'> 1</var>, <var data-var='time'>18:11:40</var> GMT+0 Monitoring - The fix has been rolled out, and nodes should be able to sync normally.. Feb <var data-var='date'> 1</var>, <var data-var='time'>18:45:34</var> GMT+0 Resolved - This incident has been resolved.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/clrp5jq3t12156b7mz0sy417ki</id> <published>2024-01-23T17:00:00.000+00:00</published> <updated>2024-01-23T17:00:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/clrp5jq3t12156b7mz0sy417ki"/> <title>OP Sepolia Planned Pause</title> <content type="html"> Jan <var data-var='date'> 23</var>, <var data-var='time'>17:00:00</var> GMT+0 Identified - We will be conducting a test of our forthcoming pausability features on the Sepolia network on noon EST on Tuesday, January 23rd, lasting for approximately 1 hour. At this time the following methods on our Bridge contracts will revert if called: - OptimismPortal.proveWithdrawalTransaction() - OptimismPortal.finalizeWithdrawalTransaction() - L1CrossDomainMessenger.relayMessage() - StandardBridge.finalizeBridgeERC20() - StandardBridge.finalizeBridgeETH() - L1ERC721Bridge.finalizeBridgeERC721() This is part of ongoing efforts to improve the security of our system and our ability to respond to an incident. Thank you.. Jan <var data-var='date'> 23</var>, <var data-var='time'>17:00:01</var> GMT+0 Identified - Maintenance is now in progress. Jan <var data-var='date'> 23</var>, <var data-var='time'>18:00:00</var> GMT+0 Completed - Maintenance has completed successfully. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clr9i8lyf1591411hfoc7j8xra6e</id> <published>2024-01-11T17:49:59.453+00:00</published> <updated>2024-01-11T17:49:59.453+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clr9i8lyf1591411hfoc7j8xra6e"/> <title>Degraded Performance on Public Endpoint</title> <content type="html"> Jan <var data-var='date'> 11</var>, <var data-var='time'>17:49:59</var> GMT+0 Investigating - We are investigating reports of degraded performance on the public endpoint. At this time some users may experience errors querying the chain or submitting new transactions through the public endpoint. To mitigate the issue, we will be switch upstream infrastructure providers. This process may take a few minutes to complete.. Jan <var data-var='date'> 11</var>, <var data-var='time'>17:53:11</var> GMT+0 Monitoring - We have transitioned our infrastructure to use a new upstream provider in order to mitigate the degraded performance on the public endpoint. The rollout may take a few minutes to fully take effect. At this time, users should no longer see degraded performance.. Jan <var data-var='date'> 11</var>, <var data-var='time'>18:12:00</var> GMT+0 Resolved - This incident has been resolved.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/clqb9s6bf5635bfmyqkrq5qq4</id> <published>2023-12-20T20:30:00.000+00:00</published> <updated>2023-12-20T20:30:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/clqb9s6bf5635bfmyqkrq5qq4"/> <title>OP Goerli planned pause</title> <content type="html"> Dec <var data-var='date'> 20</var>, <var data-var='time'>20:30:00</var> GMT+0 Identified - On Wednesday, Dec 20th 12:30pm PST, OP Goerli will be paused as part of a planned maintenance window lasting approximately one hour. During the pause, the L1 state will be frozen point-in-time and transactions will be rejected, until the unpause is issued. OP Mainnet and OP Sepolia won't be affected.. Dec <var data-var='date'> 20</var>, <var data-var='time'>20:30:01</var> GMT+0 Identified - Maintenance is now in progress. Dec <var data-var='date'> 20</var>, <var data-var='time'>20:30:01</var> GMT+0 Identified - Pause transaction: https://goerli.etherscan.io/tx/0xbbda99c8af39e983468876286cc4565d1dc86f59470173fe281d3d65abc7e460. Dec <var data-var='date'> 20</var>, <var data-var='time'>20:38:49</var> GMT+0 Identified - OP Goerli network paused successfully.. Dec <var data-var='date'> 20</var>, <var data-var='time'>20:41:50</var> GMT+0 Identified - OP Goerli network unpaused. Transaction hash: https://goerli.etherscan.io/tx/0x64cb6431423c4b08cedc3f06b3737c57de723e221c68423fc72b8326c0d9156b. Dec <var data-var='date'> 20</var>, <var data-var='time'>20:42:03</var> GMT+0 Completed - Maintenance has completed successfully.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clq9xgv3x47809b4n15cxk59wt</id> <published>2023-12-17T19:25:00.000+00:00</published> <updated>2023-12-17T22:08:35.266+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clq9xgv3x47809b4n15cxk59wt"/> <title>Goerli Safe Head Stall (Inscriptions Flood)</title> <content type="html"> Dec <var data-var='date'> 17</var>, <var data-var='time'>22:08:35</var> GMT+0 Monitoring - Our team has implemented a fix to resolve the Goerli Safe Head Stall, and is monitoring the situation. The safe head has caught up for now and should remain stable for now. All services should be restored. We鈥檒l post an update as soon as the issue is fully resolved.. Dec <var data-var='date'> 17</var>, <var data-var='time'>22:48:40</var> GMT+0 Resolved - Our team has resolved the Goerli Safe Head stall, and the safe head should now be progressing as usual for all users. If you continue to experience an issue, please let us know on Discord. Thanks for your patience with us!. Dec <var data-var='date'> 17</var>, <var data-var='time'>19:25:00</var> GMT+0 Identified - Our team has identified the cause of the safe head halt on Goerli. It is caused by the creation of GORS Inscriptions on Goerli, see https://dune.com/goerlis/goerlis for their progress. This results in very high basefees of 2k - 6k GWei. At the current rate, we expect the creation of GORS to be finished in about 3h. At this time, applications using the safe head will continue to experience a head halt until the fees cool down. In the meantime, the team is evaluating the fee caps on our end. We鈥檒l continue to share updates as we have them.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/cloekc6k81429124jdobvch8s3lf</id> <published>2023-10-31T16:48:29.227+00:00</published> <updated>2023-10-31T16:48:29.227+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/cloekc6k81429124jdobvch8s3lf"/> <title>Goerli Cluster Maintenance</title> <content type="html"> Oct <var data-var='date'> 31</var>, <var data-var='time'>16:48:29</var> GMT+0 Monitoring - The Goerli sequencer is currently undergoing required cluster maintenance. We expect a brief disruption in node sync and transaction sequencing while nodes restart.. Oct <var data-var='date'> 31</var>, <var data-var='time'>17:02:25</var> GMT+0 Investigating - We are investigating reports of slow block sync.. Oct <var data-var='date'> 31</var>, <var data-var='time'>17:13:07</var> GMT+0 Monitoring - We have applied a fix for the slow block sync. At this time, nodes should be syncing as normal. We will continue monitoring the network.. Oct <var data-var='date'> 31</var>, <var data-var='time'>17:51:56</var> GMT+0 Resolved - This incident has been resolved. Node sync is fully back to normal.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Incident/clnswfyiu4007b5n7g177oi1j</id> <published>2023-10-16T12:22:00.000+00:00</published> <updated>2023-10-16T12:22:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/incident/clnswfyiu4007b5n7g177oi1j"/> <title>OP Goerli Head Halt</title> <content type="html"> Oct <var data-var='date'> 16</var>, <var data-var='time'>12:22:00</var> GMT+0 Investigating - Our team is investigating a chain halt of OP Goerli. At this time, normal users as well as node operators may experience a complete chain halt for the safe head at 16015344, and unsafe head at 16015406. We apologize for the inconvenience and will share an update once we have more information.. Oct <var data-var='date'> 16</var>, <var data-var='time'>13:38:19</var> GMT+0 Identified - Our team has identified the cause of the OP Goerli Head Halt, and is actively working on a fix. The issue is the result of an internal problem with our sequencer L1 connection. At this time, all users will continue to experience a Goerli chain halt until we have restarted the relevant services with a fixed configuration. We鈥檒l continue to share updates as we have them.. Oct <var data-var='date'> 16</var>, <var data-var='time'>14:39:12</var> GMT+0 Monitoring - Our team has implemented a fix to resolve the OP Goerli chain halt, and is monitoring the situation. We鈥檒l post an update as soon as the issue is fully resolved.. Oct <var data-var='date'> 16</var>, <var data-var='time'>14:58:25</var> GMT+0 Resolved - Our team has resolved the OP Goerli head halt, and the chain should now be fully operational for all users. If you continue to experience an issue, please let us know on Discord. Thanks for your patience with us!. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/cllpai2nz1666bfn2dz4pvu92</id> <published>2023-08-28T17:00:00.000+00:00</published> <updated>2023-08-28T17:00:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/cllpai2nz1666bfn2dz4pvu92"/> <title>OP Mainnet Sequencer Update Enabling ZDD</title> <content type="html"> Aug <var data-var='date'> 28</var>, <var data-var='time'>17:00:00</var> GMT+0 Identified - On Monday, August 28th at 17:00 UTC, we are upgrading the OP Mainnet sequencer deployment configuration to enable future zero downtime deployments. As part of this planned maintenance, users can expect up to five minutes of downtime on OP Mainnet. We鈥檒l update this status once the maintenance window is completed and OP Mainnet is fully operational on https://status.optimism.io/ . Aug <var data-var='date'> 28</var>, <var data-var='time'>17:00:01</var> GMT+0 Identified - Maintenance is now in progress. Aug <var data-var='date'> 28</var>, <var data-var='time'>17:10:28</var> GMT+0 Completed - Maintenance has completed successfully.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/cljxih3rh70676xtojq58epp7h</id> <published>2023-07-12T20:00:00.000+00:00</published> <updated>2023-07-12T20:00:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/cljxih3rh70676xtojq58epp7h"/> <title>OP Mainnet Sequencer Update</title> <content type="html"> Jul <var data-var='date'> 12</var>, <var data-var='time'>20:00:00</var> GMT+0 Identified - On Wednesday, July 12, 2023 at 20:00 UTC, we are upgrading the version of op-geth on the OP Mainnet sequencer to reduce the average transaction inclusion latency from 2-4 seconds to 0-2 seconds. As part of this planned maintenance, users can expect up to five minutes of downtime on the OP Mainnet Sequencer. We鈥檒l update this status once the maintenance window is completed and the OP Mainnet Sequencer is fully operational. . Jul <var data-var='date'> 12</var>, <var data-var='time'>20:02:40</var> GMT+0 Identified - The sequencer is temporarily down for scheduled maintenance. We are upgrading the version of op-geth on the OP Mainnet sequencer to reduce the average transaction inclusion latency from 2-4 seconds to 0-2 seconds. Users can expect up to five minutes of downtime on the OP Mainnet Sequencer. We鈥檒l update this status once the maintenance window is completed and the OP Mainnet Sequencer is fully operational.. Jul <var data-var='date'> 12</var>, <var data-var='time'>20:09:44</var> GMT+0 Identified - Sequencer downtime is taking longer than the expected time. Please standby for updates. The sequencer is temporarily down for scheduled maintenance. We are upgrading the version of op-geth on the OP Mainnet sequencer to reduce the average transaction inclusion latency from 2-4 seconds to 0-2 seconds. We鈥檒l update this status once the maintenance window is completed and the OP Mainnet Sequencer is fully operational.. Jul <var data-var='date'> 12</var>, <var data-var='time'>20:12:36</var> GMT+0 Completed - OP Mainnet Sequencer maintenance has completed safely!. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/clje4vjfj992121h4obz8j0th3g</id> <published>2023-06-27T10:30:00.000+00:00</published> <updated>2023-06-27T10:45:01.548+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/clje4vjfj992121h4obz8j0th3g"/> <title>Goerli Sequencer Update</title> <content type="html"> Jun <var data-var='date'> 27</var>, <var data-var='time'>10:45:01</var> GMT+0 Identified - Update is now in progress.. Jun <var data-var='date'> 27</var>, <var data-var='time'>10:30:00</var> GMT+0 Identified - We are going to update the Goerli sequencer. A few minutes of sequencer downtime can be expected.. Jun <var data-var='date'> 27</var>, <var data-var='time'>10:53:14</var> GMT+0 Completed - Update has completed successfully.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/clit9r2e4175354b2okmdg7zl58</id> <published>2023-06-12T21:00:00.000+00:00</published> <updated>2023-06-12T21:00:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/clit9r2e4175354b2okmdg7zl58"/> <title>mainnet.optimism.io - public endpoint maintenance</title> <content type="html"> Jun <var data-var='date'> 12</var>, <var data-var='time'>21:00:00</var> GMT+0 Identified - We are planning for a scheduled maintenance during that time. No downtime is expected but please be aware just in case.. Jun <var data-var='date'> 12</var>, <var data-var='time'>21:19:13</var> GMT+0 Completed - Maintenance has completed successfully.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/clieqyc0x13645trowwikfepm3</id> <published>2023-06-06T16:00:00.000+00:00</published> <updated>2023-06-06T16:00:32.157+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/clieqyc0x13645trowwikfepm3"/> <title>OP Mainnet Bedrock Upgrade</title> <content type="html"> Jun <var data-var='date'> 6</var>, <var data-var='time'>16:00:32</var> GMT+0 Identified - The migration has started. Legacy network deposits and withdrawals have been paused. Transaction acceptance on the legacy sequencer has been halted.. Jun <var data-var='date'> 6</var>, <var data-var='time'>16:00:00</var> GMT+0 Identified - The OP Mainnet Bedrock Upgrade is expected to run for 2-4 hours. Find all of the details here: https://optimism.io/bedrock-upgrade Watch for updates on this status page for: * Images for node operators * Datadirs for both full node and archival node operators * Notifications on when deposits, withdrawals, and the sequencer are back live.. Jun <var data-var='date'> 6</var>, <var data-var='time'>16:36:54</var> GMT+0 Identified - We are now starting to execute the L2 portion of the migration. This is the longest step in the migration process, and could take up to 1.5 hours. During this phase of the migration, ETH balances and withdrawals will be migrated. Successful completion of this stage will conclude the L2 portion of the migration, and we will perform all related checks before moving on to subsequent phases.. Jun <var data-var='date'> 6</var>, <var data-var='time'>17:44:27</var> GMT+0 Identified - Node Operators: Docker images are now available in our community hub docs. `op-node` version: https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.1.0 (Docker Images are in the release notes) `op-geth` version: https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101105.2 (Docker Images are in the release notes) Please await the upload of the Migrated Datadir before you can fully spin up your OP Mainnet Bedrock nodes.. Jun <var data-var='date'> 6</var>, <var data-var='time'>18:20:01</var> GMT+0 Identified - The migrated (Bedrock) datadir required to spin up `op-geth` has been successfully hosted and is now ready for distribution. Full Node Operators are now fully unblocked to spin up. Archival Node Operators will need to wait for the archival datadir, which may take an additional 5-10 hours. The datadir can be downloaded from the link found in the OP Mainnet docs: https://community.optimism.io/docs/useful-tools/networks/#links. Jun <var data-var='date'> 6</var>, <var data-var='time'>18:26:31</var> GMT+0 Identified - L1 smart contract upgrades have been successfully implemented. The portal has been unpaused, and deposits/withdrawals have been re-enabled.. Jun <var data-var='date'> 6</var>, <var data-var='time'>18:50:28</var> GMT+0 Identified - The Bedrock sequencer has started up. Images, and data directories for node operators can be found [here](https://community.optimism.io/docs/useful-tools/networks/#links). Key external OP Mainnet infrastructure is starting to come back online. View the [OP Mainnet Infra Tracker](https://oplabs.notion.site/External-OP-Mainnet-Bedrock-Upgrade-Infra-Status-Tracker-07d7c9c0916243b8b743b74af77d37f9?pvs=4) to follow along. . Jun <var data-var='date'> 6</var>, <var data-var='time'>19:10:01</var> GMT+0 Identified - For node operators: We have received reports that the [full node Bedrock datadir](https://community.optimism.io/docs/useful-tools/networks/#parameters-for-node-operators) is taking a long time to download. Since it is available on GCS, you can use parallel downloader tools like `aria2` to make it faster. This method has seen download speeds in excess of 100MB/s. Some recommendations: - Run the download on a high-network box in the cloud. - Use aria2 or the gcloud storage cp command to download the file in parallel. . Jun <var data-var='date'> 6</var>, <var data-var='time'>19:38:02</var> GMT+0 Identified - For Archival node operators: While we recommend using the `legacy-geth` archival datadir we upload [once it's ready](https://community.optimism.io/docs/useful-tools/networks/#links), given the size of the archival data disk and the time it'll take for it to become available (up to 24 hours), we recommend preserving your legacy archival nodes and routing archival traffic to them if possible. To check if your legacy archival node is able to serve traffic, please do the following: Verify that the head block number is `105235062` Verify that the head block hash is `0x21a168dfa5e727926063a28ba16fd5ee84c814e847c81a699c7a0ea551e4ca50` If both of these criteria are true, then your legacy archival node is on the same block as the archival datadir and can be used to serve user traffic. You can set `--rollup.historicalrpc <l2geth-rpc>` on `op-geth` and it will forward requests for historical data it can't handle to `l2geth`.. Jun <var data-var='date'> 6</var>, <var data-var='time'>21:52:17</var> GMT+0 Identified - The public endpoint is back live: https://mainnet.optimism.io/ This should unblock most wallets to begin working again.. Jun <var data-var='date'> 6</var>, <var data-var='time'>22:48:17</var> GMT+0 Completed - Much of our our core OP Mainnet infra is back online! Continue to track https://oplabs.notion.site/External-OP-Mainnet-Bedrock-Upgrade-Infra-Status-Tracker-07d7c9c0916243b8b743b74af77d37f9?pvs=4 for updates on other key infrastructure in the OP Mainnet ecosystem. The Bridge UI has been unpaused. Deposits and Withdrawals can now be executed on OP Mainnet from: https://app.optimism.io/bridge/. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/clfso10pe19882boj2685b813</id> <published>2023-03-28T19:40:00.000+00:00</published> <updated>2023-03-28T19:40:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/clfso10pe19882boj2685b813"/> <title>public endpoint maintenance (mainnet.optimism.io)</title> <content type="html"> Mar <var data-var='date'> 28</var>, <var data-var='time'>19:40:00</var> GMT+0 Identified - [Planned] migrating public endpoint backend to new infrastructure. there may be some temporary hiccups. Mar <var data-var='date'> 28</var>, <var data-var='time'>20:10:15</var> GMT+0 Completed - Maintenance completed.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/clesphj7d24075h8nbrctt0otc</id> <published>2023-03-03T15:43:43.769+00:00</published> <updated>2023-03-03T16:01:48.402+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/clesphj7d24075h8nbrctt0otc"/> <title>Goerli Regolith Fork Maintenance</title> <content type="html"> Mar <var data-var='date'> 3</var>, <var data-var='time'>16:01:48</var> GMT+0 Completed - Maintenance has completed successfully. We will monitor the network for any issues.. Mar <var data-var='date'> 3</var>, <var data-var='time'>15:43:43</var> GMT+0 Identified - We are upgrading our infrastructure on Goerli to support the Regolith hardfork. We expect approximately 15 minutes of downtime.. Mar <var data-var='date'> 3</var>, <var data-var='time'>15:44:30</var> GMT+0 Identified - Maintenance is now in progress.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/cldak4nxe36098ayna7dizmngt</id> <published>2023-01-26T22:00:00.000+00:00</published> <updated>2023-01-26T22:00:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/cldak4nxe36098ayna7dizmngt"/> <title>Mainnet Cluster Maintenance</title> <content type="html"> Jan <var data-var='date'> 26</var>, <var data-var='time'>22:00:00</var> GMT+0 Identified - We will be performing some necessary upgrades to our mainnet Kubernetes infrastructure. We expect no more than 15 minutes of downtime as we perform these upgrades.. Jan <var data-var='date'> 26</var>, <var data-var='time'>22:00:01</var> GMT+0 Identified - Maintenance is now in progress. Jan <var data-var='date'> 26</var>, <var data-var='time'>22:54:31</var> GMT+0 Completed - Maintenance has completed successfully, sequencer is back online.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/clcmss04q1151i0onixgfcw70</id> <published>2023-01-12T18:00:00.000+00:00</published> <updated>2023-01-12T18:00:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/clcmss04q1151i0onixgfcw70"/> <title>Goerli Bedrock Upgrade</title> <content type="html"> Jan <var data-var='date'> 12</var>, <var data-var='time'>18:00:00</var> GMT+0 Identified - On January 12 at 1800 UTC, the OP Labs engineering team will begin the work to migrate Optimism鈥檚 Goerli Testnet to Bedrock. We expect the migration to take between thirty minutes and 2 hours, during which the Goerli network will be unavailable until the upgrade is complete. For more information about what to expect on upgrade day, please see the [Upgrade Guide](https://community.optimism.io/docs/developers/bedrock/upgrade-guide/).. Jan <var data-var='date'> 12</var>, <var data-var='time'>19:51:27</var> GMT+0 Identified - The Optimism Goerli Bedrock upgrade is almost complete. We are working on spinning the Sequencer back online. Expect final `op-node` and `op-geth` images shortly.. Jan <var data-var='date'> 12</var>, <var data-var='time'>18:00:01</var> GMT+0 Identified - Maintenance is now in progress. Jan <var data-var='date'> 12</var>, <var data-var='time'>18:07:31</var> GMT+0 Identified - Update: We're wrapping up the last bit of prep work before halting the Optimism Goerli network and beginning the upgrade. Please standby, the migration will begin shortly.. Jan <var data-var='date'> 12</var>, <var data-var='time'>18:20:58</var> GMT+0 Identified - The upgrade to the Bedrock Release of the Optimism Goerli Network has begun! Transactions to the Sequencer are halted (`eth_sendRawTransaction` RPC calls will be rejected by the Sequencer). Deposits and Withdrawals are paused. The Public RPC Endpoint (https://goerli.optimism.io/) will stay up with only read access.. Jan <var data-var='date'> 12</var>, <var data-var='time'>19:14:09</var> GMT+0 Identified - The final blocks on the legacy Optimism Goerli sequencer have been mined and batch submitted to L1. The last block mined was block number 4061223, and the first block of the Bedrock release will be block number 4061224.. Jan <var data-var='date'> 12</var>, <var data-var='time'>21:04:15</var> GMT+0 Identified - The Optimism Goerli migration to the Bedrock release is in its final stages! There were some unexpected delays that we will be addressing to ensure the Optimism Mainnet upgrade takes less time. The Optimism Goerli Sequencer has been upgraded to the Bedrock release and is back online at https://goerli-sequencer.optimism.io ! Transactions are now being accepted, and we are testing to see that Deposits and Withdrawals are functional. op-node image is live at: [us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v0.10.9](url) . Jan <var data-var='date'> 12</var>, <var data-var='time'>21:51:50</var> GMT+0 Completed - The Optimism Goerli network upgrade to the Bedrock release is complete! Deposits, Withdrawals, and transactions to the Sequencer are now back live. The public `https://goerli.optimism.io` endpoint is back up and will resume accepting transactions shortly. The Optimism Bridge Frontend is still being updated. Follow along as third party infrastructure projects spin back online here: https://oplabs.notion.site/External-Optimism-Goerli-Bedrock-Upgrade-Infra-Status-Tracker-86e67c08c09a4a85ae7987fca6fb1ddb. Jan <var data-var='date'> 13</var>, <var data-var='time'>17:57:40</var> GMT+0 Completed - The Optimism Bridge is back online - deposits and withdrawals are now functional: https://app.optimism.io/bridge. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/cl963iya468709a5odhayl3ipw</id> <published>2022-10-12T20:39:06.219+00:00</published> <updated>2022-10-12T20:39:06.219+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/cl963iya468709a5odhayl3ipw"/> <title>Public endpoint maintenance</title> <content type="html"> Oct <var data-var='date'> 12</var>, <var data-var='time'>20:39:06</var> GMT+0 Completed - Maintenance complete.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/cl7rm7zs859322h8ok4bspwr12</id> <published>2022-09-08T18:00:00.000+00:00</published> <updated>2022-09-08T18:00:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/cl7rm7zs859322h8ok4bspwr12"/> <title>Public mainnet endpoint maintenance</title> <content type="html"> Sep <var data-var='date'> 8</var>, <var data-var='time'>18:00:00</var> GMT+0 Identified - From September 8th 2PM EDT - 2:30PM EDT we will be undergoing planned maintenance to upgrade the public API endpoint for mainnet. There may be minimal downtime for users of the public endpoint during this window.. Sep <var data-var='date'> 8</var>, <var data-var='time'>18:00:01</var> GMT+0 Identified - Maintenance is now in progress. Sep <var data-var='date'> 8</var>, <var data-var='time'>18:30:00</var> GMT+0 Completed - Maintenance has completed successfully. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/cl77pmlz088465imossp5m5k24</id> <published>2022-08-25T18:00:00.000+00:00</published> <updated>2022-08-25T18:00:00.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/cl77pmlz088465imossp5m5k24"/> <title>Public goerli-devnet endpoint maintenance </title> <content type="html"> Aug <var data-var='date'> 25</var>, <var data-var='time'>18:00:00</var> GMT+0 Identified - From August 25th 2PM EDT - 3PM EDT we will be undergoing planned maintenance to upgrade the public API endpoint for the goerli-devnet from our self-hosted nodes to infrastructure provided by Alchemy. There may be minimal downtime for users of the public endpoint during this window.. Aug <var data-var='date'> 25</var>, <var data-var='time'>18:00:01</var> GMT+0 Identified - Maintenance is now in progress. Aug <var data-var='date'> 25</var>, <var data-var='time'>19:00:00</var> GMT+0 Completed - Maintenance has completed successfully. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/cl4hd6fqx0201uxn5abbu24oj</id> <published>2022-06-23T18:00:00.000+00:00</published> <updated>2022-06-23T18:00:01.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/cl4hd6fqx0201uxn5abbu24oj"/> <title>Public Endpoint Infrastructure Upgrade</title> <content type="html"> Jun <var data-var='date'> 23</var>, <var data-var='time'>18:00:01</var> GMT+0 Identified - Maintenance is now in progress. Jun <var data-var='date'> 23</var>, <var data-var='time'>18:38:43</var> GMT+0 Identified - We have completed the update, and are monitoring for issues.. Jun <var data-var='date'> 23</var>, <var data-var='time'>19:00:00</var> GMT+0 Completed - Maintenance has completed successfully. Jun <var data-var='date'> 23</var>, <var data-var='time'>18:00:00</var> GMT+0 Identified - We are upgrading our public endpoint infrastructure to add support for splitting traffic between multiple providers, an action we committed to as part of our token launch retrospective. During this upgrade, there may be up to 30 minutes of downtime as we provision new load balancers. To avoid downtime, please switch to a third-party provider or run your own node before then.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/cl44hfviw1229ldn6m80goepp</id> <published>2022-06-09T18:00:00.000+00:00</published> <updated>2022-06-09T18:00:01.000+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/cl44hfviw1229ldn6m80goepp"/> <title>Scheduled Infrastructure Upgrade</title> <content type="html"> Jun <var data-var='date'> 9</var>, <var data-var='time'>18:00:01</var> GMT+0 Identified - Maintenance is now in progress. Jun <var data-var='date'> 9</var>, <var data-var='time'>19:00:00</var> GMT+0 Completed - Maintenance has completed successfully. Jun <var data-var='date'> 9</var>, <var data-var='time'>18:00:00</var> GMT+0 Identified - We are upgrading our infrastructure on mainnet. We expect less than 5 minutes of downtime as services restart.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/cl44hbb7v1426l6n6otqzc6wl</id> <published>2022-06-07T18:11:15.412+00:00</published> <updated>2022-06-07T18:11:15.412+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/cl44hbb7v1426l6n6otqzc6wl"/> <title>Scheduled Infrastructure Upgrade</title> <content type="html"> Jun <var data-var='date'> 7</var>, <var data-var='time'>18:11:15</var> GMT+0 Identified - We are upgrading our infrastructure on Kovan. There should be less than 5 minutes of downtime as services restart.. Jun <var data-var='date'> 7</var>, <var data-var='time'>18:55:28</var> GMT+0 Completed - Maintenance has completed successfully.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/cl3untto11432m8n4852p8gbt</id> <published>2022-05-31T21:15:59.977+00:00</published> <updated>2022-05-31T21:15:59.977+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/cl3untto11432m8n4852p8gbt"/> <title>Limited Archive Functionality</title> <content type="html"> May <var data-var='date'> 31</var>, <var data-var='time'>21:15:59</var> GMT+0 Identified - We have temporarily limited archive node functionality until load subsides.. Jun <var data-var='date'> 2</var>, <var data-var='time'>21:10:54</var> GMT+0 Completed - Archive limitations have been removed.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/cl1ceonuz594477e3om059l21nv</id> <published>2022-03-29T18:00:00.000+00:00</published> <updated>2022-03-29T20:20:57.278+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/cl1ceonuz594477e3om059l21nv"/> <title>Scheduled Kovan/Mainnet Maintenance</title> <content type="html"> Mar <var data-var='date'> 29</var>, <var data-var='time'>20:20:57</var> GMT+0 Completed - Maintenance has completed successfully.. Mar <var data-var='date'> 29</var>, <var data-var='time'>18:00:00</var> GMT+0 Identified - We are planning for a scheduled maintenance during this time. No more than 5 minutes of downtime is expected.. Mar <var data-var='date'> 29</var>, <var data-var='time'>18:05:18</var> GMT+0 Identified - Maintenance is now in progress.. </content> </entry> <entry> <id>tag:status.optimism.io,2005:Maintenance/cl15bbg65195505swn4oi99qnc8</id> <published>2022-03-24T18:00:00.000+00:00</published> <updated>2022-03-24T18:12:56.193+00:00</updated> <link rel="alternate" type="text/html" href="https://status.optimism.io/maintenance/cl15bbg65195505swn4oi99qnc8"/> <title>Batch Compression Upgrade</title> <content type="html"> Mar <var data-var='date'> 24</var>, <var data-var='time'>18:12:56</var> GMT+0 Identified - Maintenance is now in progress.. Mar <var data-var='date'> 24</var>, <var data-var='time'>18:00:00</var> GMT+0 Identified - We will be enabling batch compression on our mainnet network today. We do not expect any downtime during this process, however withdrawals may by slightly delayed while we restart our batch submitter.. Mar <var data-var='date'> 24</var>, <var data-var='time'>18:46:15</var> GMT+0 Completed - Maintenance has completed successfully.. </content> </entry> </feed>