Summary

  • APNIC reports a 7.47-business-hour average Helpdesk response time in Q1 2026, against a target of 12 hours or less, and 95.5% favorable Helpdesk ratings against a 93% target.
  • Those are positive aggregate results. The public update does not define the response event, publish the case or rating base, split results by queue, or show a distribution or time to resolution.
  • A consistent quarterly receipt could explain the clock, cohort, median and tail, and resolution age while keeping individual Member requests private. That is a reporting proposal, not evidence that APNIC has missed a target or lacks internal data.

The result deserves to be read on its own terms

APNIC’s Secretariat has put a clean pair of figures on the public record. Its first-quarter 2026 update says the average Helpdesk response time was 7.47 business hours, against a target of no more than 12. It also says 95.5% of Helpdesk satisfaction ratings were “excellent” or “above average,” compared with a target of at least 93%.[^1] Both results clear the stated thresholds. They should be described as good reported performance, not treated as a hidden warning.

The figures appear in a broader account of the Secretariat’s first quarter, presented after the Executive Council met in May. The update also reports 20 Member meetings, improvements to website live chat, and an 89% user-satisfaction result for MyAPNIC.[^1] That last number is a different measure. It should not be added to, substituted for, or used to explain the Helpdesk rating.

This distinction matters because the headline figure is unusually easy to overread. “Average response time” sounds like a clock every Member can picture. Yet the update does not say which event starts or stops that clock. It does not call the measure a first response, and the article should not do so for it. Nor does “response” mean a request was resolved. An acknowledgement, a useful answer and a completed registry action are different service events. The public report does not tell readers which one the 7.47-hour measure captures.

That omission does not make the number false or the result unhelpful. APNIC has published a target and a favorable quarter-level average. The limit is narrower: a reader cannot infer from that average how many requests were included, whether different queues or channels performed similarly, how spread out the wait times were, or how long cases took to reach resolution. The same caveat applies to 95.5%. The update gives the share and the rating labels, but not the number of ratings, invitation or response rate, survey wording, collection channels, or any weighting method.

A trend needs a stable ruler

There is an earlier benchmark, but it is not automatically a trend line. APNIC’s account of its March 2026 AGM reports that the 2025 Annual Report presentation showed an average Helpdesk response time of 7.6 business hours, down from 8.4, and that 95% of surveyed users rated the service “excellent” or “above average.” It gives the same broad targets: fewer than 12 hours and at least 93%.[^2] That is useful context: the 2025 figures were also favorable, and the 2026 quarterly update says 7.47.

But a decimal in one report and a rounded figure in another do not by themselves establish a like-for-like improvement. The reporting periods differ. The published summaries do not supply a matched definition of “response,” the case and rating bases, or an explanation of how channel mix and exclusions were handled. The Q1 figure is more precise on its face, but added decimal places cannot repair a missing definition. Until those pieces align, the fair reading is that both reports describe favorable results against APNIC’s stated targets—not that the service improved by a calculable amount between them.

APNIC’s own account of feedback offers helpful context without filling that measurement gap. Its review of the second half of 2025 says Members consistently described positive support experiences, while some wanted clearer, more practical guidance for using MyAPNIC to manage Internet number resources. APNIC lists updated Help Centre material and a planned review of its articles among its actions.[^3] A separate account of first-half 2025 feedback mentions comments about timeliness, clarity, follow-up and self-service.[^4] These are APNIC’s summaries of feedback from earlier periods.

They do not show that those issues persisted into Q1 2026, and they are not the sample behind the 95.5% figure.

That is the strongest institutional reading: APNIC is reporting positive service measures and describing concrete work on user guidance. A quarterly score and a feedback narrative answer different questions. The score tracks a defined outcome only to the extent its definition is published; the narrative explains themes and actions, but does not quantify the distribution of support experiences. Both can be useful without one standing in for the other.

What a public service receipt could add

APNIC says this is the first in a series of quarterly reports to be shared after each Executive Council meeting, with the aim of giving Members a consistent view of activity over time.[^1] That creates a practical opportunity: the next report can preserve the useful headline while making the ruler visible.

A compact receipt would name the service and period, state what counts as a response, and describe the business-hours clock. It would show the number of eligible cases and any exclusions, then provide the average alongside a median and a high percentile. A queue or channel split could be included where it is useful and safe to publish. Response and resolution should remain separate measures: the time until a reply does not tell a Member whether the underlying request was completed, and a growing backlog may not be visible in a response average.

The satisfaction result needs its own denominator. A reader should be able to see the number of ratings, how Members were invited to respond, the survey prompt, the response rate if known, and whether the published percentage combines several channels. “95.5% of ratings” is not the same statement as “95.5% of Members,” and it is not evidence that every request received the same evaluation. If a small cell cannot be disclosed safely, APNIC could suppress it and say so rather than imply that the figure covers a uniform population.

The aim is not a dashboard full of private tickets. APNIC handles registry and resource-management work for a regional membership; a useful public measure need not identify a Member, resource or case. A stable aggregate definition can show what was counted, how the result compares with the target, and when a future quarter is not comparable. The 2026 Activity Plan already treats member service as a planned objective, while the Q1 update supplies the public target and result.[^1][^5] A reporting receipt would connect those two sides of accountability without turning a target into a guarantee for each case.

The evidence available here supports a bounded conclusion. APNIC says the Helpdesk beat its response-time and satisfaction targets in Q1 2026, and its recent feedback accounts describe positive support alongside improvements to user guidance. The public update does not reveal enough about the underlying cohorts to calculate a response distribution, compare every queue, or infer resolution quality. That is a limit on what outsiders can conclude—not proof that APNIC lacks the data or that its service fell short. The most useful next step is to keep the favorable result and publish the method beside it.

Sources

[^1]: APNIC Secretariat Q1 2026 update. [^2]: Key moments from the APNIC AGM at APRICOT 2026. [^3]: Listening and responding to Member and community feedback from the second half of 2025. [^4]: Acting on Member and community feedback from the first half of 2025. [^5]: APNIC 2026 Activity Plan and Budget, Member Service objective R3.1.