R2 logo

Is R2 Down?

Cloud InfrastructureLive status, outages, and incident history

Partly. Some of R2 is down.

R2 is in a partial outage as of October 30, 2026. Some components are down and others are still running, so check the list below to see whether your region or feature is affected.

Partial OutageChecked just nowLive · 60s while moving10 active incidents

Don't find out like this next time

You searched to find out R2 was down. Next time we tell you, usually before your customers do, and always before you think to check.

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

How we know: the official R2 status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

R2 Component Status

75 of 578 R2 components are impaired. Worst problems listed first.

30major outage4partial outage41degraded5maintenance498operational
Africa » Addis Ababa, Ethiopia -
Major Outage
Africa » Annaba, Algeria -
Major Outage
Africa » Djibouti, Djibouti -
Major Outage

575 more components tracked

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

Also tracking Africa » Lilongwe, Malawi -, Asia » Anshun, China -, Asia » Bishkek, Kyrgyzstan -, Asia » Chongqing, China -, Asia » Hagatna, Guam -, Asia » Johor Bahru, Malaysia -, Asia » Johor Bahru, Malaysia - (JHB), Asia » Shenzhen, China -, Asia » Xiangyang, China -, Asia » Xinyu, China -, Europe » Saint Petersburg, Russia -, Latin America & the Caribbean » Arica, Chile -, and 563 more.

See all of them free

Component statuses may change independently during partial outages.

Recent R2 Outages & Incidents

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

EWR (Newark) on 2026-11-06Scheduled for Nov 6, 2026 · 8h 0mScheduled

We will be performing scheduled maintenance in EWR (Newark) datacenter on 2026-11-06 between 06:00 and 14:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.

EWR (Newark) on 2026-11-05Scheduled for Nov 5, 2026 · 8h 0mScheduled

We will be performing scheduled maintenance in EWR (Newark) datacenter on 2026-11-05 between 06:00 and 14:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.

KHI (Karachi) on 2026-11-04Scheduled for Nov 4, 2026 · 4h 0mScheduled

We will be performing scheduled maintenance in KHI (Karachi) datacenter between 2026-11-04 21:00 and 2026-11-05 01:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable. You can now subscribe to these notifications via Cloudflare dashboard and receive these updates directly via email, PagerDuty and webhooks (based on your plan): https://developers.cloudflare.com/notifications/notification-available/#cloudflare-status.

R2 Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a R2 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 1100.00% average · 91 days with incidentsOct 30

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

Live R2 Outage Reports

Problems reported by engineers using R2. 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 R2 problems reported yet.

Are you seeing R2 problems too?

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

About R2

Cloudflare R2 is an S3-compatible object storage service without egress fees to Workers and compatible integrations. Disruptions can affect media hosting and static asset pipelines using R2 buckets. Track Cloudflare R2 status and outages here.

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

R2 Status FAQ

Is R2 down right now?

The verdict at the top of this page comes from the latest poll of the official R2 status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if R2 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 R2 recovers.

How do I check R2 uptime history?

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

How fast does PulsAPI detect R2 outages?

PulsAPI reads the official R2 status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual R2 components?

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

Can I get alerts when R2 goes down?

Yes. Create a free account and subscribe to R2: 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 R2 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 R2 problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor R2?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so R2 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 R2 with the rest of your stack

2463+ 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