Arbitrum - Arbitrum Sepolia Outage – Incident details

All systems operational

This page covers status and maintenance information for Arbitrum Networks including: Arbitrum One, Arbitrum Nova, Arbitrum Sepolia, and the Stylus Testnet. Arbiscan status updates and details for Arbitrum One and Nova can be found on the official Arbiscan status page, which will include information on planned outages.

For the status of network upgrades (e.g. ArbOS versions), please visit the network upgrades page.

Arbitrum Sepolia Outage

Resolved
Major outage
Started 5 months agoLasted 3 days

Affected

SEPOLIA

Major outage from 6:44 AM to 9:02 PM, Degraded performance from 9:02 PM to 5:11 PM, Partial outage from 5:11 PM to 8:04 PM, Degraded performance from 8:04 PM to 12:12 AM

SEPOLIA - Sequencer

Major outage from 6:44 AM to 9:02 PM, Degraded performance from 9:02 PM to 5:11 PM, Partial outage from 5:11 PM to 8:04 PM, Degraded performance from 8:04 PM to 12:12 AM

SEPOLIA - Batch Poster

Major outage from 6:44 AM to 9:02 PM, Degraded performance from 9:02 PM to 5:11 PM, Partial outage from 5:11 PM to 8:04 PM, Degraded performance from 8:04 PM to 12:12 AM

SEPOLIA - Validator

Major outage from 6:44 AM to 9:02 PM, Degraded performance from 9:02 PM to 5:11 PM, Partial outage from 5:11 PM to 8:04 PM, Degraded performance from 8:04 PM to 12:12 AM

SEPOLIA - Feed

Major outage from 6:44 AM to 9:02 PM, Degraded performance from 9:02 PM to 5:11 PM, Partial outage from 5:11 PM to 8:04 PM, Degraded performance from 8:04 PM to 12:12 AM

Updates
  • Resolved
    Resolved

    Arbitrum Sepolia is back online.

  • Monitoring
    Monitoring

    We've disabled feed signing on Arbitrum Sepolia to bring the network back online while we root cause the issue and work on a fix. Arbitrum Sepolia nodes on 3.7.6 should now be healthy again and properly syncing the chain.

    If you are running an Arbitrum Sepolia node on 3.8.0 (on any rc version), your node will gracefully shut down and so action is required to restart your node with the following flag in order to get your node syncing again with Arbitrum Sepolia.

    --node.feed.input.verify.dangerous.accept-missing


    We will continue our investigation and will cut a new release shortly. Thanks for your understanding and patience.

  • Identified
    Identified

    We've received reports that Arbitrum Sepolia node operators are unable to sync and progress with the chain. We are currently investigating.

  • Update
    Update

    We've identified & resolved a separate issue: After the Ethereum L1 Sepolia Fusaka hard fork, Arbitrum Sepolia had an issue posting batches after block 9409579. This is now resolved, and the batch poster has been posting blocks since block 9409825.

  • Monitoring
    Monitoring

    We've identified the issue: a deviation occurred on Arbitrum Sepolia at block204606366 with nodes running on ARM and x86 reaching different results. Arbitrum Sepolia nodes running on ARM CPU architectures are asked to switch over to servers that use x86 CPU architectures instead. Node's who are synced to Arbitrum Sepolia using x86 architecutres are unimpacted and no action is required at this time.

    Teams who wish to run ARM based nodes can do so once we release a new database snapshot to sync from (coming soon), alongside a new version of Nitro that addresses this fix (also coming soon).

  • Investigating
    Investigating

    We've received alerts and reports from Arbitrum Sepolia node operators relating to their nodes being unable to properly sync the chain. Our team is actively working on a fix and will communicate updates shortly.