<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Arbitrum Status - Incident history</title>
    <link>https://status.arbitrum.io</link>
    <description>Arbitrum</description>
    <pubDate>Fri, 4 Sep 2026 11:02:03 +0000</pubDate>
    
<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 2 minutes

    Affected Components: ARB1 - Arbiscan
    Sep 4, 11:04:15 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Sep 4, 11:02:03 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>11:04:15</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>11:02:03</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 4 Sep 2026 11:02:03 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmtmugqyi0afx0wo5alemn1d2</link>
  <guid>https://status.arbitrum.io/incident/cmtmugqyi0afx0wo5alemn1d2</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: ARB1 - Arbiscan
    Aug 19, 10:57:26 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Aug 19, 10:56:04 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 19</var>, <var data-var='time'>10:57:26</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Aug <var data-var='date'> 19</var>, <var data-var='time'>10:56:04</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 19 Aug 2026 10:56:04 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmszz7f4q0dnf0ko0h06si5ir</link>
  <guid>https://status.arbitrum.io/incident/cmszz7f4q0dnf0ko0h06si5ir</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 4 minutes

    Affected Components: ARB1 - Arbiscan
    Aug 19, 08:02:03 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Aug 19, 07:58:05 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 19</var>, <var data-var='time'>08:02:03</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Aug <var data-var='date'> 19</var>, <var data-var='time'>07:58:05</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 19 Aug 2026 07:58:05 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmszsuiyg0jty0rmltwk36h7t</link>
  <guid>https://status.arbitrum.io/incident/cmszsuiyg0jty0rmltwk36h7t</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 7 minutes

    Affected Components: ARB1 - Arbiscan
    Jul 17, 16:49:26 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Jul 17, 16:42:05 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>16:49:26</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>16:42:05</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 17 Jul 2026 16:42:05 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmrp61aln0e4z1amrzci4e45y</link>
  <guid>https://status.arbitrum.io/incident/cmrp61aln0e4z1amrzci4e45y</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 1 hour and 9 minutes

    Affected Components: ARB1 - Arbiscan
    Jul 14, 07:54:03 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Jul 14, 07:54:03 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Jul 14, 06:45:04 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 9 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>07:54:03</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>07:54:03</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>06:45:04</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 14 Jul 2026 06:45:04 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmrkadyms07pf0zo29fhzkk97</link>
  <guid>https://status.arbitrum.io/incident/cmrkadyms07pf0zo29fhzkk97</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 31 minutes

    Affected Components: ARB1 - Arbiscan
    Jul 14, 06:08:31 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Jul 14, 05:37:05 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 31 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>06:08:31</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>05:37:05</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 14 Jul 2026 05:37:05 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmrk7yjhp08hs0kpn3wnsri2i</link>
  <guid>https://status.arbitrum.io/incident/cmrk7yjhp08hs0kpn3wnsri2i</guid>
</item>

<item>
  <title>Intermittent feed connection issues </title>
  <description>
    Type: Incident
    Duration: 16 minutes

    Affected Components: NOVA - Feed, ARB1 - Feed
    May 20, 20:11:00 GMT+0 - Resolved - This incident has been resolved. May 20, 19:55:00 GMT+0 - Investigating - We have been made aware of feed connection issues and are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 16 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>May <var data-var='date'> 20</var>, <var data-var='time'>20:11:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>19:55:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We have been made aware of feed connection issues and are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 20 May 2026 19:55:00 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmpfn10dh00o0peksqhe3iqz7</link>
  <guid>https://status.arbitrum.io/incident/cmpfn10dh00o0peksqhe3iqz7</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: ARB1 - Arbiscan
    May 18, 07:20:05 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. May 18, 07:19:05 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 18</var>, <var data-var='time'>07:20:05</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>May <var data-var='date'> 18</var>, <var data-var='time'>07:19:05</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 18 May 2026 07:19:05 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmpavi5rw006ppad3816aht08</link>
  <guid>https://status.arbitrum.io/incident/cmpavi5rw006ppad3816aht08</guid>
</item>

<item>
  <title>Delays in posting an assertion.</title>
  <description>
    Type: Incident
    Duration: 30 minutes

    Affected Components: ARB1 - Validator
    May 13, 10:18:00 GMT+0 - Resolved - This incident has been resolved. An assertion was posted and all network components are fully operational. May 13, 01:29:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 13, 00:59:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>10:18:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved. An assertion was posted and all network components are fully operational..</p>
<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>01:29:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>00:59:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 13 May 2026 00:59:00 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmp3wf80i0016p8a0ycsul724</link>
  <guid>https://status.arbitrum.io/incident/cmp3wf80i0016p8a0ycsul724</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: ARB1 - Arbiscan
    May 10, 14:16:06 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. May 10, 14:15:18 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 10</var>, <var data-var='time'>14:16:06</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>May <var data-var='date'> 10</var>, <var data-var='time'>14:15:18</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 10 May 2026 14:15:18 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmozuulkw03gf1d1l71g3ejxo</link>
  <guid>https://status.arbitrum.io/incident/cmozuulkw03gf1d1l71g3ejxo</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 2 minutes

    Affected Components: ARB1 - Arbiscan
    Mar 30, 07:24:06 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Mar 30, 07:22:06 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>07:24:06</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>07:22:06</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 30 Mar 2026 07:22:06 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmncv1a9x000xu8ji6lk5znq2</link>
  <guid>https://status.arbitrum.io/incident/cmncv1a9x000xu8ji6lk5znq2</guid>
</item>

<item>
  <title>Block production halted</title>
  <description>
    Type: Incident
    Duration: 6 hours and 8 minutes

    Affected Components: SEPOLIA - Batch Poster, SEPOLIA - Feed, SEPOLIA - Sequencer, SEPOLIA - Validator
    Mar 23, 22:37:04 GMT+0 - Resolved - Arbitrum Sepolia block production has been restored. Transactions and deployments on the Arbitrum Sepolia network should now be working as usual again.

   Mar 23, 16:30:16 GMT+0 - Identified - We are continuing to work on a fix for this incident. Mar 23, 16:29:24 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 8 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>22:37:04</var> GMT+0</small><br><strong>Resolved</strong> -
  Arbitrum Sepolia block production has been restored. Transactions and deployments on the Arbitrum Sepolia network should now be working as usual again.

  .</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>16:30:16</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'> 23</var>, <var data-var='time'>16:29:24</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 23 Mar 2026 16:29:24 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmn3ei5pb13zs995pku585l4s</link>
  <guid>https://status.arbitrum.io/incident/cmn3ei5pb13zs995pku585l4s</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 15 minutes

    Affected Components: ARB1 - Arbiscan
    Mar 9, 07:49:14 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Mar 9, 07:34:04 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>07:49:14</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>07:34:04</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 9 Mar 2026 07:34:04 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmmiv7sym04bozhqksaf5i5ny</link>
  <guid>https://status.arbitrum.io/incident/cmmiv7sym04bozhqksaf5i5ny</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: ARB1 - Arbiscan
    Feb 16, 00:13:04 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Feb 16, 00:12:04 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>00:13:04</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>00:12:04</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 16 Feb 2026 00:12:04 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmlof6i0s0pp6m1zog6eioe0w</link>
  <guid>https://status.arbitrum.io/incident/cmlof6i0s0pp6m1zog6eioe0w</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 6 minutes

    Affected Components: ARB1 - Arbiscan
    Feb 9, 07:26:05 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Feb 9, 07:20:03 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>07:26:05</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>07:20:03</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 9 Feb 2026 07:20:03 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmleudx7404kn10n5ysb5twnf</link>
  <guid>https://status.arbitrum.io/incident/cmleudx7404kn10n5ysb5twnf</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: ARB1 - Arbiscan
    Feb 8, 05:16:04 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Feb 8, 05:15:03 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>05:16:04</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>05:15:03</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 8 Feb 2026 05:15:03 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmldahbp80emtgop89umx5zyo</link>
  <guid>https://status.arbitrum.io/incident/cmldahbp80emtgop89umx5zyo</guid>
</item>

<item>
  <title>Delays in posting an assertion. </title>
  <description>
    Type: Incident
    Duration: 11 hours and 37 minutes

    Affected Components: ARB1 - Validator
    Feb 6, 04:37:20 GMT+0 - Resolved - This incident has been resolved. An assertion was posted and all network components are fully operational.  Feb 5, 22:29:51 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 5, 17:00:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 37 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>04:37:20</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved. An assertion was posted and all network components are fully operational. .</p>
<p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>22:29:51</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 5 Feb 2026 17:00:00 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cml9znj2r00cjuy23b9699i0v</link>
  <guid>https://status.arbitrum.io/incident/cml9znj2r00cjuy23b9699i0v</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: ARB1 - Arbiscan
    Feb 3, 00:01:06 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Feb 3, 00:00:04 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>00:01:06</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>00:00:04</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 3 Feb 2026 00:00:04 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cml5u0zbh00cf5g8v7apvhdvf</link>
  <guid>https://status.arbitrum.io/incident/cml5u0zbh00cf5g8v7apvhdvf</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 45 minutes

    Affected Components: ARB1 - Arbiscan
    Jan 26, 03:07:05 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Jan 26, 02:22:04 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 45 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>03:07:05</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>02:22:04</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 26 Jan 2026 02:22:04 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmkujksif04fcz20r16molbyq</link>
  <guid>https://status.arbitrum.io/incident/cmkujksif04fcz20r16molbyq</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 1 hour and 18 minutes

    Affected Components: ARB1 - Arbiscan
    Jan 26, 01:41:05 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Jan 26, 00:23:04 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 18 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>01:41:05</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>00:23:04</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 26 Jan 2026 00:23:04 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmkufbr5401faboz77gro05lp</link>
  <guid>https://status.arbitrum.io/incident/cmkufbr5401faboz77gro05lp</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 27 minutes

    Affected Components: ARB1 - Arbiscan
    Jan 21, 10:46:05 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Jan 21, 10:19:05 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 27 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>10:46:05</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>10:19:05</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 21 Jan 2026 10:19:05 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmknvez5d09nlfzzynusj1hhc</link>
  <guid>https://status.arbitrum.io/incident/cmknvez5d09nlfzzynusj1hhc</guid>
</item>

<item>
  <title>Batch posting issue</title>
  <description>
    Type: Incident
    Duration: 4 hours and 2 minutes

    Affected Components: ARB1 - Batch Poster
    Jan 7, 06:32:17 GMT+0 - Resolved - This incident has been resolved. Jan 7, 02:30:36 GMT+0 - Investigating - An infrastructure issue temporarily prevented posting batches to mainnet, we are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>06:32:17</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>02:30:36</var> GMT+0</small><br><strong>Investigating</strong> -
  An infrastructure issue temporarily prevented posting batches to mainnet, we are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 7 Jan 2026 02:30:36 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmk3hc4qf03be1et0bxvpym69</link>
  <guid>https://status.arbitrum.io/incident/cmk3hc4qf03be1et0bxvpym69</guid>
</item>

<item>
  <title>NOVA - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 7 minutes

    
    Nov 21, 08:36:08 GMT+0 - Resolved - NOVA - Arbiscan is now operational! This update was created by an automated monitoring service. Nov 21, 08:29:06 GMT+0 - Investigating - NOVA - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 minutes</p>
    
    <p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>08:36:08</var> GMT+0</small><br><strong>Resolved</strong> -
  NOVA - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>08:29:06</var> GMT+0</small><br><strong>Investigating</strong> -
  NOVA - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 21 Nov 2025 08:29:06 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmi8lmkpx007fcupnflechabg</link>
  <guid>https://status.arbitrum.io/incident/cmi8lmkpx007fcupnflechabg</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: ARB1 - Arbiscan
    Nov 18, 12:32:06 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Nov 18, 12:31:04 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>12:32:06</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>12:31:04</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 18 Nov 2025 12:31:04 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmi4jy6cz00n8xa5e0ajwjz48</link>
  <guid>https://status.arbitrum.io/incident/cmi4jy6cz00n8xa5e0ajwjz48</guid>
</item>

<item>
  <title>ARB1 - Arbiscan outage</title>
  <description>
    Type: Incident
    Duration: 5 minutes

    Affected Components: ARB1 - Arbiscan
    Nov 18, 12:13:05 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Nov 18, 12:13:05 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Nov 18, 12:13:05 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Nov 18, 12:13:05 GMT+0 - Resolved - ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service. Nov 18, 12:08:04 GMT+0 - Investigating - ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>12:13:05</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>12:13:05</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>12:13:05</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>12:13:05</var> GMT+0</small><br><strong>Resolved</strong> -
  ARB1 - Arbiscan is now operational! This update was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>12:08:04</var> GMT+0</small><br><strong>Investigating</strong> -
  ARB1 - Arbiscan cannot be accessed at the moment. More details, including information about planned outages, can be found on the [Arbiscan status page](https://arbiscan.freshstatus.io/). This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 18 Nov 2025 12:08:04 +0000</pubDate>
  <link>https://status.arbitrum.io/incident/cmi4j4lhg00nry2xtno7vp9rg</link>
  <guid>https://status.arbitrum.io/incident/cmi4j4lhg00nry2xtno7vp9rg</guid>
</item>

<item>
  <title>Routine Timeboost Auctioneer maintenance</title>
  <description>
    Type: Maintenance
    Duration: 5 hours

    Affected Components: ARB1 - Batch Poster, ARB1 - Arbiscan, , ARB1 - Validator, ARB1 - Feed, , 
ARB1 - Sequencer → 
ARB1 →
    Jun 9, 19:00:00 GMT+0 - Completed - Maintenance has completed successfully. Jun 9, 14:00:00 GMT+0 - Identified - We are planning a scheduled/routine Timeboost-related maintenance window during this time. Timeboost bids will not be accepted during this time, but all other chain operations are expected to function as usual. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 hours</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    <p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning a scheduled/routine Timeboost-related maintenance window during this time. Timeboost bids will not be accepted during this time, but all other chain operations are expected to function as usual..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 9 Jun 2025 14:00:00 +0000</pubDate>
  <link>https://status.arbitrum.io/maintenance/cmbie4qgd0022dq32vl19ds1j</link>
  <guid>https://status.arbitrum.io/maintenance/cmbie4qgd0022dq32vl19ds1j</guid>
</item>

  </channel>
  </rss>