Trust

Corrections

Fast, visible corrections are a product, not an embarrassment. A directory that never admits mistakes is telling you it never checks. Every figure on this site carries its source and the month it was last verified precisely so it can be challenged, and this page is where every material correction lands, dated, in public.

The verification standard behind these numbers is explained in the data methodology, and the editorial rules in the Editorial Policy.

How to report an error

One email is enough. It goes to the editor, not a form queue:

1. Send the challenge

Email elmaccommunicationslimited@gmail.com with three things: the entry or page, the exact figure you are challenging, and a primary source (a regulator filing, an operator page, an official document). Trade press counts as a lead, not as proof.

2. Acknowledged within 48 hours

Every challenge is acknowledged, not just answered. If we cannot reproduce your source or the claim needs deeper checking, we say so plainly instead of going quiet.

3. Verified and fixed within 5 working days

Where your source checks out, the correction is applied within five working days and the entry's verification date moves. Where it does not, the entry stands and we tell you why. Either way you get a substantive reply.

4. Logged in public

Material corrections and reclassifications are added to the log below and to the update log on the methodology page, including our own errors. Accuracy beats ego.

Corrections and updates, said precisely

We distinguish two things that round-ups usually blur together:

  • A correction means the world did not change, we did: a figure was wrong, a status was misread, a source was misquoted. These are fixed fast and logged below.
  • An update means the world moved: a facility launched, a cable went ready-for-service, a regulator issued a licence. Updates follow the update cadence and material ones are logged too, because a changed number should always be traceable to the event that changed it.

Corrections and update log

Every material change to the dataset, dated, newest first. When a figure you relied on changes, this log is the receipt for why.

26 September 2026

Three-model energy framing wired across the Energy cluster: the Olkaria corridor and Ethiopia exports articles now cross-link the Dangote Lamu analysis in both directions, and the /energy hub, chatbot fact base and green-power answer name the three competing models with figures kept separate.

  • Olkaria corridor article: added a 'Three Models Now Compete for the Same Load' section framing compute-to-the-wells against Ethiopian hydro imports (200 to 400 MW planned, subject to grid testing) and the announced Lamu LNG plant (about 1,000 MW, roughly 500 MW offered, no PPA public). The section states the figure discipline explicitly: operating capacity, planned trade volume and announcement are different stages of certainty and are not summed. Internal links and the sources footer updated.
  • Ethiopia exports article: added a 'Where This Sits Among Kenya's Power Options' section placing imports alongside the Olkaria corridor and the announced Lamu plant, restating the status labels (planned trade volume vs announcement attached to an unbuilt refinery) and naming the update trigger (a Lamu PPA or financing close). Image caption figure refreshed 38.5 to 42.9 MW to match the site-stats canonical 'live designed capacity' label. Internal links updated.
  • Dangote Lamu article: the Olkaria geothermal corridor mention in the three-model paragraph is now an inline link; both sibling articles were already linked.
  • /energy hub and chatbot: the Energy cluster page description now names the three models; a Dangote Lamu fact chunk was added to the chatbot knowledge base carrying announcement-status language identical to the Microsoft-G42 chunk (treat 500 MW as an announcement, not bankable pipeline), and the green-power answer names the three models with a link to the Lamu analysis.

26 September 2026

Published the Dangote Lamu power-plant analysis (Energy cluster) with staged-announcement sourcing; registered two reference records in the policy dataset (bumped to r16).

  • New article /articles/dangote-lamu-refinery-power-plant-data-centres: covers the 26 September 2026 announcement of a 1,000 MW power plant at the proposed Lamu refinery with ~500 MW offered to the Kenyan government. The article stages every figure as an announcement, flags the refinery-capacity discrepancy across outlets (roughly 220,000 to 700,000 barrels per day as reported), establishes from The Africa Report that the plant is LNG-fired rather than renewable, sets the scale against the directory's live figures (42.9 MW built capacity, 10.5 MW published IT load, 230 MW pipeline, ~3,000 MW installed grid capacity), and records the Lamu coal-plant precedent (1,050 MW Amu Power licence revoked 2019) as part of the project's risk profile.
  • Policy intelligence source registry: added the Kenyans.co.ke report (full text captured) and The Africa Report LNG reporting (snippet capture, paywalled) as tier-2 reference records with explicit no-claim-yet notes; candidate background evidence for the energy-electricity pillar. Dataset bumped from r15 to r16.
  • Imagery: the article uses photographs of the Ruto-Dangote walkthrough at the Lekki refinery (supplied by the editor and uploaded to the repository) for the hero and announcement sections, an explicitly labelled artistic impression of the proposed Lamu layout flagged as promotional material, and existing verified infrastructure photography for the grid and geothermal sections. No AI-generated imagery was retained for this article.

26 September 2026

Fifth audit pass: MTN/Africa Data Hub announcement added to the policy intelligence source registry (dataset bumped to r15) and the article's IT News Africa citation canonicalised; crawler-report triage confirmed closed.

  • Policy intelligence source registry: added the IT News Africa report of the MTN Digital Infrastructure / Africa Data Hub Holding Limited partnership (31 Aug 2026, full text captured 26 Sep) as a tier-2 reference record. It is a commercial market development, not a policy claim, so it is registered with an explicit note that it supports no claim yet and is candidate background evidence for the ai-digital-policy and regional-frameworks pillars. Dataset bumped from r14 to r15.
  • MTN analysis article (mtn-africa-data-hub-ai-data-centres): the IT News Africa citation used the publisher's older /2026/08/ path, which only resolves via redirect; updated to the canonical /enterprise/digital-transformation/ path and verified live (HTTP 200).
  • Re-verified the article against the captured source text: every material fact (Africa Data Hub Holding Limited vehicle, Bayobab's shareholder role, the Mroué and Al Ashram quotes, the South Africa and Nigeria initial focus, Ambition 2030 framing) was already present and accurate; no content change was needed.
  • Re-checked the external crawler report's remaining items against the live site and the four earlier audit passes: the two genuine number-consistency findings were already fixed in passes 2-4, and the rest were crawler artefacts (guessed routes, XML rendering failures) confirmed with live HTTP checks recorded on 25 September.

26 September 2026

Fourth audit pass: FAQ page answers re-scoped to Kenya where the question is Kenya-scoped, plus copy fixes.

  • FAQ “How much new data centre capacity is coming to Kenya?”: the 232 MW figure summed announced pipeline across all tracked records including the East African reference builds; the question asks about Kenya, so the answer is now the Kenya-scoped 230 MW.
  • FAQ “Which Kenyan data centres are AI-ready?”: read “5 of the 31 tracked facilities”, using the full register as denominator for a Kenya-scoped question; now “5 of the 27 Kenyan facilities in the directory”.
  • Directory page: fixed a stray space before the comma in “free to download and cite”.
  • DigitalOcean analysis article: cross-reference to the market-numbers explainer updated from “26 facilities” to “27 verified facilities” following the 19 September directory update, and the article's updated_date moved accordingly.

25 September 2026

Third audit pass: the chatbot's curated answers were still quoting superseded numbers, and the directory meta description still showed a city split that did not sum.

  • Chatbot FAQ “How many data centres does Kenya have?”: said “16 tracked data centre facilities, of which 12 are operational”, a superseded snapshot from an earlier register. It now derives the answer from the live directory like the FAQ page does: 27 verified Kenyan facilities, 20 operational, plus 4 East African reference records (31 tracked).
  • Chatbot FAQ “Which Kenyan data centres are AI-ready?”: said “12 of the 16 tracked facilities”. The AI-ready flag is held by 5 of the 27 tracked Kenyan facilities; the answer is now dataset-derived.
  • Chatbot FAQ “Who operates Kenya's data centres?”: said “12 tracked operators”. The directory tracks 18; the answer is now dataset-derived.
  • Chatbot FAQ “How much new data centre capacity is coming to Kenya?”: said “roughly 171 MW” and named the Microsoft–G42 campus as part of it. The announced pipeline is 230 MW (77 MW of it under construction across iXAfrica NBOX1.2, Africa Data Centres Nairobi 2 and Nxtra by Airtel Tatu City), and G42's own directory record warns the project has stalled on grid power constraints, so the answer now separates the two and derives the total from the dataset constant.
  • Chatbot Microsoft–G42 fact chunk: described the project as “pending grid capacity” and “the single largest project in Kenya's data centre pipeline”. It now carries the same caveat as the directory record: no site confirmed, stalled on grid power, treat the 100 MW as an announcement, not bankable pipeline.
  • Chatbot FAQ “How many submarine cables”: kept 7 in service (re-verified against the dataset) but now states 10 systems tracked and names Daraja and LuLu as in development; “awaits full service” tightened to “awaits ready-for-service”.
  • Chatbot FAQ “Do you need a licence...”: refreshed with the September 2026 CA standalone-licence consultation (tiered annual fees to KSh 100,000 or 0.4 percent of turnover, whichever is higher, submissions due on or about 8 October 2026 to datacentres@ca.go.ke) and now links Policy Intelligence alongside the explainer.
  • Directory meta description: the 25 Sep pass log said the city split was fixed “in both the meta description and the body copy”, but only the body was reordered; the meta description still read 27 facilities with a 19 + 4 city split that does not sum. It now reads the full split (19 Nairobi, 4 Mombasa, and the remaining 4 named by city), computed from the dataset alongside the body copy so the two can never drift or fail to sum again.
  • Also re-verified live: every internal link on /infrastructure/map resolves HTTP 200 (the crawler's ten guessed routes never existed), robots.txt “Disallow: /api/” affects only search indexing while the /directory CSV link keeps working for users, and /api/directory/csv serves HTTP 200.

25 September 2026

Second audit pass: Kenya scoping on the annual review and research hub cards; the Brief/01 PDF re-minted to the current dataset; directory sentence order clarified.

  • Annual review (research/state-of-kenyan-data-centres-2026): the headline KPI counted all 31 directory records (22 operational) under a review titled “State of Kenyan Data Centres”. It now reads 27 facilities tracked, 20 operational in Kenya. The carrier-neutral footnote and the pipeline-to-watch grid are Kenya-scoped too, so the 2 regional under-construction reference records no longer appear as Kenyan pipeline, and the intro states the 27 + 4 split explicitly.
  • Research hub: the Brief/01 card carried the 21 September snapshot figures (26 facilities, 186 MW pipeline); it now shows the current dataset (27 facilities, 230 MW pipeline). “122 top networks” and “8/20 carrier-neutral” were re-verified against the dataset and are unchanged.
  • Brief/01 PDF: the downloadable edition was minted 21 September from an earlier snapshot (26 facilities, 186 MW announced) with no marker separating it from the live page it is an edition of. It was first stamped with a visible data-snapshot note, then fully re-minted the same week from the current dataset: cover bullets, the Section 1 stat strip and Figure 1 now read 27 facilities, 42.9 MW built, 230 MW announced and 10.5 MW published IT load, with the under-construction stage restated as 77 MW across three projects (iXAfrica NBOX1.2, Africa Data Centres Nairobi 2, Nxtra by Airtel Tatu City). The temporary stamp is retired and the cover states the dataset verification month (2026-09) like the live page. Section 2 figures (122 networks, 8 of 20 carrier-neutral) were re-verified and are unchanged.
  • Directory intro: reordered the sentence so the city split (Nairobi, Mombasa, the rest) attaches to the 27 Kenyan facilities rather than reading as a split of the 20 operational — in both the meta description and the body copy. The numbers themselves were already correct.
  • Megawatt figures cross-checked and confirmed as three different labelled metrics, not contradictions: 10.5 MW published in-service IT load, 42.9 MW built (designed) capacity of live sites, 230 MW announced pipeline, 272.9 MW total tracked supply. Also re-verified live: sitemap.xml (HTTP 200, 179 URLs), /infrastructure/map (200), /api/directory (200), unique titles on methodology/corrections/editorial-policy.
  • Advisory, owner decision pending (not a factual error): the site runs on a vercel.app subdomain, the contact address is a gmail inbox, and the brand mixes “centers” (domain) with “centres” (editorial style).

24 September 2026

Scope reconciliation on the homepage directory band and FAQ; stale snapshot count removed from the annual review metadata.

  • Homepage “The DC Directory” band: the status line under “Every known data-centre facility in Kenya” was counting all 31 tracked records (22 operational · 5 under construction · 1 committed · 3 early stage), which includes 4 East African reference records. It is now scoped to Kenya as the heading promises: 20 operational · 3 under construction · 1 committed · 3 early stage (27 facilities).
  • FAQ “How many data centres does Kenya have?”: the answer said “31 facilities across Kenya, of which 22 operational” — both figures are region-wide (31 records and 22 operational include 2 operational records in Kampala). It now reads: 31 records = 27 Kenyan facilities + 4 East African reference facilities, 20 of them operational in Kenya.
  • Annual review metadata description dropped its hardcoded “26 tracked facilities” (a superseded snapshot count); the page body already states it draws live from the full register.
  • Audited and confirmed correct, no change needed: sitemap.xml (live HTTP 200, 179 URLs), /infrastructure/map (live HTTP 200), /api/directory (live HTTP 200), unique metadata titles on methodology/corrections/editorial-policy, and the directory page's internally consistent 27/20/19/4 arithmetic.

18 September 2026

Homepage stat strip made fully data-driven; research page listing.

  • Fixed the homepage stat strip: “Subsea cables live” now reads directly from the verified cable dataset (7 live of 9 systems) instead of a hardcoded number, the explainer count updates itself from the article index (97), and the verification stamp moved to September 2026.
  • Listed the Rack Report PDF editions (Issues 001 and 002) on the Research page alongside the report PDFs.

8 September 2026

Directory sweep: 10 facilities added, 2 removed, 2 reclassified, and unsourced capacity figures withdrawn.

  • Added the four iColo (Digital Realty) facilities (NBO1, NBO2, MBA1, MBA2) previously missing despite MBA1 being the most interconnected building on the Kenyan coast (94 networks on PeeringDB).
  • Added PAIX Nairobi (Britam Tower), Safaricom Thika, Safaricom Red Hill (Limuru), Telkom Milimani, Telkom Telephone House (Nairobi and Mombasa), Konza National Data Centre, SEACOM Mombasa cable landing station, and SimbaNET Nairobi.
  • Removed Wingu Nairobi after checking the operator's own website, which names only Djibouti, Ethiopia and Tanzania, Wingu does not operate in Kenya, despite appearing in many round-ups (including ours previously).
  • Removed Africa Data Centres Mombasa: no operator page, no register entry, and no independent evidence supports it.
  • Reclassified ADC Nairobi 2 as under construction, ADC's own site lists only NBO1 in Nairobi, and no source confirms the January 2023 expansion completed.
  • Withdrew the capacity figures previously shown for Raxio Nairobi and reclassified it as early stage, the facility does not appear on the PeeringDB register (checked 8 Sep 2026) and no operator page confirms an opened Nairobi site.
  • Updated iColo NBO2 for its formal launch on 7 September 2026 (Capital FM / Digital Realty), still ramping on interconnection.
  • Cross-checked every PeeringDB-registered Kenyan facility (14 records fetched 8 Sep 2026) and added per-entry network and exchange counts.

The promise, in one line: challenges acknowledged within 48 hours, verified fixes applied within 5 working days with the verification date moved, and every material change logged here. If we ever miss that standard, the failure is logged too.