This post is also available in 简体中文, Français, Deutsch, Italiano, 日本語, 한국어, Português, Español (Latinoamérica), Español, Рyсский, Polski, Nederlands and 繁體中文. Note: This post was updated to clarify the relationship of the internal WAF tool with the incident on Dec. 5. On December 5, 2025, at 08:47 UTC (all times in this blog are UTC), a portion of Cloudflare’s network began experiencing significan
AWS DevOps Agent helps you accelerate incident response and improve system reliability (preview) | Amazon Web Services
AWS News Blog AWS DevOps Agent helps you accelerate incident response and improve system reliability (preview) Today, we’re announcing the public preview of AWS DevOps Agent, a frontier agent that helps you respond to incidents, identify root causes, and prevent future issues through systematic analysis of past incidents and operational patterns. Frontier agents represent a new class of AI agents
Amazon CloudWatch incident reports now support Five Whys analysis - AWS
Amazon CloudWatch incident reports now support Five Whys analysis Amazon CloudWatch launched incident report generation capabilities with an AI-powered root-cause workflow that guides customers through the "Five Why’s" analysis technique. The feature is modeled on the correction or errors process used by both teams within Amazon and our customers to improve their operations. The incident report ge
Published Sep 17, 2025 This is a technical report on three bugs that intermittently degraded responses from Claude. Below we explain what happened, why it took time to fix, and what we're changing. Between August and early September, three infrastructure bugs intermittently degraded Claude's response quality. We've now resolved these issues and want to explain what happened. In early August, a num
On June 12, 2025, Cloudflare suffered a significant service outage that affected a large set of our critical services, including Workers KV, WARP, Access, Gateway, Images, Stream, Workers AI, Turnstile and Challenges, AutoRAG, Zaraz, and parts of the Cloudflare Dashboard. This outage lasted 2 hours and 28 minutes, and globally impacted all Cloudflare customers using the affected services. The caus
https://github.com/openai/codex/blob/cfe50c7107b926c69f0774601909fa893bfe1055/codex-cli/src/utils/agent/agent-loop.ts#L1512-L1520 https://github.com/openai/codex/blob/cfe50c7107b926c69f0774601909fa893bfe1055/codex-cli/src/utils/agent/agent-loop.ts#L1525-L1528 https://github.com/openai/codex/blob/cfe50c7107b926c69f0774601909fa893bfe1055/codex-cli/src/utils/agent/agent-loop.ts#L1517-L1524
In the process of remediating CVE-2025-29927, we looked at other possible exploits of Middleware. We independently verified this low severity vulnerability in parallel with two reports from independent researchers. SummaryTo mitigate CVE-2025-29927, Next.js validated the x-middleware-subrequest-id which persisted across multiple incoming requests:
GitHub Actions Supply Chain Attack: A Targeted Attack on Coinbase Expanded to the Widespread tj-actions/changed-files Incident: Threat Assessment (Updated 4/2) Executive Summary Update April 2: Recent investigations have revealed preliminary steps in the tj-actions and reviewdog compromise that were not known until now. We have pieced together the stages that led to the original compromise, provid
Last week, we published CVE-2025-29927 and patched a critical severity vulnerability in Next.js. Here’s our post-incident analysis and next steps. Timeline2025-02-27On 27 Feb 2025 06:03:00 GMT, the vulnerability was disclosed to the Next.js team through GitHub private reporting. The researchers also emailed security@vercel.com. The initial report disclosed the vulnerability in older versions of Ne
Update 3: Wiz research has published that the initial leak was actually due to an upstream workflow, reviewdog/actions-setup@v1. This attack was done with a local script instead of calling out to gist, but similarly printed tokens in job logs. I’ve created a python script to check if your logs are effected. Update 1: The repo is back online with a statement on what happened. An access token for th
Intro 弊社で開発しているサービスの、ドメインを変更することになったときの話。 すでに旧ドメインで一部顧客に利用していただいていたため、旧ドメインは破棄せずに新ドメインにリダイレクトさせるようにしました。 DNSの設定やコードをいくらか修正し、リリースをしました。Webアプリを触って画像が表示されたりデータが取得更新できたりと、通常通り使えることを確認して一安心していました。 問題発生 すでに使っていただいていた社外ユーザーから「画像が表示されない」と連絡がありました。 スクリーンショットを見るとたしかに画像が切れてALTテキストが表示されていました。しかし同じ画面を自分のPCで閲覧すると正常に画像が表示されています。 先方のファイアウォールがホワイトリスト制にでもなっているのかと思い、ファイアウォールの設定をご確認くださいと返答しました。ですが「TCP/80(http)とTCP/44
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
