JupiteX Get the app
Markets & Finance16 Nov 2026 · about 7 min

The Next Wave: Microsoft’s outage showed Africa’s banks had no real plan B

The brief

The outage disrupted email and other work that depended on Microsoft systems, rather than stopping every bank service. That distinction matters: customers could still make payments and use mobile banking, while some routine tasks became harder or slower. The article does not report interruptions to either service at the Kenyan lenders it names. At Avenue Hospital in Nairobi, patients with insurance could not leave until the insurer approved their care. The approval process ran through systems that relied on Microsoft. Banks also said their email was down, and customers were directed to other ways to contact them. The article notes that email supports tasks such as loan applications, bank statements and complaints. Clinics stayed open and branches continued serving people, but patients waited and bank customers had to call or message instead of writing. Bank notices said payments and mobile banking remained available. The episode showed that a business can keep its main transaction channels running while other important services grind to a halt.

01

What parts of African banks’ services were disrupted when Microsoft went down, and what kept working?

The outage disrupted email and other work that depended on Microsoft systems, rather than stopping every bank service. That distinction matters: customers could still make payments and use mobile banking, while some routine tasks became harder or slower. The article does not report interruptions to either service at the Kenyan lenders it names.

At Avenue Hospital in Nairobi, patients with insurance could not leave until the insurer approved their care. The approval process ran through systems that relied on Microsoft. Banks also said their email was down, and customers were directed to other ways to contact them. The article notes that email supports tasks such as loan applications, bank statements and complaints.

Clinics stayed open and branches continued serving people, but patients waited and bank customers had to call or message instead of writing. Bank notices said payments and mobile banking remained available. The episode showed that a business can keep its main transaction channels running while other important services grind to a halt.

02

How widespread was the outage, and which African countries’ banks reported problems?

Microsoft’s outage crossed national borders and disrupted users in 74 countries. Downdetector counted it as the largest outage across all the services it monitored in 2026. Its scale matters because the same technology provider supported businesses in multiple countries, so one failure could affect many organisations at once.

In Kenya, at least six lenders sent notices about service problems, including Equity, Standard Chartered, Stanbic, UBA, I&M and Loop; NCBA’s digital bank also notified customers. In Nigeria, Wema Bank and Stanbic IBTC reported email problems. In South Africa, Absa was among the organisations affected, alongside Eskom, FlySafair and the SABC. The South African Revenue Service also warned taxpayers.

Reports climbed from 8 AM to 11 AM local time on Friday, when offices across the continent were opening. Microsoft said settings applied to servers after an update overwhelmed a process for setting up secure connections. The article’s examples show reported problems in three African countries, not that every bank there was affected.

03

What is a business continuity plan, and what did banks’ fallback plans actually offer customers?

A business continuity plan sets out how an organisation will keep important services available, or restore them, when normal operations are disrupted. It matters because a written promise of resilience is only useful if staff and customers can rely on the response during an actual outage.

The banks’ notices offered practical ways to reach them while email was down: call, message on WhatsApp or contact a relationship manager. Wema also pointed customers to Instagram for urgent requests. Those channels gave customers somewhere to turn, but the article questions whether a phone number alone amounts to a robust fallback. Some lenders took more than 15 hours after Microsoft acknowledged the fault to tell customers where to go instead.

The notices said payments and mobile banking were unaffected at the Kenyan lenders. The article argues that plans should be judged by how quickly they work in practice, not just by whether a continuity plan exists. It does not describe every bank’s internal recovery arrangements, but it says the public fallback customers saw was largely alternative contact channels.

04

Why could banks’ email problems still cause trouble even when payments and mobile banking worked?

Payments and mobile banking are only part of a bank’s work. Email carries many routine tasks, so its failure can disrupt customers even if they can still transact. This matters because a service can appear to be operating normally while customers are unable to complete related requests or get help.

The article lists loan applications, bank statements and customer complaints as work that often runs through email. It gives a separate example from Avenue Hospital: the insurer’s approval for patients depended on systems running on Microsoft. A customer who needs a bank statement before a Friday visa appointment could face a problem even if their account and payment services remain available.

Kenyan lenders said payments and mobile banking were not interrupted, and branches kept serving people. But customers had to call or message instead of emailing, while some patients waited longer. The contrast shows why continuity planning needs to consider everyday support and administrative work, not just the channels used to move money.

05

Why was sending customers to WhatsApp not a fully independent backup for Microsoft services?

A backup is most independent when it does not rely on the same source of risk as the main service. The article’s concern is that banks responded to a Microsoft outage by steering customers to another large US technology company. Using two providers spreads dependency, but it does not make either one immune to failure.

Banks suggested WhatsApp, and some also suggested Instagram; both belong to Meta. Wema also offered phone lines. The article says WhatsApp lines and chatbots were official, logged and worked on Friday. But it asks what would have happened if WhatsApp had also gone down that morning. A second platform can help during one outage without being a guaranteed fallback for every outage.

The article does not claim Microsoft and Meta share systems or that their services failed together. Its point is that both companies have outage histories, so relying on one when the other fails is not the same as building a fully independent backup. The banks’ notices show customers were redirected, not that platform risk disappeared.

06

Would putting Microsoft servers in Kenya have prevented this outage, and why or why not?

The article does not discuss Microsoft servers located in Kenya, so it cannot establish whether local hosting would have prevented this particular outage. As general technology context, a server’s physical location does not by itself guarantee resilience. What matters is also whether the backup uses separate systems and can keep working if the same service or configuration fails.

Microsoft attributed the incident to settings applied to servers after an update. A process for setting up secure connections became overwhelmed, and servers stopped handling requests. If Kenyan servers had depended on the same affected Microsoft service or settings, moving their location alone might not have removed that dependency. The article does not say where the affected servers were or how widely those settings were applied.

A separately designed, tested fallback could reduce reliance on one failure path, but the source provides no details about such a setup in Kenya. Its broader point is that banks need a real alternative, not just a plan on paper. Claims about a specific local data centre preventing this event would go beyond the information given.

07

What is vendor concentration risk, and how can relying on one technology company make many businesses vulnerable at once?

Vendor concentration risk arises when an organisation depends heavily on one outside company for important technology. If many organisations make the same choice, one provider’s failure can affect them at the same time. That matters because an outage can spread beyond the provider’s own customers to the businesses and services that rely on it.

The article describes banks and other organisations across African countries experiencing problems during Microsoft’s outage. The failure began after server settings were applied following an update; a process for setting up secure connections became overwhelmed, and servers stopped handling requests. Banks then sent customers to alternatives such as WhatsApp, which the article says moved reliance to another major platform rather than eliminating it.

Payments and mobile banking kept working at the Kenyan lenders, but email-dependent work slowed. The article says a second, tested email system costs money and may be used rarely, which helps explain why businesses accept dependence on one vendor. It warns that future outages could be more serious if AI agents take on work that staff currently perform, leaving less human capacity to step in.

This brief was written by AI from the original reporting and checked by other models. Names, figures and quotes come from the source; read it for full context.

Read more in the JupiteX app

Pulse is free. New stories every 4 hours, each one broken into the questions that explain it.

Or read more news on the web