
Graphics engineer at Tokyo, in Japan. All opinion are my own. グラフィックスプログラムに興味無さそうな方はご遠慮して頂いてます。@pocol.bsky.social
Local Space Coordinate
Joined November 2010
- Tweets19.3K
- Following557
- Followers647
- Likes11.9K
Pinned Tweet
「Direct3D 12ゲームグラフィックス実践ガイド」発売中です!よろしくお願いします!
gihyo.jp/book/2021/978-4-297…
Pocol retweeted
全国のお客様およびパートナーの皆様へ
先週発生した Microsoft 365 の障害により、お客様およびパートナーの皆様の日々の業務や事業運営に、多大なご迷惑とご心配をおかけしましたことを、改めまして心よりお詫び申し上げます。
本件は技術的な問題によるもので、サイバー攻撃または AI や AI エージェントに起因するものではありません。多くの Microsoft 365 サービスの前段に位置するネットワーク ゲートウェイにおいて、次の 3 つの要因が重なり、グローバル規模の障害に至りました。
第一に、特定の負荷条件下で、サーバーが過負荷となり応答不能に陥る潜在的な不具合がありました。これは、Microsoft 365 のネットワーク ゲートウェイ サーバー専用に用意した修正プログラムに起因するものです。この修正プログラムは本年 7 月から全世界へ順次展開され、3 か月以上にわたり、本不具合は顕在化していませんでした。
第二に、障害発生の約 15 時間前、Teams は、利用するネットワーク ゲートウェイを Exchange Online も利用しているプライマリ ゲートウェイへ切り替えました。これにより同ゲートウェイの負荷が増加し、トラフィックのパターンも変化しました。なお、この切り替えは、通常の運用手順に従ったものでした。
第三に、その時点で、前日に発生した別の問題により、ネットワーク ゲートウェイのサーバーの約 14% が停止していました。全体の処理能力には十分な余裕があったため、この停止だけではお客様への影響は確認されていませんでした。しかし、前述の切り替えによる負荷の集中と重なったことで、その余裕が大きく減少しました。
このように、負荷の増加とサーバー容量の減少が重なった結果、潜在していた不具合が顕在化しました。リクエストが滞留して最終的にサーバーが応答不能に陥り、障害は世界各地のネットワーク ゲートウェイ基盤へと連鎖的に拡大しました。また、通常より復旧に時間を要したのは、サービスを復旧したサーバーに、待機していたトラフィックが一斉に流れ込み、再び過負荷となったためです。当社は本不具合が原因であることを特定後、該当する処理を従来の正常な状態に戻すためのアップデートを開発し、サービスを段階的に復旧いたしました。
障害の発生以降、処理能力を増強するとともに、トラフィックのリダイレクトと接続処理に関する監視を強化しました。あわせて、影響の連鎖的な拡大を防ぐため、負荷を分散する制御策を導入しております。また、障害中に滞留したメールが配信不能として送信者に返送されないよう、メールの配信期限を延長いたしました。事後検証報告書(PIR)は、Microsoft 365 管理センターで公開しております。
お客様が当社サービスに寄せてくださる信頼に応える責任を、私たちは極めて重く受け止めています。今回の教訓を確実に生かし、再発防止に全力を尽くしてまいります。
More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below.
We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations.
The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services.
First, a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments.
The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact.
Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores.
Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts.
Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own.
Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States.
When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive.
Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally.
Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway.
Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change.
After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region).
The final Post-Incident Review (PIR) will provide more details later this week.
devblogs.microsoft.com/cppbl…
MSVC最新アプデ、使う人マジで気をつけた方がいいよ。
リリースノートに一切書いてないけどフロントエンドの挙動相当変わってて、MSVCが今まで規格違反だったせいで通ってたコードが拒否されたり、暗黙のインスタンス化の挙動が変わってたりする。直すの簡単ではない。
Pocol retweeted
Over the past week, I’ve been overwhelmed by the love and support of friends, industry colleagues, and people I've never met. Thank you to everyone who has shown kindness to my family and me. It means the world to me.
I came to the United States 53 years ago, and becoming an American citizen is one of the greatest gifts and proudest moments of my life. NVIDIA has been my life’s work. Building it into the company it is today alongside my colleagues has been a privilege and an honor. Nowhere but in America could a company like NVIDIA be possible. I love our country, and I love NVIDIA.
I did not live up to the standards expected of everyone at NVIDIA, and I have made serious mistakes in my personal life. I created problems for the Board that I deeply regret. I own my mistakes completely, and I am committed to cooperating with the Board’s independent investigation.
Since my departure, I’ve seen an outpouring of calls from NVIDIA’s employees, investors, business partners, and customers for me to return as CEO. Many continue to reach out to me directly as the company navigates complex technology, market, competitive, and geopolitical dynamics. NVIDIA is a once-in-a-generation company. If the Board of Directors decides that my return is in the best interest of our shareholders, our employees, the company, and America, I would be honored to answer these calls and return as CEO.
Thank you again to everyone who has shared their good wishes. I am profoundly humbled by your support. To my family: I love you, and I will spend the rest of my life being worthy of yours.
Jensen
Pocol retweeted
Ray-traced parallax octahedral impostors
github.com/SamG-Coder/SmartI…
Made a forest renderer in rust + vulkan. close trees are the real megaplant meshes, anything past 50m turns into an impostor that gets ray marched inside an RTX intersection shader. 81k trees running around 7ms. got the idea from Toni Macaroni’s forest video
This is my best guess on how this works
(Most Likely wrong)
github.com/SamG-Coder/SmartI…
日本から、Graphics Programming Conference行っている人どのくらいいる?楽しそうだから一度ぐらい行ってみたい。
graphicsprogrammingconferenc…
Pocol retweeted
A developer explains how to convert EXACT UNORM8 to float for accurate color handling in game development
fgiesen.wordpress.com/2024/1…
#gamedevelopment #indiedev #gamedev
Pocol retweeted
【フアン氏がNVIDIA復帰協議 報道】
news.yahoo.co.jp/pickup/6602…
Pocol retweeted
【速報】🇺🇸 NVIDIAフアン元CEOの復帰署名、6万5000人突破と報道
・株主3万5000人以上が署名
・現役・元従業員4700人も参加
・イーロン・マスク氏も署名し、復帰を支持
Pocol retweeted
これちょっと調べないと出てこないんですよねー!
Xで何人かまとめてくださっていますがわたしからも。
【XBOX Nanoコントローラーのアップデート手順】
①公式サポート記事から PC用ドライバー(INFファイル3つ) をダウンロードして、全部インストール(inf各ファイルを右クリック→「インストール」)
②PCを再起動 ←これをやらないと次の更新が失敗します
③XBOXアクセサリーアプリを入れて、Nanoを USB-Cで有線接続 → 更新が終わったら、コントローラーを一度再起動すると適用されます
④iPhoneで使う場合は iOS 27.2以降 へのアップデートも必要です…
(残り194文字)
#mond_MISUZU_zip
Pocol retweeted
Released Jolt Physics v5.7.0. Main reason is that an MSVC update changed the behavior of /fp:fast and completely broke the simulation. So better update :)
github.com/jrouwe/JoltPhysic…
Pocol retweeted
Game developers demonstrate a ray‑splitting technique used in real‑time rendering.
jacktollenaar.top/articles/s…
#indiedev #gamedevelopment #rendering #gamedev
Pocol retweeted
「CAPCOM オープンカンファレンス RE:2026」の講演アーカイブ動画が一部公開
gamemakers.jp/article/2026_1…
『モンハンワイルズ』『バイオハザード レクイエム』などの開発ノウハウが語られた7講演。リアルタイムパストレーシング、風の流れを低負荷で表現できるVFXシステムについても解説
Pocol retweeted
Graphics Programming weekly - Issue 462 - November 8th, 2026 jendrikillner.com/post/graph…


















































