Ofcom has fined Meta £450,000 after finding that it gave the UK regulator inaccurate WhatsApp Business data in answers to five questions across two statutory information notices, according to the Confirmation Decision Ofcom published on 12 November. Ofcom says “the failures were repeated and extended across multiple requests and five separate questions”.
The fine is 22.5% of the £2,000,000 maximum the Communications Act 2003 allows for this breach, by our arithmetic, and includes a 25% settlement discount on a £600,000 figure. Set against the $200.97 billion of 2025 revenue that Ofcom cites from Meta’s 10-K, it equals about 1.6 minutes of Meta’s sales, by our arithmetic.
Business Pill · Data Flywheel
An evergreen Business Engineer explainer on how product data loops work. It teaches the general idea only and does not discuss Meta or Ofcom.
The key insight: As we read the decision, the record matters more than the £450,000: about 27 months passed between Ofcom’s first notice and its decision, by our arithmetic, while the same WhatsApp Business data was corrected across five questions, and Meta’s own explanation is that its data systems were “primarily designed for evolving operational and product purposes”.
Ofcom sent Meta Notice 1 on 31 July 2024 and Notice 2 on 19 June 2025 under section 135 of the Act. Both asked for WhatsApp Business conversation volumes and revenue, split between direct and indirect provision, for Ofcom’s review of the wholesale A2P SMS termination market, the decision says.
In July 2025 Meta told Ofcom that its Notice 1 answer had “incorrectly included both directly and indirectly provided conversations”, overstating direct volumes. On another question, Meta said: “We believe that we inadvertently provided figures for a 1-month period, rather than for the full 36-month period”.
The corrections were themselves wrong, the decision records. Meta said reusing its Notice 1 code on a changed data source “led to inconsistencies” that, in its words, significantly understated conversation volumes. A later fix overcounted: “Because a single business account can have multiple associated phone numbers there was duplication in the conversation accounts”. Meta sent its final corrected dataset on 4 September 2025.
Ofcom’s penalty on Meta for failing to give accurate information under section 135 of the Communications Act 2003: a statutory maximum of £2,000,000, a £600,000 figure before the 25% settlement discount, and the £450,000 fine imposed, per Ofcom’s Confirmation Decision. The 22.5% share is our arithmetic.
Why Ofcom Called It Serious
Meta’s Notice 1 data informed Ofcom’s consultation of 28 January 2025, which Ofcom later amended with Correction Notes on 28 March 2025 and 22 September 2025; the decision says the first addressed Ofcom’s own misdescription of the WhatsApp Business volumes Meta had provided. Ofcom says the errors “did not in the end affect the overall provisional findings of the market review”, but that “there was a risk that they could have done”.
Only the errors in Meta’s original Notice 1 response were identified by Meta; the remaining errors “had to be identified by Ofcom”, the decision says. Ofcom says it saw no evidence the breaches were deliberate but found they occurred carelessly, and it identified no evidence that Meta made any gain from them.
Using the dates in the decision, the three Notice 1 contraventions lasted 321 to 356 days and the two Notice 2 contraventions 49 days each, by our arithmetic. Ofcom puts them at 10 to 11 months and 7 weeks. From Notice 1 to the decision of 9 November 2026 took 831 days, about 27 months, by our arithmetic.
The Fine in Context
Section 139 of the Act caps the penalty for these contraventions at £2,000,000, the decision says. Ofcom says it had not previously found Meta in breach of section 135 or opened any prior investigation into the company. Meta must pay within two calendar months of any final enforcement notification.
Meta told Ofcom the amendments reflect “the inherent complexity of extracting accurate, internally consistent data from large-scale, multi-layered data systems primarily designed for evolving operational and product purposes”, and that it has added safeguards. Ofcom says Meta accepted liability and settled. We covered Brazil’s election court fine on Meta on 11 November.
The Structural Read
As we read the timeline, each correction created a new error: the July 2025 fix understated volumes because Meta’s data logging had changed, and the August 2025 fix overcounted because one business account can carry several phone numbers, according to the decision.
As we read Ofcom’s reasoning, the fine is about the reliability of the regulator’s own inputs: Ofcom says the errors did not in the end change its market review findings, yet it calls the contraventions serious because it must be able to rely on the information it receives and because the failures were repeated.
Ofcom, non-confidential Confirmation Decision to Meta Platforms, Inc., 9 November 2026
“Ofcom must be able to rely on the accuracy and completeness of information it receives”
Three Implications
FOR META The fine is 22.5% of the £2,000,000 statutory maximum and about 1.6 minutes of its 2025 revenue, by our arithmetic; Meta accepted liability and settled.
FOR COMPANIES ANSWERING OFCOM Ofcom says only the errors in Meta’s original Notice 1 response were identified by Meta; the remaining errors had to be identified by Ofcom.
FOR THE RECORD Ofcom says it had not previously found Meta in breach of section 135 or opened any prior investigation into the company.
The framework says: “Each moat is built by a different data pipeline”.
As we read it, Ofcom’s decision shows the reverse side of that idea: Meta told Ofcom its data systems were designed for evolving operational and product purposes, and they took several attempts to produce a consistent WhatsApp Business series for a regulator. The framework predates the decision and does not discuss Ofcom.
Days from Meta’s inaccurate response to its corrected data for each of the five contraventions in Ofcom’s decision: 356, 339 and 321 days for Notice 1 questions 12(a), 10(a) and 19(c), and 49 days each for Notice 2 questions 2(a) and 3(a). Day counts are our arithmetic from the dates in the decision; Ofcom puts them at 11, 11 and 10 months and 7 weeks.
What Is Not Established
The published decision is a non-confidential version: Ofcom redacted parts of Meta’s explanations and the governance changes Meta listed, and it does not give the WhatsApp Business volumes or revenue themselves. The decision does not break the £600,000 figure down by contravention.
The dollar comparison uses European Central Bank reference rates for 11 November 2026 and is approximate. We did not contact Meta for this piece; its quoted explanations come from the decision.
This Week In The AI Supercycle
The Great Convergence of Capital, Power, and Geopolitics
This week’s issue: for two years the AI build-out was priced as a supply story, and last week as a credit story. This week it was priced as a permission story, and the answer arrived as a cost, not a ban.
Ofcom fined Meta £450,000, 22.5% of the statutory maximum by our arithmetic, for WhatsApp Business data that was wrong across five questions and had to be corrected several times. Ofcom says the errors did not change its market review findings, and Meta accepted liability.
A note on sourcing. The fine, the legal basis, the dates, the contraventions and Meta’s quoted explanations come from Ofcom’s case page and its non-confidential Confirmation Decision to Meta Platforms, Inc., issued on 9 November and published on 12 November 2026, which we read in full; Meta’s 2025 revenue is the figure Ofcom cites from Meta’s 10-K. ISPreview’s report of 12 November gave the case page link.
The cap share, the day counts and the dollar comparison (ECB reference rates, 11 November 2026) are our arithmetic. We did not contact Meta for this piece.
Gennaro Cuofano is a CRO and tech executive who has worked in AI since late 2015, starting with bringing NLP, natural-language generation, voice and chatbot products to the marketing industry. His background is in law and finance: he holds a Master's degree in Law and an International MBA with an emphasis on corporate finance (LUISS Business School and the University of San Diego, 2012), and worked as a financial analyst at a real-estate investment firm in San Diego and as an assistant controller. His work focuses on business model strategy, business engineering and, more broadly, structural analysis: how companies make money, read from their own filings. He created FourWeekMBA and leads research there and at The Business Engineer, his newsletter on AI and business strategy, with over 95,000 subscribers and more than 1,000 published analyses. His writing has also appeared on Entrepreneur (for example, How to Digitize a Family Business in Europe) and HackerNoon. Find him on LinkedIn and Substack. See how we source.
