---
title: "9Mobile power-related service outage in Nigeria"
description: "Disruption to voice, data, SMS, and short-code services for affected subscribers"
incident_type: "Operational outage"
status: "active"
last_modified: "2026-11-17"
canonical_url: "https://www.ally.security/incidents/9mobile-nigeria-power-outage-2026"
markdown_url: "https://www.ally.security/incidents/9mobile-nigeria-power-outage-2026.md"
stix_url: "https://www.ally.security/incidents/9mobile-nigeria-power-outage-2026/stix.json"
---

# 9Mobile power-related service outage in Nigeria

Disruption to voice, data, SMS, and short-code services for affected subscribers.

Last modified Nov 17, 2026 · 1 source

## Summary

- **Environment:** 9Mobile cellular network, including subscriber systems for Kano and Port Harcourt
- **Operational impact:** Disruption to voice, data, SMS, and short-code services for affected subscribers
- **Financial impact:** Financial impact remains unquantified in public reports

## What happened

On November 13, 2026, the [Nigerian Communications Commission](https://www.ncc.gov.ng/) recorded a major service outage at [T2mobile](https://t2mobile.com.ng/), listed as 9Mobile in the regulator’s report. The [incident notice](https://ncc.gov.ng/node/7662) linked the outage to a power failure, identified subscribers served by network systems in Kano and Port Harcourt, and listed disruptions across multiple locations in Nigeria. [1](#source-1)

## Impact

- The regulator listed voice calls, mobile data, SMS, and short-code services as affected. The incident title identifies customers served by the Kano and Port Harcourt subscriber systems. [1](#source-1)

## Timeline

### November 13, 2026 — Regulator records a major 9Mobile outage

The commission recorded the disruption as INC-20261113-00000003. [1](#source-1)

### November 17, 2026 — Briefing updated

This briefing was last reviewed and updated on November 17, 2026.

## Threat Group & Attack Vector

The commission categorized the cause as a power outage. The notice gives no further detail on the equipment or power supply involved. [1](#source-1)

## Response

The regulator lists the incident as resolved. The restoration method and exact time remained unspecified in the incident notice. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/9mobile-nigeria-power-outage-2026/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### NCC notice on the 9Mobile power-related outage

regulatory · Nigerian Communications Commission · Nov 13, 2026

<https://ncc.gov.ng/node/7662>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Affected Organization · 100% confidence · current**  
   9Mobile power-related service outage in Nigeria: T2mobile
2. **Resulted In · 100% confidence · current**  
   9Mobile power-related service outage in Nigeria: The commission categorized the cause as a power outage. The notice gives no further detail on the equipment or power supply involved.
3. **Resulted In · 100% confidence · current**  
   9Mobile power-related service outage in Nigeria: On November 13, 2026, the Nigerian Communications Commission recorded a major service outage at T2mobile, listed as 9Mobile in the regulator’s report. The incident notice linked the outage to a power failure, identified subscribers served by network systems in Kano and Port Harcourt, and listed disruptions across multiple locations in Nigeria.
4. **Occurred At · 100% confidence · current**  
   Regulator records a major 9Mobile outage: 2026-11-13
5. **Resulted In · 100% confidence · current**  
   9Mobile power-related service outage in Nigeria: The regulator listed voice calls, mobile data, SMS, and short-code services as affected. The incident title identifies customers served by the Kano and Port Harcourt subscriber systems.
6. **Resulted In · 100% confidence · current**  
   9Mobile power-related service outage in Nigeria: The regulator lists the incident as resolved. The restoration method and exact time remained unspecified in the incident notice.

</details>
