I-Google Cloud yahluleka ngenxa yendawo engenalutho. Amahora amathathu.
Umugqa wenqubomgomo onezindawo ezimbalwa ezingenamuntu uhlangabezana ne-null pointer, futhi i-Google Cloud iyahluleka kuzo zonke izifunda ngesikhathi esisodwa — bese i-Cloudflare nayo iyawa.
Umugqa wenqubomgomo onezindawo ezimbalwa ezingenamuntu uhlangabezana ne-null pointer, futhi i-Google Cloud iyahluleka kuzo zonke izifunda ngesikhathi esisodwa — bese i-Cloudflare nayo iyawa. Juni 12, 2025, 17:49 UTC: I-Service Control, i-binary evumela yonke i-Google Cloud API request, ifunda ushintsho lwenqubomgomo ye-quota "enezindawo ezingahlosile ezingenalutho", ihlangabezana nekhodi ethunyelwe emasontweni amabili ngaphambili ngaphandle kokuhlola i-null futhi ngaphandle kwefulegi lesici, futhi ingena ku-crash loop kuzo zonke izifunda — umugqa wawusatshalaliswe emhlabeni jikelele ngemizuzwana. Ama-API angaphandle abuyisa u-503 amahora amathathu; i-us-central1 ithatha amahora ama-2 nemizuzu engama-40 ngoba imisebenzi eqalayo ishanela itafula elifanayo le-Spanner ngaphandle kokubuyiselwa emuva okungahleliwe. Emizuzwini emithathu yokukhubazeka kwe-Google, i-Workers KV ye-Cloudflare — lapho umthombo weqiniso uhlala khona ku-"umhlinzeki wefu wenkampani yesithathu" — ilahlekelwa u-90 % wezicelo, kanti i-Access, i-WARP, i-Workers AI, i-Pages, i-Stream ne-Turnstile nayo iyawa amahora ama-2 nemizuzu engama-28. Ikhasi lesimo le-Google lithumela isibuyekezo salo sokuqala ngemuva kwehora, ngoba lisebenza ku-Google Cloud.
Funda uhlelo olubhaliwe (isiNgisi) ↗
Lokho okuhlanganiswa yile vidiyo
- Indawo engenalutho, i-null pointer, yonke indawo
- Ulayini wesikhathi: Meyi 29 → 17:45 → i-crash loop → inkinobho ebomvu → 17:52 Cloudflare
- us-central1: umthelela womhlambi
- Inqubo: hlola endleleni yesicelo, ukusatshalaliswa komhlaba wonke, umthengisi oyedwa
- git blame — ukuhlukana
Imibuzo nezimpendulo
Yini eyabangela ukuphazamiseka kwe-Google Cloud ngoJuni 12, 2025?
Ulayini wenqubomgomo yesilinganiso onamasimu angenalutho ugoqe i-Service Control, okuyibhina elivuma zonke izicelo ze-Google Cloud API. Ngokombiko kaGoogle wesigameko, ulayini wawungena endleleni yekhodi engenakho ukuhlola okungenalutho futhi engenayo ifulegi lesici, kwathi ibhina langena kumjikelezo wokuphahlazeka kuzo zonke izifunda. Ama-API angaphandle abuyisa amaphutha angu-503 cishe amahora amathathu.
Kungani ukuqala kabusha izinsizakalo kungenza ukuphazamiseka kwefu kuhlale isikhathi eside esifundeni esisodwa?
Imisebenzi eminingi eqala kabusha ngesikhathi esisodwa ingagcwalisa isizindalwazi esabiwe esifanayo. E-us-central1, imisebenzi kaGoogle eqala kabusha yagijimisela etafuleni le-Spanner elingenakho ukuhlehla okungahleliwe, ngakho-ke iGoogle yawabamba ngesandla. Leso sifunda sathatha amahora amabili namashumi amane ukululama, kanti ezinye izifunda zalulama ngo-19:48.
Kungani izinsizakalo ze-Cloudflare zehluleka lapho i-Google Cloud ihluleka?
I-Workers KV ye-Cloudflare igcine umthombo wayo weqiniso kumhlinzeki wefu wenkampani yesithathu. Ngokusho kwe-Cloudflare, i-Workers KV yalahlekelwa u-90% wezicelo, kwathi i-Access, i-WARP, i-Workers AI, i-Pages, i-Stream ne-Turnstile yehla nayo amahora angu-2 nemizuzu engu-28. Lesi sigameko siphawula ukuthi i-Workers KV yayiphakathi nokufuduka iye endaweni yokugcina ye-R2 ye-Cloudflare.
Amaqembu angawumisa kanjani ulayini wokumisa okubi ukuthi ungahluleki isevisi kuso sonke isifunda?
Kunemikhuba emithathu elandela lesi sigameko. Gcina ikhodi entsha ngemuva kwefulegi lesici elihamba, hlola ukuthi akukho lutho lapho idatha ingena khona, futhi uhlele idatha yesilinganiso esikhundleni sokuyiphindaphinda emhlabeni jikelele ngesikhathi esisodwa. Umbiko kaGoogle uthi ifulegi belingabamba iphutha esigabeni sokuhlola, futhi izilungiso zawo zihlanganisa ukwehluleka okuvulekile nokuhlehla okuyisilayidi.
Ingabe izitatimende zangemuva kwezinsiza ze-Google Cloud ne-Cloudflare ezivela ngoJuni 12 zibeka isibonelo esihle semibiko yesigameko?
Isinqumo se-The Daily Diff sasiyi-SHIP IT. Zombili izitatimende zangemuva kwezinsiza zafika phakathi kwamahora angamashumi amathathu futhi zombili zasola izinkampani zazo. Izilungiso zikaGoogle zazinokuqondakala, okungukuthi ukwehluleka okuvulekile, amafulegi avaliwe ngokuzenzakalelayo nokuhlehla okuyisilayidi. Isifundo sangoMsombuluko ukuthumela ikhodi entsha ngemuva kwefulegi eliqala livulekile.
Umbhalo obhaliwe ohunyushwe
Kuhunyushwe kusuka ekulandiseni kokuqala kwesiNgisi. Umsindo namazwibela atholakalayo alawulwa yi-YouTube.
Indawo engenalutho, i-null pointer, yonke indawo
0:00 Umugqa wenqubomgomo onezindawo ezingenamuntu uhlangabezana ne-null pointer, futhi i-Google Cloud iyahluleka ku zonke izifunda ngesikhathi esisodwa — futhi i-Cloudflare nayo iyawa, bese ibiza i-Google "umhlinzeki wenkampani yesithathu". Juni 12, 2025, 17:49 UTC. Umbiko we-Google: I-Service Control, i-binary evumela yonke i-API request, ku-crash loop amahora amathathu. Eka-Cloudflare, ngalobo busuku obufanayo: I-Workers KV, amaphesenti angamashumi ayisishiyagalolunye ehlulekile, amahora amabili nemizuzu engamashumi amabili nesishiyagalombili.
0:23 Ukuthi kwenzekeni, ukuthi kungani indawo eyodwa engenalutho yasatshalaliswa emhlabeni jikelele ngemizuzwana, nokuthi ubani ofanele ukusolwa. Lokhu yi-The Daily Diff, i-postmortem. Meyi 29. I-Service Control ithola ukuhlola okusha kwe-quota, ethunyelwa isifunda ngesifunda nge
Ulayini wesikhathi: Meyi 29 → 17:45 → i-crash loop → inkinobho ebomvu → 17:52 Cloudflare
0:35 inkinobho ebomvu — kodwa indlela yekhodi entsha ayikaze isebenze ngesikhathi sokukhipha; akukho okuqala okwamanje. Akukho ukuhlola i-null. Alikho ifulegi lesici. 17:45. Ushintsho lwenqubomgomo lwezindawo ezingenamuntu lufika etafuleni le-Spanner. I-Quota isatshalaliswa emhlabeni wonke, ngakho umugqa usatshalaliswa yonke indawo ngemizuzwana. Yonke i-Service Control binary iyayifunda, ihlangabezane ne-null pointer, iyahluleka, iqala kabusha, iyifunda futhi. Yonke i-API call: 503.
0:55 I-Google iyashesha: ukuhlela ngemizuzu emibili, imbangela enkulu ngeshumi. Inkinobho ebomvu iphuma ngamashumi amane, nezifunda ezincane ziyalulama kuqala. Ikhasi lesimo lithumela isibuyekezo salo sokuqala ngemuva kwehora, ngoba lisebenza ku-Google Cloud. 17:52. Ithimba le-Cloudflare WARP libona amadivayisi amasha ehluleka ukubhalisa. I-Workers KV, ingxenye yesitolo se-Cloudflare esetshenziselwa ukucushwa nobunikazi, ihlala ku-cloud yenkampani yesithathu. I-Access iyahluleka yonke ukungena ngemvume — ngokwengqondo, iyahluleka ukuvala.
1:20 I-Workers AI iyahluleka yonke i-inference. 19:11, Gergely Orosz: amafu amabili azimele ehluleka ngesikhathi esisodwa, akukaze kubonwe ngaphambili. 19:32, I-Google support itshela umsebenzisi ukuthi azikho iziphazamiso ezaziwayo — zama ukusula ama-cookies akho. Konke okunye kuyalulama ngo-19:48.
us-central1: umthelela womhlambi
1:34 us-central1 ayenzi: imisebenzi eqalayo ishanela itafula elifanayo le-Spanner, akukho ukubuyiselwa emuva okungahleliwe, ngakho i-Google iyabanciphisa ngesandla. Amahore amabili nemizuzu engamashumi amane. Okokuqala: ukuhlola inqubomgomo kuhlala ngaphakathi kwendlela yesicelo; lapho ukuhlola kufa,
Inqubo: hlola endleleni yesicelo, ukusatshalaliswa komhlaba wonke, umthengisi oyedwa
1:46 i-API iyafa. Okwesibili: idatha ye-quota ihamba emhlabeni jikelele ngaphandle kokuhlola; umugqa omubi ngumugqa womhlaba wonke. Okwesithathu: I-Cloudflare yayazi. I-Workers KV yayisephakathi kokufuduka kwayo ku-R2 yayo, yehliswe yaba umhlinzeki oyedwa — i i-postmortem iyibiza ngokuthi igebe ekubambeni.
git blame — ukuhlukana
2:00 git blame. I-Google, amaphesenti angamashumi amahlanu nanhlanu: akukho ukuhlola i-null, alikho ifulegi lesici, akukho ukubuyiselwa emuva — umbiko wabo uthi ifulegi lingayitholile esigabeni sokuhlola. Ukusatshalaliswa komhlaba wonke, amashumi amabili: umugqa owodwa, yonke indawo, imizuzwana. I-Cloudflare, amashumi amabili: ingxenye yomugqa womkhiqizo esitolo somthengisi oyedwa, ne-postmortem engakaze isho i-Google. Ikhasi lesimo, amahlanu, lokuphila kulokho elibika ngakho. Ubukhulu bokungqubuzana: imikhiqizo engamashumi ayisikhombisa ye-Google Cloud, izinhlelo zokusebenza eziyishumi ze-Workspace,
Ubukhulu bokungqubuzana
2:23 yonke indawo. Amahora amathathu. Ku-Cloudflare: I-Access, i-WARP, i-Workers AI, i-Pages, i-Stream — amabili nengxenye. I-Hacker News, amaphuzu ayinkulungwane namakhulu amane; amazwana aphezulu: ikhasi lesimo liluhlaza.
Isinqumo + umugqa woMsombuluko
2:33 Isinqumo, i-postmortem: SHIP IT. Zombili izi-postmortem zifika phakathi kwamahora angamashumi amathathu, zombili zizisole zona, nezilungiso ze-Google zicacile: yehluleke ukuvula, amafulegi avalwe ngokuzenzakalelayo, ukubuyiselwa emuva okwandayo. Umugqa woMsombuluko: ikhodi entsha ngemuva kwefulegi eliphuma ngaphandle, nokuhlola i-null lapho idatha ingena khona. Ngithumele isigameko ongakavunyelwa ukukhuluma ngaso, kumazwana, noma ku-thedailydiff.dev. Futhi lokho ukwehluka kwanamuhla.
2:53 NginguNiko wase-Axrisi. Hlanganisa ngokuzibophezela.
Imithombo
- Google Cloud Service Health, Incident Report (Jun 13, 2025) + Mini Incident Report (Jun 12)status.cloud.google.com
- Cloudflare, "Cloudflare service outage June 12, 2025" (Jun 12, 2025, 22:00 UTC)blog.cloudflare.com
- Cloudflare Status, "Broad Cloudflare service outages" (18:19–21:31 UTC)www.cloudflarestatus.com
- Gergely Orosz, 19:11 UTC, "Their infra is fully independent AFAIK"x.com
- @Google support, 19:32 UTC, "there aren't any known service disruptions"x.com
- Thomas Kurian (Google Cloud CEO), Jun 13 01:35 UTCx.com
- Hacker News, "GCP Outage" (1,468 points)news.ycombinator.com
- Hacker News, "Cloudflare was down" (341 points)news.ycombinator.com
- Hacker News, "Google Cloud Incident Report – 2025-06-13" (209 points)news.ycombinator.com



