Arbitrum: Degraded feed and sequencer endpoint performance
Is it fixed? Yes.
Resolved after <1 min. First reported Nov 18, 15:24 UTC, resolved Nov 18, 15:24 UTC. The vendor posted it on its status page first.
What happened
Arbitrum experienced degraded performance affecting the ARB1 Batch Poster and ARB1 Feed components. The incident lasted for 1 hour and 34 minutes before being fully resolved.
What caused it?
Under active investigation. No report has identified a root cause yet.
No verified workaround yet
This incident was resolved upstream without a reported workaround.
Official fixTimeline
- Investigating(done)
- Workaround available(skipped)
- Resolved(current)
Evidence
1 report · 1 StatusShow
- [1]Status First reportDegraded feed and sequencer endpoint performance(opens official status page in a new tab)
Investigating: This incident has been resolved.. Resolved: This incident has been resolved.. Affected Components: ARB1 - Batch Poster, ARB1 - Feed Duration: 1 hour and 34 minutes Type: Incident
by arbitrum status
FAQ
What happened in the Arbitrum outage?
Arbitrum experienced degraded performance affecting the ARB1 Batch Poster and ARB1 Feed components. The incident lasted for 1 hour and 34 minutes before being fully resolved.
What is affected by the Arbitrum outage?
Arbitrum.
When did the Arbitrum outage start and end?
It started Nov 18, 15:24 UTC and was resolved Nov 18, 15:24 UTC, after <1 min.
How do I get alerts for Arbitrum?
Subscribe to the Arbitrum RSS feed for every new Arbitrum incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Arbitrum is down. Arbitrum feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source, including the vendor’s own status page.