ziper (@ziperke) header
ziper (@ziperke) profile picture

Backend Engineer

localhost
Joined January 2021
Photo by ziper (@ziperke)Photo by ziper (@ziperke)Photo by ziper (@ziperke)Photo by ziper (@ziperke)Photo by ziper (@ziperke)Photo by ziper (@ziperke)Photo by ziper (@ziperke)Photo by ziper (@ziperke)Photo by ziper (@ziperke)Photo by ziper (@ziperke)
Replying to @citizentvkenya
Hitler did to the Whites, what was reserved for the Blacks.
25
26
2
350
43,051
ziper retweeted
Replying to @OleItumbi
Tim Wanyonyi is very educated Lawyer & David Ole Sankok is educated in Medicine they've both risen to the top despite living with Disabilities y haven't they been appointed to head Judicial Service Commission, CEO Kenya Power or CS Health or CEO KEMSA respectively??
4
3
51
5,154
Replying to @OleItumbi
Pulling a disability card now 😤😤😤
4
7
1
292
9,336
Replying to @OleItumbi
There is no doubt Cheptumo is qualified. The issue is not qualification, but equitable representation. A government that consistently draws its leadership of government institutions from one ethnic group CANNOT hide behind the language of Merit, or Usawa Ni Sawa. That is not meritocracy but Kanjinisation of the state dressed up as competence.
17
26
1
452
14,609
🚨 AFRIQUE DU SUD 🇿🇦 : Deux femmes arrêtées pour avoir violé un homme de 32 ans. La police sud-africaine a arrêté deux femmes âgées de 26 ans, soupçonnées d'avoir violé un homme de 32 ans dans le secteur de Tembisa. Selon les rapports de la police, l'homme aurait rencontré ces deux femmes dans un bar du quartier. Après avoir consommé de l'alcool ensemble, elles l'auraient invité dans une chambre qu'elles avaient réservée dans le secteur de Winnie Mandela, zone 4. Une fois à l'intérieur, les deux femmes l'auraient déshabillé de force et soumis à des actes de violence se*uelle. Cependant, l'homme a réussi à s'échapper. Le propriétaire de la maison l'aurait ensuite accompagné au commissariat pour signaler les faits à la police. La police a salué le courage de cet homme pour avoir dénoncé les faits. Elle a également souligné que de nombreux hommes victimes de violences se*uelles hésitent à porter plainte, notamment à cause de la honte, du jugement des autres et de la peur de ne pas être crus par la société.
369
429
117
3,854
632,676
We want to be clear that we aren’t currently seeing evidence of a broad Gmail service disruption, and you can always check real-time status on our Status Dashboard: google.com/appsstatus/dashbo…
58
227
36
2,297
195,330
全国のお客様およびパートナーの皆様へ 先週発生した 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.
28
1,251
75
2,138
279,943
“She had to wait for a hydraulic crane from Industrial Area to evacuate her to the nearby AAR Hospital.” Some of you are so damn disgusting!
Terence Creative’s wife Milly Chebby falls while running at Karura Forest… She had to wait for a hydraulic crane from Industrial Area to evacuate her to the nearby AAR Hospital.
29
34
2
472
30,944
Wanaita mtoto wa OF model na scammer, King Von 😭😭😭.
25
173
16
1,178
23,563
ziper retweeted
Mambo gani tena..Drama asTraffic Police Fight with GSU Civilian Officer in kimbo Ruiru🫴
24
144
2
1,558
215,273
Good morning ladies and gentlemen, plz find a moment to congratulate this trio for their appointments during this season of usawa ni sawa.
345
1,010
53
3,121
187,137
ziper retweeted
"Y'all wouldn't even let me turn heel" 😂 @JohnCena
279
1,456
289
19,246
2,164,431
Ukienda interview kengen
94
1,075
53
4,942
136,431
ziper retweeted
I'm hiring 2 Junior Software Engineers to work directly with me. 1. WordPress & Frontend: WordPress, React, websites & AI coding tools. 2. Full-Stack & QA: Web development, software testing, debugging & AI coding tools. Send your CV + a brief intro to [email protected]
32
60
2
568
28,958
So basically it will be cheaper for my clients to pay with pesalink to my clinic account instead of sending to green then sending to paybill . Very nice let’s support our clients guys 😅
23
182
4
1,472
33,976
When you’re OF model they judge you When you become wifey they still judge you Ladies do what you want
7
12
4
50
10,954
BREAKING; #NgigeKnows “We Are Shocked To See Boys With Such Small Manhoods. Something Must Be Done Urgently To Address This. Otherwise.....” - Kiama kia Maa. #culture #tradition
55
130
54
589
130,462
104
38
18
434
25,517
Terence Creative’s wife Milly Chebby falls while running at Karura Forest… She had to wait for a hydraulic crane from Industrial Area to evacuate her to the nearby AAR Hospital.
66
53
15
546
154,912
ziper retweeted
UPDATE — 🇺🇸 Emergency message sent to US television stations:
NEW — 🇺🇸 An emergency warning system drill will be conducted in the US. All television and radio broadcasts will be automatically interrupted.
16
144
14
1,035
576,767
Reheat that OF link queen
Hi guys My boyfriend has been arrested for a crime he didn’t commit He just wanted to make a good life for me n our son If you anyone in my followers can help me I’ll really appreciate #operationgetman
34
233
5
1,019
33,302