Arbitrum logo

Is Arbitrum Down?

SaaSLive status, outages, and incident history

No. Arbitrum is up right now.

Every monitored Arbitrum system is operational as of November 10, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · every 60s

Know the moment Arbitrum breaks

Arbitrum is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Arbitrum status page
How we know: the official Arbitrum status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Arbitrum Status Summary

As of 01:16 UTC on 10 November 2026, Arbitrum is operational. PulsAPI checked Arbitrum's official status page and found 12 of 12 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Arbitrum, counting degraded performance as up. The latest incident, "ARB1 - Arbiscan outage", was on Aug 19, 2026 and lasted 6 min.

Cite as: PulsAPI, “Arbitrum status”, checked 10 November 2026, 01:16 UTC. https://www.pulsapi.com/services/arbitrum

Arbitrum Component Status

The main Arbitrum systems on this page. All 12 are operational right now.

12operational
ARB1 - Sequencer » ARB1 - Batch Poster
Operational
ARB1 » ARB1 - Arbiscan
Operational
ARB1 » ARB1 - Feed
Operational

9 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking ARB1 » ARB1 - Validator, NOVA » NOVA - Batch Poster, NOVA » NOVA - Feed, NOVA » NOVA - Sequencer, NOVA » NOVA - Validator, SEPOLIA » SEPOLIA - Batch Poster, SEPOLIA » SEPOLIA - Feed, SEPOLIA » SEPOLIA - Sequencer, SEPOLIA » SEPOLIA - Validator.

See all of them free

Component statuses may change independently during partial outages.

Recent Arbitrum Outages & Incidents

Incident history from the official Arbitrum status page, including resolution updates.

ARB1 - Arbiscan outageResolved Aug 19, 2026 · 6 minResolved

Arbitrum Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Arbitrum incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 12100.00% average · 1 day with incidentsNov 10

Going further back: Arbitrum uptime by month and every recorded Arbitrum outage.

Live Arbitrum Outage Reports

Problems reported by engineers using Arbitrum. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Arbitrum problems reported yet.

Something wrong with Arbitrum on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Arbitrum

Arbitrum publishes overall service health on its public status page at status.arbitrum.io. PulsAPI tracks Arbitrum outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Arbitrum uptime at 100.00%. Response times, incident history, and SLA tracking for Arbitrum are available on the PulsAPI dashboard.

Arbitrum Status FAQ

Is Arbitrum down right now?

The verdict at the top of this page comes from the latest poll of the official Arbitrum status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Arbitrum is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Arbitrum recovers.

How do I check Arbitrum uptime history?

PulsAPI tracks Arbitrum uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Arbitrum changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Arbitrum outages?

PulsAPI reads the official Arbitrum status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Arbitrum components?

Yes. PulsAPI monitors 12 individual Arbitrum components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Arbitrum goes down?

Yes. Create a free account and subscribe to Arbitrum: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Arbitrum to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Arbitrum problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Arbitrum?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Arbitrum plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Arbitrum with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services