"The 100th Electron has left the factory, headed for launch," Rocket Lab posted on 29 October 2026, "and the 99 before it." [1] That is the easy half of this week's story. It is a count of rockets built, not rockets flown. The difference matters more than the celebration suggests. Five days later, at 5:41 a.m. New Zealand Daylight Time on 3 November 2026, Rocket Lab's ninety-ninth Electron lifted off from Launch Complex 1 on the Māhia Peninsula. [2][3] The hundredth Electron to fly is still ahead of it: no earlier than 14 November 2026, inside the week this article publishes. Two different hundreds, in the same fortnight. For once, neither number is wrong.
Rocket Lab's own description of the coming flight calls it an unprecedented milestone for a commercial small-lift orbital rocket, a threshold rarely crossed in modern spaceflight. [2] The claim is earned. What it needs is a qualifier every time the bare number appears. This week carries two hundreds worth tracking. Only one of them has already happened.
What happened
The ninety-ninth flight, named "The Sea God Surveys," carried a synthetic aperture radar satellite called WADATSUMI-II to a 575 kilometre orbit for the Institute for Q-shu Pioneers of Space, a Japanese earth-observation operator building a radar constellation one Electron at a time. [2][3] Synthetic aperture radar images the ground through cloud and darkness alike. That is why a constellation like this is built launch by launch rather than waiting on one large platform: each satellite in orbit is immediately useful, not a placeholder for a future one. It was the tenth consecutive Electron launch for that customer, at a clean mission-success record. Eight more dedicated flights are already booked to complete the constellation by 2030. Running total: 99 Electron flights overall, 20 of them this year. Each of those ninety-nine is a discrete, countable event with a flight record attached. That is exactly the property a manufacturing milestone lacks, and, as the next section covers, so does a jurisdictional dispute, until someone goes and checks.
A word on the date. Rocket Lab's release and a second outlet that republishes its language word for word both give the same instant: 5:41 a.m. NZDT on 3 November. [2][3] A third report, previewing the launch a day earlier, called it "Monday," which is 2 November in United States Pacific time. [4] Nothing here is wrong. New Zealand Daylight Time runs roughly twenty-one hours ahead of the US West Coast in early November. The same ignition is a Tuesday morning at the launch site and a Monday afternoon on the other side of the Pacific. This series dates Māhia launches in NZDT, as it has before, so the record here is 3 November. Two sources giving different dates for the same event are not always in conflict. Sometimes they are two clocks disagreeing about which day it already is. The fix is to ask which clock is being read, not which source is wrong.
The hundredth Electron's actual flight, named "The Mountain God Rises," is booked no earlier than 14 November 2026 from the same pad, carrying another radar satellite for the same customer. [2][5] That "no earlier than" is the one honest piece of uncertainty in this story. A launch date can slip a day or a week, for reasons that have nothing to do with the number painted on the fairing. The count behind it cannot. Ninety-nine rockets have already flown. The hundredth is next, whichever day it goes.
The other count, and who gets to answer for it
A second story, held back from this slot deliberately, belongs to the same week for a different reason. It is not about which number is correct.
On 25 October 2026, Radio New Zealand reported that US Space Command had directed the New Zealand Defence Force not to release operational detail about a facility at RNZAF Base Auckland. The request came from an Official Information Act filing RNZ had made. [6] The NZDF's own account, quoted directly: "We have received advice from US Space Command that does not change the decision on your request." [6] The sharper detail sits one sentence later. The NZDF suggested RNZ try the United States Freedom of Information Act instead. [6][7] A New Zealand agency, answering a New Zealand statutory request about a facility on New Zealand soil, pointed the requester at a foreign country's own disclosure law.
The facility coordinates the Pacific segment of the Joint Commercial Operations network, a structure the Pentagon built in 2020. It routes roughly US$50 million a year of commercial satellite sensor data into US Space Command, for distribution to combatant commands and allied partners. [6] Defence officials maintain that New Zealand retains sovereignty over the site itself. They acknowledge they cannot release mission logs without American authorisation. [6] The Auckland hub runs a follow-the-sun watch across three time zones, feeding commercial radar, optical and radio-frequency tracking into shared operational pictures. [7] A companion report quotes a US Space Force official describing plans to extend the network into all six ground combatant commands within the following year. [7]
I've used the Pirate Radio Parallel from my book Space Mafia eight times in this series. Every one of those times, it ran the same direction. An operator sits outside a jurisdiction's reach, the way 1960s radio ships anchored in international waters to broadcast past laws that could not follow them past the coastline. The parallel is built on absence. Escape the border, and the law that should apply does not.
Auckland is the mirror image. The facility is not outside New Zealand's jurisdiction; it sits inside it, under New Zealand's own Official Information Act, on New Zealand's own soil. The law still does not reach it. Answering the question requires a release the host nation does not control. A pirate broadcaster escapes a coastal state's authority by sitting beyond its waters. This facility sits inside the waters, and the authority still does not land. It is the same question asked from the opposite direction: whose jurisdiction actually reaches a transmitter, once you ask who controls what can be said about it. Oman's Etlaq Spaceport, the real-world instance this series has cited before for the canonical sense, is still the clean case: an operator choosing a jurisdiction for its light-touch licensing. Auckland is not choosing anything. Here, the jurisdiction itself cannot answer the question.
New Zealand's own sovereignty claim and the authorisation requirement are not in tension with each other. That is what makes the gap durable, rather than a one-off oversight. A nation can host a facility, retain sovereignty over the ground it sits on, and still need a foreign partner's sign-off before saying anything about what happens inside it. That is exactly the gap an Official Information Act request cannot close, no matter how it is worded. The request is addressed to the wrong layer of the arrangement.
That is not a defect unique to one hub. The Joint Commercial Operations network's own stated purpose is to distribute commercial sensor data to hundreds of agencies and governments. [6] Auckland is unlikely to be the only node where a host nation's law meets a foreign command's release authority and stops there. A network built to move information across borders quickly can also leave a host government unable to answer questions about what moves through its own territory.
New Zealand's general election fell on 7 November 2026, and this article publishes inside the three-week window between polling day and the declaration of official results on 27 November. The caretaker convention applies through that period. Nothing about the facts above depends on who holds office when the declaration lands. The Official Information Act obligations the NZDF answers to, and the arrangement that shapes how it can answer them, exist independent of any government. What follows is the agencies' own stated positions, attributed to them, not an assessment of how well either one performed.
What this means for New Zealand organisations
New Zealand's Outer Space and High-altitude Activities Act, the GBSI Act in this series' own shorthand, is not the instrument in play in either of this week's stories. It governs ground infrastructure, launch and payload authorisation through the New Zealand Space Agency. Rocket Lab's own launches from Māhia are licensed domestically under it. The Joint Commercial Operations hub's information regime is not, because an Official Information Act request and a bilateral defence data-sharing arrangement sit outside the Act's scope entirely. An organisation checking its own GBSI Act obligations this week learns nothing new from either headline. It should not read either one as changing what the Act requires.
What does change, for a board or an architecture team assessing dependence on a foreign-hosted or foreign-controlled data arrangement, is the shape of the question worth asking. Rocket Lab's hundredth launch shows that a count-based milestone is a cleaner thing to track than a date. A schedule can slip, but a number already built cannot un-build itself. The Auckland hub shows the opposite problem in a different domain. Physical presence on your own territory is not the same thing as informational control over what happens on it, when the facility's own release authority sits with a partner elsewhere.
Both failure modes are preventable in principle. Neither needs a new regulation to fix. The count-versus-date failure is preventable simply by not quoting a schedule as if it were a settled fact; Rocket Lab's own language already does this correctly, using "no earlier than" rather than a fixed date throughout. The informational-control failure is harder to catch. It depends on terms negotiated well before any particular request is ever filed, inside an arrangement a board may not have reviewed since the day it was signed. The GBSI Act's own transitional compliance window closed on 29 July 2026. Nothing in that Act reaches an arrangement of this kind.
Four questions worth asking before the next version of either story lands, not after:
- Is the milestone you are tracking a count, or a date someone estimated.
- Does your own jurisdiction over a facility include the right to release what it knows.
- Who holds the authorisation to answer a statutory request about a shared or hosted arrangement.
- What does "the agency recommends a foreign statute instead" actually tell you about where control sits.
New Zealand's standing operational dependencies have not moved since they were last checked. Close to 99 per cent of the country's international data traffic still transits a small number of subsea cables, all landing at Auckland, with no large-country alternative-route redundancy. SouthPAN, the joint Australia and New Zealand satellite-based GNSS augmentation system led on the New Zealand side by Toitū Te Whenua LINZ, depends on contracted satellite transponder capacity. A dedicated AWS Asia Pacific (New Zealand) region has operated in-country since September 2025, narrowing one offshore cloud concentration this series has flagged before.
What to watch
One further count moved this week, in a different domain. This series has tracked it since a five-satellite, five-accelerator baseline first appeared in its own ledger. On 30 October 2026, five already-flown Trillium-generation chips aboard Google's Project Suncatcher prototype produced their first inference output: a haiku, returned during a ground-station pass over Svalbard, running on the open-weight Gemma model. [8] The poem itself, Google's own transcription: "Blue marble below / Data streams in silent grace / Starlight feeds my core." The round trip, prompt up, inference on board, poem down, needed no terrestrial data centre at all. This project's own running description of orbital compute has read "flown and operating" for months. This is the first entry that reads flown, operating and producing. Whether that count moves again before the hundredth Electron does is worth watching on its own terms, not because the two are related.
Two threads carry past this week. Rocket Lab's own manifest puts the actual hundredth Electron flight no earlier than 14 November, still subject to the ordinary slip any "no earlier than" date carries. A slip of a week would not change the count; it would only change which Monday this series has to update the number again. And the Joint Commercial Operations network's own stated ambition, extending into all six ground combatant commands, means Auckland's jurisdictional question is a preview rather than a one-off. A second host nation receiving the same kind of request, and the same kind of answer, would turn this week's finding from an isolated case into a pattern. Watch whether either count changes before the next Monday. Watch which one changes on a schedule, and which one changes on a decision.
Three numbers belong to this week, not two. Ninety-nine Electrons have flown. One statutory request got pointed at a foreign country's own disclosure law instead of answered. And one orbiting chip, asked for a response, returned a haiku rather than nothing at all.
There is an open-source dimension here, before extending this one step further. Ground segment and flight software are not uniformly proprietary across this industry. NASA's Core Flight System was released under an Apache licence by Goddard Space Flight Center in 2015 and has flown on more than twenty NASA missions since. It is a complete, auditable flight-software stack that any operator, allied or otherwise, can run without asking a vendor's or a partner's permission to see how it works. That is a meaningfully different sovereignty position from hosting a node inside someone else's network and depending on that network's own command structure to decide what gets released. An open flight-software stack does not settle a jurisdictional question on its own. It removes one layer of dependency that a closed, foreign-controlled system does not.
The same distinction carries directly into the defence side of this week's finding. The Joint Commercial Operations network exists specifically to move allied commercial sensor data into US Space Command, for distribution to combatant commands and partner governments. That means the jurisdictional gap this week's finding exposes in New Zealand is a structural feature of the network itself, not a one-off. A host nation's physical sovereignty over a facility and its informational sovereignty over what that facility discloses are two separate questions. An allied commercial-data arrangement can satisfy the first while leaving the second with the controlling command. That is a procurement and governance question before it is a conflict one. Any organisation entering a data-sharing or hosting arrangement with an allied military structure is agreeing, in effect, to the same split.
Your organisation may host, or depend on, a facility whose disclosure decisions sit with a partner rather than with you. Have you ever tested what happens when someone asks it a question only the partner can answer?
This is one of seven weekly series in The Hamberger Report. Subscribe on LinkedIn and the next one arrives in your feed.
The views expressed in this article are entirely my own, informed by more than 30 years of professional experience in architecture, security, and technology leadership in New Zealand. I write as director of Te Pono Limited; the views are personal and do not represent the position of any client, any government agency, or the New Zealand government. My commentary on legislation and policy is analytical, drawing on publicly available sources and my professional expertise in architecture, security, and AI governance, and it is politically neutral.
Andreas Hamberger is a New Zealand leader in Architecture & Security and Associate Member of the Institute of Directors. Space Mafia examines the sovereignty implications of orbital compute infrastructure.
This article was produced with AI assistance under my direction. Research, drafting and images pass through a pipeline I built and govern: automated gates for source verification, forbidden language and political neutrality, and my own review before anything is published. The tools include Claude, Gemini and Openart. The frameworks, arguments and editorial judgements are mine and are the same discipline I apply to the AI systems I audit for clients. AI accelerated the work; the thinking, and the responsibility for it, are mine.
[1] Rocket Lab (@RocketLab). X post. 29 October 2026. https://x.com/RocketLab/status/2115897086046802163
[2] StockTitan. "Mission Success: Rocket Lab Launches 99th Electron." 3 November 2026. https://www.stocktitan.net/news/RKLB/mission-success-rocket-lab-launches-99th-electron-pskns08xpkca.html
[3] Newsroom America. "Rocket Lab Launched Its 99th Electron Rocket, Deploying a QPS-SAR Satellite for iQPS From Launch Complex 1; the Company's 100th Electron Launch Is Scheduled for No Earlier Than November 14, 2026." 3 November 2026. https://newsroomamerica.com/a/1Ng2E3HuTVk9kWQ9OC17Wh7hSMZ/rocket_lab_launched_its_99th_electron_rocket_deploying_a_qps_sar_satellite_for_iqps_from_launch_complex_1_the_company_s_100th_electron_launch_is_scheduled_for_no_earlier_than_november_14_2026.html
[4] TechTimes. "Rocket Lab Targets 100th Electron Launch After iQPS Radar Mission Monday." 1 November 2026. https://www.techtimes.com/articles/329833/20261101/rocket-lab-targets-100th-electron-launch-after-iqps-radar-mission-monday.htm
[5] Rocket Lab. "iQPS: The Mountain God Rises." Mission page. https://rocketlabcorp.com/missions/launches/iqps-the-mountain-god-rises/
[6] RNZ. "US Space Command Applies Gag Over Auckland Space-Watching Hub." 25 October 2026. https://www.rnz.co.nz/news/politics/2149096/us-space-command-applies-gag-over-auckland-space-watching-hub
[7] SatNews. "U.S. Space Command Directs New Zealand to Withhold Operational Data on Auckland Tracking Hub." 25 October 2026. https://satnews.com/2026/10/25/u-s-space-command-directs-new-zealand-to-withhold-operational-data-on-auckland-tracking-hub/
[8] Google. "Google Receives Response From Project Suncatcher Prototype Satellite in Space." 30 October 2026. https://blog.google/innovation-and-ai/models-and-research/google-research/project-suncatcher-satellite-response/