Unichain Status - Incident history https://status.unichain.org Unichain Tue, 24 Mar 2026 02:07:26 +0000 Unichain Sepolia Consensus Layer Peering Issues Type: Incident Duration: 45 minutes Affected Components: Node Syncing Mar 24, 02:07:26 GMT+0 - Identified - We are continuing to work on a fix for this incident. Mar 24, 02:34:22 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 24, 02:52:10 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 45 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>02:07:26</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>02:34:22</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>02:52:10</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 24 Mar 2026 02:07:26 +0000 https://status.unichain.org/incident/cmn3z5ioa020flimgty767s80 https://status.unichain.org/incident/cmn3z5ioa020flimgty767s80 Unichain Sepolia Unsafe Head Stall Type: Incident Duration: 18 hours and 48 minutes Affected Components: L2 Block Production, Flashblocks Websocket Stream, Public RPC, L1 Batch Posting, , Node Syncing, Unichain Sepolia → Mar 5, 23:00:06 GMT+0 - Investigating - We are currently investigating this incident. Mar 5, 23:50:33 GMT+0 - Identified - Fix implemented, recovery in progress. Mar 5, 23:53:52 GMT+0 - Monitoring - Block production has resumed without flashblocks. We are working on recovering flashblocks. Mar 6, 17:48:27 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 18 hours and 48 minutes

Affected Components: , , , , ,

<p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>23:00:06</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>23:50:33</var> GMT+0</small><br><strong>Identified</strong> - Fix implemented, recovery in progress..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>23:53:52</var> GMT+0</small><br><strong>Monitoring</strong> - Block production has resumed without flashblocks. We are working on recovering flashblocks..</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>17:48:27</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 5 Mar 2026 23:00:06 +0000 https://status.unichain.org/incident/cmme2j9vf000l11emh0k10rlf https://status.unichain.org/incident/cmme2j9vf000l11emh0k10rlf Unichain Mainnet: Post-Fusaka Safe Head Stall Type: Incident Duration: 3 hours and 33 minutes Affected Components: Flashblocks Websocket Stream, L2 Block Production, Public RPC, L2 Block Production, Flashblocks Websocket Stream, Node Syncing, L1 Batch Posting, Public RPC, L1 Batch Posting, , , Node Syncing, Unichain Sepolia → Unichain Mainnet → Dec 4, 01:48:56 GMT+0 - Identified - After working with OP Labs, we have identified both an issue in our batch submission and in the consensus client handling of such a case. We are trying to roll out a new version of the consensus client that fixes this issue. Dec 4, 02:32:32 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 4, 02:32:46 GMT+0 - Resolved - We have identified that the root cause of the safe head stall on Unichain Mainnet is due to a bug in how op-node handles fetching blobs. All nodes operators will need to update their op-node to`us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:e1db990da90a845e1943b1dc20f59e18099db538` Dec 4, 02:40:49 GMT+0 - Postmortem - Unichain Mainnet erroneously posted the same batch transaction at two different nonces. This triggered a corner case in the consensus layer client that made it impossible for the L2 Safe Head to progress. OP Labs has a fix available: [us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.16.3](http://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:e1db990da90a845e1943b1dc20f59e18099db538). Please upgrade your consensus layer clients on Unichain to use this image until OP Labs provides a newer release. Dec 3, 23:00:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 3 hours and 33 minutes

Affected Components: , , , , , , , , , , ,

<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>01:48:56</var> GMT+0</small><br><strong>Identified</strong> - After working with OP Labs, we have identified both an issue in our batch submission and in the consensus client handling of such a case. We are trying to roll out a new version of the consensus client that fixes this issue..</p> <p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>02:32:32</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>02:32:46</var> GMT+0</small><br><strong>Resolved</strong> - We have identified that the root cause of the safe head stall on Unichain Mainnet is due to a bug in how op-node handles fetching blobs. All nodes operators will need to update their op-node to`us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:e1db990da90a845e1943b1dc20f59e18099db538`.</p> <p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>02:40:49</var> GMT+0</small><br><strong>Postmortem</strong> - Unichain Mainnet erroneously posted the same batch transaction at two different nonces. This triggered a corner case in the consensus layer client that made it impossible for the L2 Safe Head to progress. OP Labs has a fix available: [us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.16.3](http://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:e1db990da90a845e1943b1dc20f59e18099db538). Please upgrade your consensus layer clients on Unichain to use this image until OP Labs provides a newer release..</p> <p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Wed, 3 Dec 2025 23:00:00 +0000 https://status.unichain.org/incident/cmiqogerv02pkfqco435uzb9e https://status.unichain.org/incident/cmiqogerv02pkfqco435uzb9e Unichain - L2 Batches are not being submitted to L1 Type: Incident Duration: 35 minutes Affected Components: L1 Batch Posting, L1 Batch Posting Nov 16, 15:31:43 GMT+0 - Investigating - We are currently investigating this incident. Nov 16, 15:47:49 GMT+0 - Identified - We have identified an upstream issue with our TEE signers that has made batch posting functionality flaky. Nov 16, 16:06:13 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 35 minutes

Affected Components: ,

<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>15:31:43</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>15:47:49</var> GMT+0</small><br><strong>Identified</strong> - We have identified an upstream issue with our TEE signers that has made batch posting functionality flaky..</p> <p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>16:06:13</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 16 Nov 2025 15:31:43 +0000 https://status.unichain.org/incident/cmi1vita8005dfg4en1srqgm9 https://status.unichain.org/incident/cmi1vita8005dfg4en1srqgm9 Unichain Mainnet: Transactions are not being included in new blocks Type: Incident Duration: 4 hours Affected Components: Public RPC, L2 Block Production, Node Syncing, L1 Batch Posting, L1 Batch Posting, L2 Block Production, Public RPC, , , Node Syncing, Unichain Sepolia → Unichain Mainnet → Nov 14, 14:30:00 GMT+0 - Investigating - We have noticed that many transactions are getting stuck within Unichain Mainnet's mempool and are subsequently not being added to newly produced blocks. This means user swaps and regular transactions are not being submitted to the chain. Nov 14, 17:00:00 GMT+0 - Identified - Many users are reporting that their swaps and transactions are stuck. We have identified an issue with Unichain's proxy where it is not forwarding transactions to our TEE builder. Nov 14, 18:30:00 GMT+0 - Resolved - This incident has been resolved. An upgrade to the TEE builder had a poor interaction with our proxy, leading to transactions not being submitted properly. Type: Incident

Duration: 4 hours

Affected Components: , , , , , , , , ,

<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We have noticed that many transactions are getting stuck within Unichain Mainnet's mempool and are subsequently not being added to newly produced blocks. This means user swaps and regular transactions are not being submitted to the chain..</p> <p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Identified</strong> - Many users are reporting that their swaps and transactions are stuck. We have identified an issue with Unichain's proxy where it is not forwarding transactions to our TEE builder..</p> <p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>18:30:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. An upgrade to the TEE builder had a poor interaction with our proxy, leading to transactions not being submitted properly..</p> ]]> Fri, 14 Nov 2025 14:30:00 +0000 https://status.unichain.org/incident/cmhz96d4500nkrz0fk81sivx8 https://status.unichain.org/incident/cmhz96d4500nkrz0fk81sivx8 Unichain Mainnet Safe Head Stall Type: Incident Duration: 4 hours and 9 minutes Affected Components: Node Syncing, Public RPC, L2 Block Production, Public RPC, L1 Batch Posting, L2 Block Production, , Node Syncing, , L1 Batch Posting, Unichain Mainnet → Unichain Sepolia → Nov 3, 17:00:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Nov 3, 18:22:17 GMT+0 - Identified - We are continuing to work on a fix for this incident. Nov 3, 19:11:34 GMT+0 - Monitoring - We are posting batches, but our internal beacon chain RPC is having issues. Internal rollup nodes are unable to derive from L1, but the safe head is being advanced on-chain. Nov 3, 20:36:57 GMT+0 - Monitoring - We've identified a fix and are rolling it out. Some rollup nodes are starting to recover on mainnet already. Nov 3, 21:09:05 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 4 hours and 9 minutes

Affected Components: , , , , , , , , ,

<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>18:22:17</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>19:11:34</var> GMT+0</small><br><strong>Monitoring</strong> - We are posting batches, but our internal beacon chain RPC is having issues. Internal rollup nodes are unable to derive from L1, but the safe head is being advanced on-chain..</p> <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>20:36:57</var> GMT+0</small><br><strong>Monitoring</strong> - We've identified a fix and are rolling it out. Some rollup nodes are starting to recover on mainnet already..</p> <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>21:09:05</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 3 Nov 2025 17:00:00 +0000 https://status.unichain.org/incident/cmhji1s4p00k0148tuan0prn3 https://status.unichain.org/incident/cmhji1s4p00k0148tuan0prn3 Safe head stall and withdrawals delayed on Unichain Mainnet and Sepolia Type: Incident Duration: 3 hours and 56 minutes Affected Components: Public RPC, , Node Syncing, L1 Batch Posting, Node Syncing, Public RPC, , L2 Block Production, L1 Batch Posting, L2 Block Production, Unichain Mainnet → Unichain Sepolia → Oct 3, 17:52:39 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 15, 17:37:20 GMT+0 - Postmortem - <https://uniswaplabs.notion.site/Public-Postmortem-Unichain-Mainnet-and-Sepolia-Safe-Head-Stall-Withdrawal-Delay-28dc52b2548b802c89b7cb36af3e16e5> Oct 3, 19:42:36 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 3, 21:18:15 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 3, 20:30:16 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 3, 21:32:57 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. The safe head is currently catching up. Oct 3, 21:48:21 GMT+0 - Resolved - This incident has been resolved. Oct 3, 18:33:47 GMT+0 - Monitoring - We've identified a fix and are currently deploying and testing it. Oct 3, 19:18:15 GMT+0 - Monitoring - Still working on current fix. Type: Incident

Duration: 3 hours and 56 minutes

Affected Components: , , , , , , , , ,

<p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>17:52:39</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>17:37:20</var> GMT+0</small><br><strong>Postmortem</strong> - <https://uniswaplabs.notion.site/Public-Postmortem-Unichain-Mainnet-and-Sepolia-Safe-Head-Stall-Withdrawal-Delay-28dc52b2548b802c89b7cb36af3e16e5>.</p> <p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>19:42:36</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>21:18:15</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>20:30:16</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>21:32:57</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result. The safe head is currently catching up..</p> <p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>21:48:21</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>18:33:47</var> GMT+0</small><br><strong>Monitoring</strong> - We've identified a fix and are currently deploying and testing it..</p> <p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>19:18:15</var> GMT+0</small><br><strong>Monitoring</strong> - Still working on current fix..</p> ]]> Fri, 3 Oct 2025 17:52:39 +0000 https://status.unichain.org/incident/cmgb56k8201ghhrwxqujgmyji https://status.unichain.org/incident/cmgb56k8201ghhrwxqujgmyji Flashblocks down on Unichain Mainnet Type: Incident Duration: 13 minutes Affected Components: L2 Block Production Aug 21, 19:37:00 GMT+0 - Investigating - We are currently investigating this incident. Flashblocks are not being produced, but blocks are still being produced on the 1s block time. Aug 21, 19:50:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 13 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>19:37:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. Flashblocks are not being produced, but blocks are still being produced on the 1s block time..</p> <p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>19:50:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 21 Aug 2025 19:37:00 +0000 https://status.unichain.org/incident/cmeltlid10002ditoqktih1f6 https://status.unichain.org/incident/cmeltlid10002ditoqktih1f6 Unichain Mainnet - Batcher not submitting and safe head stall Type: Incident Duration: 15 hours and 15 minutes Affected Components: L1 Batch Posting Jul 9, 02:30:00 GMT+0 - Resolved - L1 Batch Posting is now functional. L2 safe head is advancing. Jul 9, 15:34:00 GMT+0 - Investigating - L1 Batch Posting is unable to connect to the active sequencer and is not posting batches to L1\\. L2 Safe head is stalled. Jul 9, 15:45:00 GMT+0 - Resolved - This incident has been resolved. Jul 9, 01:20:00 GMT+0 - Investigating - L1 Batch Posting is unable to connect to the active sequencer and is not posting batches to L1\. L2 Safe head is stalled. Type: Incident

Duration: 15 hours and 15 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>02:30:00</var> GMT+0</small><br><strong>Resolved</strong> - L1 Batch Posting is now functional. L2 safe head is advancing..</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>15:34:00</var> GMT+0</small><br><strong>Investigating</strong> - L1 Batch Posting is unable to connect to the active sequencer and is not posting batches to L1\\. L2 Safe head is stalled..</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>15:45:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>01:20:00</var> GMT+0</small><br><strong>Investigating</strong> - L1 Batch Posting is unable to connect to the active sequencer and is not posting batches to L1\. L2 Safe head is stalled..</p> ]]> Wed, 9 Jul 2025 01:20:00 +0000 https://status.unichain.org/incident/cmcvcwdwv001oc3nwefxc4k17 https://status.unichain.org/incident/cmcvcwdwv001oc3nwefxc4k17 Unichain Sepolia Batcher is Not Producing Batches Type: Incident Duration: 1 hour and 25 minutes Affected Components: , L1 Batch Posting, Unichain Sepolia → Jul 3, 09:53:57 GMT+0 - Resolved - This incident has been resolved. Jul 3, 08:29:00 GMT+0 - Investigating - We are currently investigating this incident. Jul 3, 09:49:22 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Type: Incident

Duration: 1 hour and 25 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>09:53:57</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>08:29:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>09:49:22</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> ]]> Thu, 3 Jul 2025 08:29:00 +0000 https://status.unichain.org/incident/cmcn4jc6f005h9mhuwe0kew7g https://status.unichain.org/incident/cmcn4jc6f005h9mhuwe0kew7g Unichain Mainnet Unsafe Head Stall Type: Incident Duration: 8 minutes Affected Components: Node Syncing, L2 Block Production, L1 Batch Posting, Public RPC Jun 6, 02:22:00 GMT+0 - Identified - Unichain Mainnet sequencer stalled for almost 10 minutes during planned maintenance period. Jun 6, 02:30:00 GMT+0 - Resolved - Active sequencer is restarted and unsafe head is progressing. Type: Incident

Duration: 8 minutes

Affected Components: , , ,

<p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>02:22:00</var> GMT+0</small><br><strong>Identified</strong> - Unichain Mainnet sequencer stalled for almost 10 minutes during planned maintenance period..</p> <p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>02:30:00</var> GMT+0</small><br><strong>Resolved</strong> - Active sequencer is restarted and unsafe head is progressing..</p> ]]> Fri, 6 Jun 2025 02:22:00 +0000 https://status.unichain.org/incident/cmbk7yqxu002dnk4624sd5jdo https://status.unichain.org/incident/cmbk7yqxu002dnk4624sd5jdo Unichain Infrastructure upgrade Type: Maintenance Duration: 18 hours and 56 minutes Affected Components: Public RPC, Node Syncing, Node Syncing, L2 Block Production, L2 Block Production, L1 Batch Posting, Public RPC, L1 Batch Posting May 22, 22:49:57 GMT+0 - Identified - Maintenance is taking longer than estimated. Unichain Sepolia is almost finished upgrading the fleet and Unichain Mainnet is pending. The Maintenance period will be increased by 2 hours. May 22, 20:33:03 GMT+0 - Identified - We are upgrading the machines running our various rollup nodes to be able to handle Unichain's growth for the foreseeable future. We do not expect any outages or downtime in this period, but large upgrades such as this can have impact on chain performance if something goes wrong. May 23, 15:29:33 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 18 hours and 56 minutes

Affected Components: , , , , , , ,

<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>22:49:57</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is taking longer than estimated. Unichain Sepolia is almost finished upgrading the fleet and Unichain Mainnet is pending. The Maintenance period will be increased by 2 hours..</p> <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>20:33:03</var> GMT+0</small><br><strong>Identified</strong> - We are upgrading the machines running our various rollup nodes to be able to handle Unichain's growth for the foreseeable future. We do not expect any outages or downtime in this period, but large upgrades such as this can have impact on chain performance if something goes wrong..</p> <p><small>May <var data-var='date'> 23</var>, <var data-var='time'>15:29:33</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Thu, 22 May 2025 20:33:03 +0000 https://status.unichain.org/maintenance/cmazu0pjy004docwbvjy5cyic https://status.unichain.org/maintenance/cmazu0pjy004docwbvjy5cyic Unichain Sepolia - Safe Head is stalled due to L1 Batcher Degradation Type: Incident Duration: 3 hours and 18 minutes Affected Components: L1 Batch Posting, Public RPC, Node Syncing, Node Syncing, L2 Block Production, L2 Block Production, L1 Batch Posting, Public RPC May 14, 02:26:28 GMT+0 - Monitoring - L1 Batches are being regularly posted now and the backlog of L2 transactions is being reduced. May 14, 01:10:00 GMT+0 - Identified - The infrastructure supporting the L1 Batcher has began OOM'ing. Engineers have identified a fix and are deploying it, currently. May 14, 04:27:51 GMT+0 - Resolved - All systems are operational and L1 batches for all transactions over the incident period have been submitted to the L1. Type: Incident

Duration: 3 hours and 18 minutes

Affected Components: , , , , , , ,

<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>02:26:28</var> GMT+0</small><br><strong>Monitoring</strong> - L1 Batches are being regularly posted now and the backlog of L2 transactions is being reduced..</p> <p><small>May <var data-var='date'> 14</var>, <var data-var='time'>01:10:00</var> GMT+0</small><br><strong>Identified</strong> - The infrastructure supporting the L1 Batcher has began OOM'ing. Engineers have identified a fix and are deploying it, currently..</p> <p><small>May <var data-var='date'> 14</var>, <var data-var='time'>04:27:51</var> GMT+0</small><br><strong>Resolved</strong> - All systems are operational and L1 batches for all transactions over the incident period have been submitted to the L1..</p> ]]> Wed, 14 May 2025 01:10:00 +0000 https://status.unichain.org/incident/cmanb3h7k003711hg74gruc70 https://status.unichain.org/incident/cmanb3h7k003711hg74gruc70 Unichain Sepolia Unsafe Head Stall Type: Incident Duration: 13 minutes Affected Components: L2 Block Production Mar 26, 20:25:00 GMT+0 - Identified - The unsafe head on Unichain Sepolia stopped due to infrastructure issues. It is now advancing again. Mar 26, 20:38:28 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 13 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>20:25:00</var> GMT+0</small><br><strong>Identified</strong> - The unsafe head on Unichain Sepolia stopped due to infrastructure issues. It is now advancing again..</p> <p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>20:38:28</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 26 Mar 2025 20:25:00 +0000 https://status.unichain.org/incident/cm8qdz9qm000fhz5swmjkwtux https://status.unichain.org/incident/cm8qdz9qm000fhz5swmjkwtux Unichain Sepolia Pectra Blob Schedule Network Upgrade Type: Maintenance Duration: 33 minutes Affected Components: Node Syncing Mar 20, 15:45:00 GMT+0 - Identified - The Pectra Blob Schedule network upgrade is scheduled for Thu Mar 20 16:00:00 UTC 2025\. Node operators must have updated their nodes by this time. See <https://docs.unichain.org/docs/updates#critical-upgrade-for-unichain-sepolia-nodes-03152025> for more information. Mar 20, 16:18:11 GMT+0 - Completed - Maintenance has completed successfully. Mar 20, 15:45:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 33 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>15:45:00</var> GMT+0</small><br><strong>Identified</strong> - The Pectra Blob Schedule network upgrade is scheduled for Thu Mar 20 16:00:00 UTC 2025\. Node operators must have updated their nodes by this time. See <https://docs.unichain.org/docs/updates#critical-upgrade-for-unichain-sepolia-nodes-03152025> for more information..</p> <p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>16:18:11</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>15:45:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Thu, 20 Mar 2025 15:45:00 +0000 https://status.unichain.org/maintenance/cm8ghp6e900flvfxds1yenx0w https://status.unichain.org/maintenance/cm8ghp6e900flvfxds1yenx0w Investigating Unichain Sepolia Batching Issues Type: Incident Affected Components: L2 Block Production, Public RPC, L1 Batch Posting, Node Syncing Mar 19, 01:17:28 GMT+0 - Resolved - All rollup nodes are recovered, L2 block production continues and L1 batch posts are going through. Type: Incident

Affected Components: , , ,

<p><small>Mar <var data-var='date'> 19</var>, <var data-var='time'>01:17:28</var> GMT+0</small><br><strong>Resolved</strong> - All rollup nodes are recovered, L2 block production continues and L1 batch posts are going through..</p> ]]> Wed, 19 Mar 2025 01:17:28 +0000 https://status.unichain.org/incident/cm8f8g33l0050tm4jlgzmekxf https://status.unichain.org/incident/cm8f8g33l0050tm4jlgzmekxf Mainnet Rollup Node upgrade Type: Maintenance Affected Components: Public RPC Mar 11, 21:42:51 GMT+0 - Completed - We are upgrading our mainnet nodes to support Pectra Type: Maintenance

Affected Components:

<p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>21:42:51</var> GMT+0</small><br><strong>Completed</strong> - We are upgrading our mainnet nodes to support Pectra.</p> ]]> Tue, 11 Mar 2025 21:42:51 +0000 https://status.unichain.org/maintenance/cm850r9yu000110keqsge7trv https://status.unichain.org/maintenance/cm850r9yu000110keqsge7trv Public RPC Experiencing High Error Rate Type: Incident Duration: 27 minutes Affected Components: Public RPC Mar 7, 21:00:00 GMT+0 - Investigating - We are currently investigating this incident. Mar 7, 21:26:53 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 27 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>21:26:53</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 7 Mar 2025 21:00:00 +0000 https://status.unichain.org/incident/cm7z9nfb4000oima88s2r52g3 https://status.unichain.org/incident/cm7z9nfb4000oima88s2r52g3 Sepolia Unichain L2 blocks not being produced by sequencer Type: Incident Duration: 29 minutes Affected Components: L2 Block Production, Public RPC Mar 5, 14:46:03 GMT+0 - Resolved - This incident has been resolved. Mar 5, 14:16:59 GMT+0 - Investigating - We are currently investigating this incident. Transactions are not posting. Type: Incident

Duration: 29 minutes

Affected Components: ,

<p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>14:46:03</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>14:16:59</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. Transactions are not posting. .</p> ]]> Wed, 5 Mar 2025 14:16:59 +0000 https://status.unichain.org/incident/cm7w04n340031k4oct3uj406d https://status.unichain.org/incident/cm7w04n340031k4oct3uj406d Sepolia Safe Head Rate Stalled Type: Incident Duration: 1 hour and 53 minutes Affected Components: L2 Block Production, Public RPC, L1 Batch Posting, Node Syncing Mar 5, 14:45:25 GMT+0 - Resolved - This incident has been resolved. Mar 5, 12:52:37 GMT+0 - Investigating - The Sepolia Unichain Batcher has stalled because of the Pectra hardfork. We are investigating. Mar 5, 13:22:49 GMT+0 - Identified - The L1 Pectra release has introduced a problem with deposit transactions and no transactions are going through L1\. We are waiting for L1 RPC partners to update to the new version geth/op-geth: <https://github.com/ethereum/go-ethereum/releases/tag/v1.15.5> Type: Incident

Duration: 1 hour and 53 minutes

Affected Components: , , ,

<p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>14:45:25</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>12:52:37</var> GMT+0</small><br><strong>Investigating</strong> - The Sepolia Unichain Batcher has stalled because of the Pectra hardfork. We are investigating..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>13:22:49</var> GMT+0</small><br><strong>Identified</strong> - The L1 Pectra release has introduced a problem with deposit transactions and no transactions are going through L1\. We are waiting for L1 RPC partners to update to the new version geth/op-geth: <https://github.com/ethereum/go-ethereum/releases/tag/v1.15.5>.</p> ]]> Wed, 5 Mar 2025 12:52:37 +0000 https://status.unichain.org/incident/cm7vx44sf001flq263e08rli7 https://status.unichain.org/incident/cm7vx44sf001flq263e08rli7 Sepolia: Safe Head Stall Type: Incident Duration: 31 minutes Affected Components: L2 Block Production, Public RPC, L1 Batch Posting, Node Syncing Mar 3, 22:50:39 GMT+0 - Resolved - This incident has been resolved. Mar 3, 22:20:00 GMT+0 - Identified - A scheduled maintenance led to an unexpected outage in our active sequencer for Unichain Sepolia. As a result the safe head being stalled until we were able to triage it. Type: Incident

Duration: 31 minutes

Affected Components: , , ,

<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>22:50:39</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>22:20:00</var> GMT+0</small><br><strong>Identified</strong> - A scheduled maintenance led to an unexpected outage in our active sequencer for Unichain Sepolia. As a result the safe head being stalled until we were able to triage it..</p> ]]> Mon, 3 Mar 2025 22:20:00 +0000 https://status.unichain.org/incident/cm7tnk64p004frrgl8rlrjhtq https://status.unichain.org/incident/cm7tnk64p004frrgl8rlrjhtq Scheduled Maintenance for Pectra release Type: Maintenance Affected Components: L2 Block Production, Public RPC Feb 26, 21:03:50 GMT+0 - Completed - We are planning for a scheduled maintenance during this time. Expect transactions to be slow on chain for this period. Type: Maintenance

Affected Components: ,

<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>21:03:50</var> GMT+0</small><br><strong>Completed</strong> - We are planning for a scheduled maintenance during this time. Expect transactions to be slow on chain for this period..</p> ]]> Wed, 26 Feb 2025 21:03:50 +0000 https://status.unichain.org/maintenance/cm7memnh6000111gt5uybv98d https://status.unichain.org/maintenance/cm7memnh6000111gt5uybv98d Transactions not being processed Type: Incident Affected Components: Public RPC Feb 26, 00:53:00 GMT+0 - Resolved - A peering issue between the sequencer and ingress nodes caused a temporary period where no transactions or deposits were processed on Unichain Sepolia. Type: Incident

Affected Components:

<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>00:53:00</var> GMT+0</small><br><strong>Resolved</strong> - A peering issue between the sequencer and ingress nodes caused a temporary period where no transactions or deposits were processed on Unichain Sepolia..</p> ]]> Wed, 26 Feb 2025 00:53:00 +0000 https://status.unichain.org/incident/cm7lboqke00kz13sb46y2yrn1 https://status.unichain.org/incident/cm7lboqke00kz13sb46y2yrn1 No new blocks produced by sequencer Type: Incident Duration: 4 hours and 10 minutes Affected Components: L2 Block Production, Public RPC, L1 Batch Posting, Node Syncing Dec 30, 15:33:00 GMT+0 - Identified - A sequencer stall has led to the sequencer needing to resync from an earlier snapshot of the chain. This has led to no new blocks being produced while the sequencers catch up. Dec 30, 19:42:59 GMT+0 - Resolved - The sequencer has recovered and is producing new blocks. Type: Incident

Duration: 4 hours and 10 minutes

Affected Components: , , ,

<p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>15:33:00</var> GMT+0</small><br><strong>Identified</strong> - A sequencer stall has led to the sequencer needing to resync from an earlier snapshot of the chain. This has led to no new blocks being produced while the sequencers catch up..</p> <p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>19:42:59</var> GMT+0</small><br><strong>Resolved</strong> - The sequencer has recovered and is producing new blocks..</p> ]]> Mon, 30 Dec 2024 15:33:00 +0000 https://status.unichain.org/incident/cm5bcjduy001a2l0soosugdtx https://status.unichain.org/incident/cm5bcjduy001a2l0soosugdtx Unichain Sepolia Safe Head Stall Type: Incident Duration: 30 days Affected Components: L1 Batch Posting, Node Syncing Dec 29, 17:00:00 GMT+0 - Resolved - This incident has been resolved. Dec 29, 05:00:00 GMT+0 - Identified - The op-node rejected some batches from the batcher and the safe head stalled out for 12 hours. Consequently, a re-org occurred. The batcher is correctly posting again. Type: Incident

Duration: 30 days

Affected Components: ,

<p><small>Dec <var data-var='date'> 29</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Dec <var data-var='date'> 29</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Identified</strong> - The op-node rejected some batches from the batcher and the safe head stalled out for 12 hours. Consequently, a re-org occurred. The batcher is correctly posting again..</p> ]]> Sun, 29 Dec 2024 05:00:00 +0000 https://status.unichain.org/incident/cm59woivt002eojkulcdt9rlw https://status.unichain.org/incident/cm59woivt002eojkulcdt9rlw Node Syncing Outage Type: Incident Affected Components: Node Syncing Dec 2, 22:25:52 GMT+0 - Resolved - Due to an issue with the batcher, there was a deep reorg. Unichain Sepolia has recovered at this time. Users who are running full (non-archive) nodes will need to re-sync the chain. Type: Incident

Affected Components:

<p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>22:25:52</var> GMT+0</small><br><strong>Resolved</strong> - Due to an issue with the batcher, there was a deep reorg. Unichain Sepolia has recovered at this time. Users who are running full (non-archive) nodes will need to re-sync the chain..</p> ]]> Mon, 2 Dec 2024 22:25:52 +0000 https://status.unichain.org/incident/cm47ln3vv00147ipnyqgfanqg https://status.unichain.org/incident/cm47ln3vv00147ipnyqgfanqg Active Sequencer stalled Type: Incident Duration: 11 hours and 28 minutes Affected Components: Public RPC, L2 Block Production, L1 Batch Posting Dec 2, 19:28:28 GMT+0 - Resolved - This incident has been resolved. Batcher operation is restored, L2 blocks are being produced and safe head latency is at normal rates. Dec 2, 08:00:00 GMT+0 - Identified - At 12:00 AM PST, our active sequencer stalled and failed to derive or produce any further blocks. We have identified the issue as being related to the communication between op-geth and op-node over the Auth RPC port. We have mitigated this issue by restarted the sequencing nodes. Type: Incident

Duration: 11 hours and 28 minutes

Affected Components: , ,

<p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>19:28:28</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Batcher operation is restored, L2 blocks are being produced and safe head latency is at normal rates..</p> <p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Identified</strong> - At 12:00 AM PST, our active sequencer stalled and failed to derive or produce any further blocks. We have identified the issue as being related to the communication between op-geth and op-node over the Auth RPC port. We have mitigated this issue by restarted the sequencing nodes..</p> ]]> Mon, 2 Dec 2024 08:00:00 +0000 https://status.unichain.org/incident/cm478l6qg004cpa98khiodtyl https://status.unichain.org/incident/cm478l6qg004cpa98khiodtyl Unichain Sepolia Public RPC Maintence Type: Maintenance Duration: 10 minutes Affected Components: Public RPC, L2 Block Production, L1 Batch Posting Nov 25, 18:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time which will affect the public RPC and sequencer URL. Nov 25, 18:07:13 GMT+0 - Completed - Public RPC maintenance is complete & the RPC is functioning again. Nov 25, 18:00:00 GMT+0 - Identified - Maintenance has been started. Type: Maintenance

Duration: 10 minutes

Affected Components: , ,

<p><small>Nov <var data-var='date'> 25</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time which will affect the public RPC and sequencer URL..</p> <p><small>Nov <var data-var='date'> 25</var>, <var data-var='time'>18:07:13</var> GMT+0</small><br><strong>Completed</strong> - Public RPC maintenance is complete & the RPC is functioning again..</p> <p><small>Nov <var data-var='date'> 25</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Identified</strong> - Maintenance has been started..</p> ]]> Mon, 25 Nov 2024 18:00:00 +0000 https://status.unichain.org/maintenance/cm3t7na36005qpfgn6hqfiehl https://status.unichain.org/maintenance/cm3t7na36005qpfgn6hqfiehl