- Level
- confirmed
- Worst impact
- Degraded
- Components
- Ahmedabad, India - (AMD), Adelaide, Australia - (ADL), Auckland, New Zealand - (AKL), Almaty, Kazakhstan - (ALA), Brisbane, Australia - (BNE), Bangalore, India - (BLR), Canberra, Australia - (CBR), Christchurch, New Zealand - (CHC), Bangkok, Thailand - (BKK), Bandar Seri Begawan, Brunei - (BWN), Hagatna, Guam - (GUM), Melbourne, Australia - (MEL), Cebu, Philippines - (CEB), Noumea, New Caledonia - (NOU), Chandigarh, India - (IXC), Perth, Australia - (PER), Sydney, Australia - (SYD), Changde, China - (CGD), Tahiti, French Polynesia - (PPT), Chennai, India - (MAA), Suva, Fiji - (SUV), R2, Chittagong, Bangladesh - (CGP), Hobart, Australia - (HBA), Colombo, Sri Lanka - (CMB), Dhaka, Bangladesh - (DAC), Foshan, China - (FUO), Fukuoka, Japan - (FUK), Fuzhou, China - (FOC), Guangzhou, China - (CAN), Chengmai, China - (HAK), Hanoi, Vietnam - (HAN), Hengshui, China - (SJW), Ho Chi Minh City, Vietnam - (SGN), Hong Kong - (HKG), Hyderabad, India - (HYD), Islamabad, Pakistan - (ISB), Jakarta, Indonesia - (CGK), Jinan, China - (TNA), Johor Bahru, Malaysia - (JHB), Kanpur, India - (KNU), Kaohsiung City - (KHH), Karachi, Pakistan - (KHI), Kathmandu, Nepal - (KTM), Kolkata, India - (CCU), Kuala Lumpur, Malaysia - (KUL), Beijing, China - (PKX), Macau - (MFM), Male, Maldives - (MLE), Manila, Philippines - (MNL), Mumbai, India - (BOM), Nagpur, India - (NAG), Naha, Japan - (OKA), New Delhi, India - (DEL), Osaka, Japan - (KIX), Patna, India - (PAT), Phnom Penh, Cambodia - (PNH), Qingdao, China - (TAO), Seoul, South Korea - (ICN), Shanghai, China - (SHA), Singapore, Singapore - (SIN), Surat Thani, Thailand - (URT), Taipei - (TPE), Tokyo, Japan - (NRT), Ulaanbaatar, Mongolia - (ULN), Vientiane, Laos - (VTE), Nanchang, China - (KHN), Yerevan, Armenia - (EVN), Yogyakarta, Indonesia - (JOG), Cagayan de Oro, Philippines - (CGY), Kochi, India - (COK), Denpasar, Indonesia - (DPS), Kannur, India - (CNN), Shenzhen, China - (SZX), Guiyang, China - (KWE), Shaoxing, China - (HGH), Changzhou, China - (CZX), Kunming, China - (KMG), Chiang Mai, Thailand - (CNX), Zhengzhou, China - (CGO), Yangquan, China - (TYN), Changsha, China - (CSX), Dalian, China - (DLC), Chongqing, China - (CKG), Xiangyang, China - (XFN), Da Nang, Vietnam - (DAD), Jiaxing, China - (JXG), Tarlac City, Philippines - (CRK), Thimphu, Bhutan - (PBH), Baoji, China - (XIY), Kuching, Malaysia - (KCH), Aktobe, Kazakhstan - (AKX), Tongren, China - (TEN), Taizhou, China - (HYN), Bishkek, Kyrgyzstan - (FRU)
- Regions
- apac, au, in, jp
- Down Index
- 42of 100
What to do
Check whether you use Cloudflare Workers Ahmedabad, India - (AMD), Adelaide, Australia - (ADL), Auckland, New Zealand - (AKL), Almaty, Kazakhstan - (ALA) and 91 more in apac, au, in, jp. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2025-11-05 22:24 UTC and 2025-11-05 22:24 UTC may need a replay.Subscribe to Cloudflare Workers's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=cloudflare-workers works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Cloudflare Workers 1
- resolved
During 21:40 - 21:52 UTC R2 buckets in the APAC region may have experienced an elevated error rate.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-48c2aa0509
Is Cloudflare Workers still down?
No, this incident was resolved 2025-11-05 22:24 UTC. For Cloudflare Workers's live state, see https://down.guide/cloudflare-workers.
How long did it last?
0m, from 2025-11-05 22:24 UTC to 2025-11-05 22:24 UTC, by the times Cloudflare Workers posted.
What was affected?
Cloudflare Workers named Ahmedabad, India - (AMD), Adelaide, Australia - (ADL), Auckland, New Zealand - (AKL), Almaty, Kazakhstan - (ALA) and 91 more in apac, au, in, jp.
What caused it?
Cloudflare Workers hasn't published a root cause. If it does, it shows here.
Where does this come from?
Cloudflare Workers's official status page, https://www.cloudflarestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.