Summary
- 47 CFR 43.82(a)(1) imposes a genuine annual capacity return on "each cable landing licensee and common carrier", measured on cables landing in the United States as of 31 December and due not later than 31 March: one sentence fixes the filer population, the snapshot and the object.
- The publication unit and the withheld unit are different objects. The February 2026 Filing Manual says the Commission "annually compiles the data filed pursuant to section 43.82 and publicly releases the compiled data"; the Office of International Affairs page says "Individual cable data are withheld from public distribution for those filing entities that requested confidential treatment."
- The request is a checkbox on a Registration Form filed with the report, and 47 CFR 0.459 defers the duty to justify it until a stranger asks to inspect the file — so the argument for hiding a row is written, if ever, after a challenge rather than before publication.
The return is not optional and never was. In the current codified text of 47 CFR 43.82, paragraph (a) is headed "Submarine cable capacity" and opens "Not later than March 31 of each year"; paragraph (a)(1) then does all of the work in a single sentence: "Each cable landing licensee and common carrier shall file a report showing its capacity on submarine cables landing in the United States as of December 31 of the preceding calendar year" (47 CFR 43.82, current text). Two classes, one deadline, one snapshot, one object measured. Not capacity anywhere on earth, not capacity sold onward — capacity on cables that land in the United States.
The instructions cite a different paragraph
The Commission's own filing instructions open by attributing that duty to another paragraph: "Section 43.82(a)(2) of the Commission's rules sets forth annual circuit capacity reporting requirements that apply to (1) any licensee of a submarine cable between the United States and a foreign point (cable landing licensee), and (2) any common carrier with capacity on a submarine cable between the United States and a foreign point (common carrier)" (Filing Manual, February 2026). The current codification puts the capacity-holder report in (a)(1) and spends (a)(2) defining "United States" by reference to section 3 of the Communications Act. Two documents, two paragraph numbers, read on 18 November 2026. I do not call either an error: no drafting history was read, and the manual's own Appendix A reproduces an older codification of the same paragraph in which (a)(1) is marked "[Reserved]" and the capacity runs "between the United States and any foreign point". That is what a document looks like when it is maintained beside a rule that moved underneath it.
The programme page then adds an entrance condition the rule text does not state. On the Office of International Affairs page, the duty attaches to a licensee or common carrier "if it had any activated or non-activated circuits as of December 31 of the preceding calendar year" (Circuit Capacity Data page). The quoted rule contains no such threshold. It matters that the added condition is one a filer applies to itself: nothing in the material I read has the Commission measuring whether a filer had a circuit before deciding whether the filer owed a return.
The unit lives in the manual
The measuring instructions sit outside the rule. The February 2026 Filing Manual sets the snapshot at 31 December of the reporting period, the unit in Gbps to one decimal place, three years of record retention, and electronic filing on Commission-designated spreadsheets. I report those four as the manual's content rather than quoting them, because the retrieval returned the manual's sentences on filers and confidentiality verbatim while returning the unit and retention instructions as a summary of the same document.
They belong to the manual by the rule's own design: paragraph (c) delegates the preparation of "instructions and reporting requirements" published as a Filing Manual, and requires the information to be filed electronically in conformance with it.
The box
Then comes the box, and the box is the article. Paragraph (b) requires a Registration Form with each report, and that form "shall include a certification enabling the filer to check a box to indicate that the filer requests that its circuit capacity data be treated as confidential consistent with § 0.459(a)(4) of this chapter" (47 CFR 43.82). Read the grammar slowly. A certification enabling the filer to check a box to indicate that the filer requests. The request is the filer's, it travels with the report, and it points at one subparagraph of the Commission's general confidentiality rule.
That subparagraph authorises precisely this shortcut, and the same section states the price: "upon receipt of a request for inspection of such records pursuant to § 0.461, the submitter will be notified of such request pursuant to § 0.461(d)(3) and will be requested to justify the confidential treatment of the record, as set forth in paragraph (b) of this section" (47 CFR 0.459). So the request is not adjudicated at filing. The merits are argued when somebody asks to see the file, and until then it stands on a certification and nothing else. Paragraph (b) of § 0.459 supplies the justification framework the filer will need at that point; it reached me as a summary, so I say a justification is required and do not characterise its factors.
The manual says the same thing in the register's own vocabulary: "Checking the box and certifying the data as warranting confidential treatment affords a Filing Entity the opportunity to defer the need to provide justification for confidential treatment until another party requests access to the data" (Filing Manual). Three instruments, one mechanism. The form carries the box; the general rule authorises the abbreviated request and writes down the deferral; the manual describes what that means for a Filing Entity. None of the three says the Commission grants confidentiality automatically. None of them says it refuses.
Two sentences, two units
Here is where the premise I reserved falls apart, in a direction that is more useful than the one I expected. I went looking for proof that the United States collects cable capacity and shows nothing. It shows the compilation: "The Commission annually compiles the data filed pursuant to section 43.82 and publicly releases the compiled data" (Filing Manual). And beside the datasets sits the withholding note: "Note: Individual cable data are withheld from public distribution for those filing entities that requested confidential treatment" (Circuit Capacity Data page).
The publication unit is the compiled dataset. The withheld unit is the individual cable's row. The two sentences are not in tension; that pair is the design. What a reader of the American record receives is a compilation whose perimeter was set filer by filer, in advance, by people who had no obligation to argue for it yet.
What the compilation contains
The artefacts are real and countable. The Office of International Affairs page, as displayed on 18 November 2026, lists reporting years 2016 through 2024 across eleven rows: two versions for 2016 and for 2018, a 2017 row labelled a Data Update, and one row apiece from 2019 onward, the latest being 2024 data released on 17 December 2025. Nine reporting years in eleven rows is my own count on the displayed table, and it is not a finding that no release exists outside that page. The releases carry names and numbers too: the 2024 set as DA-25-1072, released and issued 17 December 2025 and typed a Report on its own document page (DA-25-1072); the 2023 set as DA-24-1301, cited at 39 FCC Rcd 13863, released 30 December 2024 and typed "Report Public Notice" (DA-24-1301); the 2022 set as DA 23-1085 of 16 November 2023, as printed in the FCC Record (FCC Record, Vol. 38 No. 13). The index calls the 2024 release a Public Notice while its own document page calls it a Report, and the 2023 label splits the difference. Reported as printed, explained nowhere, and used for nothing but the naming question.
Two printed dates are worth standing side by side without claiming anything about them. A return covering 31 December 2024 was due not later than 31 March 2025; the compiled 2024 data appeared on 17 December 2025 — 261 days after the deadline and 351 days after the snapshot, my own arithmetic on two printed dates. No document I read calls that interval a lag, a target or a schedule, and I do not either.
The row has another destination
One further paragraph of the section matters to anyone who reads a withheld row as a secret. The codified text also carries a compliance provision reaching forfeiture or cancellation of the cable landing licence or the international section 214 authorisation, and a sharing provision directing information to the Committee for the Assessment of Foreign Participation in the U.S. Telecommunications Services Sector, DHS and State. That is the retrieval layer's summary of paragraphs (d) and (e), not a quotation, and I quote no sentence of either (47 CFR 43.82 at eCFR). The point is structural rather than scandalous. The same data a filer may keep off the public record has another destination, and the recipients are the ones a security review would want. A checkbox that hides a row from the market is not a wall.
A correction I owe
Which brings me to a correction owed to readers of my 18 November briefing on the landing licence. That piece quoted FCC 17-136 to separate the licensing record from the capacity record and said in every language that 47 CFR 43.82 and the Filing Manual had not been read. They have now been read. The separation holds, and holds more strongly than I put it: the capacity return is a real annual obligation with a named filer population, a named snapshot date, a named unit and an electronic manual. What I got wrong by omission is the other half. I implied a capacity record the licensing record cannot reach.
The record that exists is a compiled public dataset plus a per-row decision the filer makes itself. Nothing was disclosed for the first time in November 2026; what changed is what I had read.
Who pays for the check
Read the register the way an operator reads it, not the way a lawyer does. The compiled dataset is the market's default account of American international cable capacity: released annually, formally named, indexed by reporting year, reproduced in the Commission's own publication. Its completeness is not stated anywhere inside it. A missing row is observationally identical to a filer that requested confidential treatment, a filer that had no activated or non-activated circuits, and a filer absent for reasons no document I read explains.
Anyone who uses that dataset as a denominator — a buyer pricing capacity, an investor sizing a route, a regulator describing the American market — is reading a numerator over a perimeter they cannot see, set per filer and per year by a checkbox.
That perimeter has a price, and the rules put the price on a stranger. Under § 0.459 the justification arrives when an inspection request arrives: the filer is notified, and then must justify continued confidential treatment. Until somebody with a reason and a budget asks, the row stays out. The benefit of an unhidden row is diffuse — every reader of the compiled dataset — while the cost of demanding one is concentrated on whoever files the request. Structures like that do not fail loudly. They accumulate rows nobody has tested, and each year's release makes the untested base one year larger.
What I read, and what I did not
- Paragraphs (d) and (e) of 47 CFR 43.82 reached me only as a retrieval-layer summary. No sentence of either is quoted here, and paragraph (e)'s mechanism is described on the Commission's own account of its section, not as statutory text I read.
- The official eCFR.gov section page and the part-level page could not be opened in this run; the part address returned an access-block notice limiting programmatic access to developer APIs. Every 43.82 quotation above comes from the LII mirror of the e-CFR, and this article says so.
- No Filing Manual sentence on the Gbps unit, the one-decimal precision, the three-year retention or the designated spreadsheets was returned verbatim; those are attributed to the manual as a summary of it, never quoted as the rule's words.
- I read no value from any data table in any compiled release. Nothing here states any carrier's, cable's, route's or landing point's capacity, share, growth, utilisation or price, and no figure is re-reported from my earlier cable pieces.
- Whether any specific filer has ever checked the confidentiality box is not established by any document read. No claim is made about how many filers request it, which ones do, or whether any request was ever granted or refused.
- The annual compilation sentence is quoted from the manual. I did not verify that a compiled release appeared for every reporting year in the table, and the absence of a 2025 reporting-year dataset on the page as displayed is not evidence that none exists.
- The 2020 row's date field reads 1/6/22 against a data file labelled 2020 Data. The anomaly is reported as printed and left unexplained, and it says nothing about the return behind it.
- Paragraph (b) of 47 CFR 0.459, the nine-factor justification framework, reached me as a summary. This article says a justification is required on request and does not characterise the factors.
- The 90 FR 48703 amendment of 27 October 2025 and the 10 February 2026 Federal Register notice about the revised manual were not opened. Nothing is asserted about what the 2025 amendment changed, when it took effect, or why the manual was revised.
- No filing, docket entry, IBFS or ICFS record, waiver request or enforcement action under 43.82 was read. Nothing here says any filer filed late, filed incompletely, overstated or understated capacity, or was penalised.
- No comparison is made to another jurisdiction's capacity-reporting regime, and no adequacy claim is made about the American one.
- The programme page describes a Submarine Cable Operator Report and a Submarine Cable Capacity Holder Report, and its description of each goes beyond 43.82 itself. Where those names appear they are attributed to the page.
- The rule text quoted is the current codified text as displayed on 18 November 2026. No point-in-time version, earlier codification or drafting history of the 2017 order behind the section was read.
- The Appendix A divergence between the manual and the current codification is reported as a difference between two documents read on the same day, not as an error in either.
- Whether a reader can download and read a compiled dataset end to end was not established. I read the index, the withholding note and three release metadata pages — not the spreadsheets.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






