←
Ravi1,130 posts
Ravi avatar

Ravi

@jidge_

A software engineer. Here to support right cause. Tweets are funded by Soros.

◷ Joined April 2014▧ 46 Photos and videos
Charles Lamanna avatar
⟳ Ravi retweeted
Charles Lamanna@clamanna·Nov 16

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.

We have released the Preliminary Post-Incident Report of last week’s outage, which is accessible via the Admin center under MO1550821 and EX1550543.

Microsoft 365 Status avatar
⟳ Ravi retweeted
Microsoft 365 Status@MSFT365Status·Nov 12

We're investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas. More details can be found in the Microsoft 365 admin center under EX1550543.

RushLane avatar
⟳ Ravi retweeted
RushLane@rushlane·Nov 9

Just to explain how these campaigns generally work. This isn't simply a case of someone posting an opinion about ethanol blending because they happen to have one. There is an entire campaign structure behind it. And we need to understand this. To make it simple, we know very little about ethanol blending, testing methods, frequency of daily testing, etc. First, creators are shortlisted across Mega, Macro, Micro and Nano categories. Their Instagram and X profiles, follower numbers, engagement, location, language and commercial rates are collected. The objective is pan-India coverage, so expect creators across multiple states and languages. Then comes the campaign brief. Creators receive specific talking points, key messages and communication objectives. In this case, the broad objective is to create awareness about ethanol blending and address what the campaign classifies as misinformation. Many times, the infographic itself will be provided to you, and you only have to post it at a pre-decided time. The more influencers, the merrier as it helps amplify the campaign. Next comes the content approval process. Creators prepare their posts, reels, scripts and captions, submit them for approval as per a directive, make any requested changes and wait for clearance before publishing. Or you could be provided the material to be posted. Independent thoughts are welcome, presumably after they have passed the approval process. Deliverables could include: • Instagram Reel: A 30–60 second video explaining E20 petrol, ethanol blending, its benefits and addressing commonly raised concerns. • Instagram Stories: Multiple slides carrying campaign messages, statistics, FAQs and calls to action. • X posts: A series of posts explaining ethanol blending, sharing selected data points, responding to criticism and reinforcing campaign talking points. • Regional-language content: The same broad messaging adapted in your language to achieve nationwide reach. There will also be a defined campaign period, posting windows, submission deadlines and publishing schedules. Creators may be expected to post on specified dates and times rather than whenever they feel like discussing fuel policy. The campaign will run for a month, with deliverables and timelines communicated after selection. Charges will depend on creator category and agreed deliverables. So, essentially, creators supply the audience, reach, regional credibility and distribution. The campaign supplies the subject, messaging, talking points, approval process and publishing schedule. It's quite a production for something that might otherwise look like a spontaneous wave of people independently deciding to discuss ethanol blending. The important distinction is that this is influencer marketing, not necessarily independent public education. And when the subject is a public policy with legitimate questions around fuel economics, vehicle compatibility, mileage, emissions and agricultural priorities, that distinction matters. Thank you for your attention to this matter 😹😹😹

Post attachment
Cartoonist Rakesh Ranjan avatar
⟳ Ravi retweeted
Cartoonist Rakesh Ranjan@cartoonistrrs·Oct 27

मेरे इंस्टाग्राम अकाउंट को साहब ने भारत में रिस्ट्रिक्ट कर दिया है, उनका डर चीख चीख के बोल रहा है। मेरे दूसरा अकाउंट Cartoonistrrs2.0 को फॉलो कर लीजिए। तुम कितने अकाउंट बंद करोगे मैं हर मिनट अकाउंट बनाऊँगा ।

Post attachment
Neha avatar
⟳ Ravi retweeted
Neha@neha_aisa·Oct 12

Where is @harshdelhise??? @DelhiPolice has made a journalist disappear, and his whereabouts have been unknown for over 48 hours! AMPLIFY THIS EVERYWHERE until his whereabouts are known!

Ratna Singh avatar
⟳ Ravi retweeted
Ratna Singh@whattalawyer·Oct 10

Judge serving the master. Went for break/meeting 4 times during entire hearing. Order without any application of law. Welcome to new India, where Sarkar can put 30 police personnel confining you & then say we won coz armless people couldn’t come to the protest site. Irony is that people with criminal history are roaming around in Delhi & police personnel are busy detaining peaceful protesters.

#Breaking Delhi court rejects CJP legal head Ratna Singh's plea seeking release from allegedly illegal Delhi police detention. @whattalawyer @CJP_for_India

Post attachment
Congress avatar
⟳ Ravi retweeted
Congress@INCIndia·Oct 10

दिल्ली पुलिस के सामने BJP-RSS के गुंडे प्रोटेस्टर्स को मार रहे हैं। मोदी-शाह ने पूरे देश में गुंडाराज कायम कर दिया है। वीडियो में दिख रहा है कि गुंडे एक लड़की को जमीन पर गिराकर मार रहे हैं और पुलिस तमाशा देख रही है।

1:36
Cockroach Janta Party - CJP avatar
⟳ Ravi retweeted
Cockroach Janta Party - CJP@Cockroachisback·Oct 10

If you or someone you know has been unlawfully detained, please fill out this form ASAP! CJP is putting together the information needed to support affected volunteers and individuals. Please share this widely. Every case matters, and nobody should have to navigate this alone. We want to ensure those affected get the support and legal aid they require. forms.gle/dJoTy4Yiw4vBfLqB9

atul kasbekar avatar
⟳ Ravi retweeted
atul kasbekar@atulkasbekar·Oct 10

Just a reminder that most of the Indians shot at Jallianwala Bagh were shot by Indians in uniforms Gen. Dyer didn’t kill them all himself There are lessons in history that keep getting repeated

Saurav Das avatar
⟳ Ravi retweeted
Saurav Das@SauravDassss·Oct 10

Our legal affairs head @whattalawyer has been detained by the Police. She was on her way to join lawyers in their protest on the issue. In solidarity with everyone who is facing crackdown under Dictator Modi! ✊🏻🇮🇳🪳

Ravi avatar
Ravi@jidge_·Sep 28

Very well put

🚨#Important: Several petitions are now being filed in the High Courts and the Supreme Court “against” the actions of Chief Election Commissioner Gyanesh Kumar. But we must not forget what happened the last time citizens knocked on the doors of the judiciary. The Supreme Court ENSURED that the SIR happened in Bengal in whatever manner barely months before the election. When the consequences of mass voters deletions became impossible to ignore, Justice Joymalya Bagchi in that bench made an extraordinary observation that those unable to vote “this time” could vote “next time”. Who is to tell him that there is no “next time” for a possibly stolen election? So because the courts are constitutional institutions, let them hear these new petitions against Gyanesh as many times as they want. Let them pass whatever orders they want to. But our democratic demand for Gyanesh Kumar’s accountability will NOT BE outsourced to the courtrooms. The people will decide. Because ultimately, neither an Election Commissioner nor a judge owns Indian democracy. We, the People, do. @Cockroachisback @abhijeet_dipke @AshutoshRanka

Amock_ avatar
⟳ Ravi retweeted
Amock_@Amockx2022·Jul 28

During UPA govt, Sony TV did a comedy show where they mocked Dr Manmohan Singh and Sonia Gandhi They literally trolled Sonia Gandhi for her accent and weaker grip on hindi 💔 But Congress never played victim card, and didn't run after the actors or producers INC used to take jokes, abuses, trolling everything with smile on faces. Never claimed that trolling a politician or PM was like going against India That's the difference

0:32