Summary

  • The Customer Standing Committee is chartered to monitor agreed IANA naming service levels every month, analyse the operator's report and publish a finding, which turns a missed target into a public sentence rather than a private exception.
  • Its January 2024 finding recorded one named miss — Technical Check (Retest) at 12.88 minutes against a ten-minute threshold at the 95th-percentile target — and still rated the month satisfactory, while its June 2026 finding recorded all 64 then-defined thresholds met. Between either finding and any consequence sit formal steps that move on procedural or implementation failure, not on the metric alone.

A number, and the sentence it lives in

The January 2024 monthly performance report for IANA's naming functions carries one awkward line. Technical Check (Retest) — Routine (Technical) is recorded at 12.88 minutes against a ten-minute threshold at the 95th-percentile target (January 2024 operator report). The same report records 123 retests across the month with a mean of 3.15 minutes, and attributes the exception to waiting on unreachable nameservers, including timeouts and retries. Its narrative says, in the operator's own words: "One request exceeded the technical check threshold of 10 minutes."

Both figures sit in the same document because they answer different questions. A mean over 123 retests describes the ordinary retest; the threshold at issue is written against the tail. Three point one five minutes cannot convert a breached ninety-fifth percentile into a pass, and no honest reading of the table makes it try. The report is equally clear that 12.88 is the response-time statistic compared against a threshold, not a mean with a ten-minute target hung on it.

The committee that turns a metric into a sentence

The body doing the converting is the Customer Standing Committee. Its amended charter was approved by the ICANN Board on 3 May 2026 and took effect on 3 July 2026, and it obliges the committee to monitor agreed service levels monthly, analyse the reports provided by the IANA Functions Operator, publish monthly findings and work with the operator on performance-resolution plans (CSC charter). The same charter tells the committee to look for systemic or persistent patterns in complaints, and tells it, in the same breath, that it does not intervene in individual operator-customer disputes.

Membership is set by the Bylaws, not by the committee. Section 17.2(a)(i) requires "Two individuals representing gTLD registry operators appointed by the Registries Stakeholder Group", alongside two ccNSO-appointed country-code representatives and a liaison from Public Technical Identifiers, with an optional seat for other TLD registries and optional non-voting liaisons from the GNSO, ALAC, NRO/ASO, GAC, RSSAC and SSAC. Annual slates are approved by the ccNSO and GNSO (ICANN Bylaws).

On 14 February 2024 the committee published its finding for January 2024. Its overall sentence reads: "PTI met the service level agreement for 98.4% of defined metrics." The named miss was Technical Check (Retest) — Routine (Technical). The committee accepted the operator's explanation, identified no persistent problem, concluded that no further action was needed and reported no new escalations (January 2024 CSC findings).

Read that percentage precisely. It is the share of defined metrics that met their targets, not the share of individual requests completed on time. A month in which 98.4% of metrics passed is a month in which the ledger was mostly green, and it is also a month in which one specific tail measurement did not clear its line. Both statements are true, and they are not the same statement.

Three propositions, not one score

It is tempting to collapse the paperwork into a single performance verdict. The documents resist it, and the resistance is the interesting part. A metric result is a measurement. A qualitative finding is a judgement about whether that measurement signals a problem worth chasing. An escalation record is a statement about what the institution did next. Three propositions, three hands, and a clean one does not vouch for the other two.

The June 2026 cycle shows the same separation from the other direction. The committee's finding, dated 22 July 2026, states: "PTI met all 64 of the currently defined thresholds." It rated performance excellent, reported no metrics requiring close tracking and reported no new escalations during the period (June 2026 CSC findings). The operator's report for that month supplies the texture: Technical Check (First) at 3.50 minutes against a ceiling of 50 minutes at the 95th percentile, retest at 1.18 minutes against 10 minutes at the same percentile, Validation and Reviews at 1.54 days against 5 days at the 90th percentile, Root Zone Publication at 58.00 hours against 72 hours at the 99th percentile, root zone management system availability at 100.00% against a floor of 99%, and root zone file accuracy at 100.00% against 100% (June 2026 operator report). Its summary table is headed "Percentage of SLA thresholds met of those defined" and totals 64 of 64.

That heading is the honest one, and it is also the trap. Sixty-four of sixty-four is a conformity statement about the thresholds that existed in June 2026. It is not a statement about the thresholds that existed in January 2024, and this review did not obtain the two periods' metric definitions, denominators or target values side by side. So no improvement is computed here between the 98.4% month and the 64-of-64 month. A reader who wants a trend needs the table, not the score.

The ladder, and what actually trips it

Between a published finding and an operator consequence sits a written procedure. The CSC and PTI Remedial Action Procedures, Version 2.0, adopted by the committee in January 2019 and by PTI in February 2019, require the committee to invite the PTI President's comments before finalising a finding on a performance issue, ordinarily within ten business days (Remedial Action Procedures). A remedial-action report then goes to the PTI President, copying the ICANN Global Domains Division President, and the meeting, the corrective plan and the committee's review carry successive ten-business-day deadlines.

Above that, escalation exists for failures of procedural, implementation or reporting obligations: to the PTI Board, then the ICANN chief executive, then the ICANN Board. If the matter is unresolved after that, the committee may raise it with the ccNSO and GNSO Councils, potentially including a Special IFR. Response deadlines can be changed by agreement, and corrective work follows agreed milestones rather than a fixed statutory clock.

The drafting is the finding. The triggers that unlock the ladder are failures of process and delivery, not the breach of a numeric target by itself. A month in which a tail measurement misses, the operator explains why, and the committee accepts the explanation, ends at the finding — which is exactly what the January 2024 record shows, including its explicit conclusion that no further action was needed.

Above the procedure sits the contract. The IANA Naming Function Contract of 30 September 2016 obliges the contractor to "act in good faith to resolve issues identified by the CSC" (Naming Function Contract). Section 7.3(c) lets ICANN amend or terminate the agreement in order to implement an approved IFR, Special IFR or SCWG recommendation, subject to the Bylaws. The Bylaws then set the preconditions for a Special IFR: unsuccessful remediation under the remedial procedures, Council review, broader consultation and both Councils' supermajority approvals, with public comment where requested. The charter closes the loop by stating that the committee cannot itself initiate operator replacement through a Special IFR.

So the sequence from a measured miss to a change of operator runs through acceptance or remediation, the PTI Board, the ICANN chief executive, the ICANN Board, two Councils' supermajority approvals, a Special IFR, and finally the contractual amendment or termination power. Every one of those is a real step with real participants. None of them is the publication of a monthly finding.

The one change that skips the queue

The thresholds themselves are not fixed in the contract. Amendment No. 1, dated and effective 7 May 2019, replaced the original annex so that root zone management conforms to externally published service levels maintained through a defined change procedure, and it distinguishes a process, a metric, an individual-request threshold, a minimum or maximum type, an aggregate compliance percentage and a measurement period (Amendment No. 1).

The procedure governing those changes was last amended on 16 July 2025 according to its own text. Public Technical Identifiers, ICANN or the committee may request a change; existing service levels stay as they are without mutual agreement; ordinary changes require public comment and approval by both the ccNSO and GNSO Councils. Changes solely to existing threshold values are exempt from those two steps (SLA amendment process).

That exemption deserves a plain sentence. A change that alters what counts as passing is the one class of change that does not have to pass through public comment and both Councils, while a change to the metric, the process or the measurement period must. The same document states that the service levels are incorporated into and enforceable through the Naming Function Contract, that the procedure does not override contractual obligations, and that the committee must initiate a complete service-level review at least every five years, measured from completion of the previous review's outcomes.

None of this establishes that any threshold was moved to flatter a monthly finding. No series of threshold values and no criteria for the committee's overall ratings were obtained here, so that inference is unavailable and unnecessary. What the record does establish is narrower and more useful: the denominator in "thresholds met" is maintained separately from the finding, and the least visible way to change what a clean month means is to edit the table.

Where this review stops

The record has edges, and they belong beside the claims they limit. The consolidated current text of the Naming Function Contract was not obtained in this review, and neither was the live service-level table: the Public Technical Identifiers agreements page and its naming services service-level page each returned only a JavaScript-required notice (PTI agreements, PTI naming services SLA page). Every threshold quoted above is therefore tied to January 2024 or June 2026 and is not presented as the current target.

The amendment trail is uneven too. ICANN's consolidated financial statements for the year ended 30 June 2026, with the auditor's report dated 6 October 2026, describe the Naming Function Contract as amended on 24 June 2024, in effect since 30 September 2021, held on a five-year term with automatic renewal pending certain requirements and renewed on 30 September 2026 (ICANN financial statements). The prior year's statements label the same contract as amended 7 May 2019. The text of whatever changed in June 2024 was not obtained, so nothing here assumes it touched a provision cited above. The amendment process document carries 24 September 2025 in its filename while its own text says last amended 16 July 2025.

The performance figures are operator-reported. No independent audit or external validation of the monthly numbers was identified in the reviewed set, and the criteria that turn a month into "satisfactory" or "excellent" were not obtained. Nor was a multi-year run of monthly findings and performance plans, so no escalation pattern and no trend is asserted here. Who employs, funds or directs the committee's secretariat is likewise not established by these documents; the arrangement described above is one of functions, information and approvals, and that is all it is described as.

What would change the reading is concrete. A finding that names a miss and is followed by a published remedial-action report. A performance-resolution plan with dates and a named owner in the public record. A threshold change accompanied by its date, its old value and its new one. Any of those would move the monthly finding from an assessment with a paper trail to a documented decision with a consequence attached. Until one appears, the honest description of IANA's naming oversight is a ledger kept in public, checked monthly by a committee that must publish, and enforced through doors that open on process failures rather than on a number.

The directory entry for the subject is here: IANA.

Sources