Updated October 14, 2026 Alpine Gets a Firm Ride Contract, Not an Operational Network Alpine has a delivery contract, not an in-orbit service record. That is the clearest way to read ispace's latest Lunar Connect progress. A September definitive agreement with Argo Space moves the first relay satellite beyond the initial March arrangement, while two October European agreements address network interoperability and ULTRA lander production. These are different kinds of progress, and none is a completed lunar deployment. On September 17, ispace-U.S. and Argo announced that they had executed the definitive agreement for Mission 2.5. The payload is now explicitly named Alpine , rather than the earlier Alpine-or-Lupine description. Argo's Argonaut, described by the companies as a water-powered space logistics vehicle, is contracted to deliver it to lunar orbit. The announced timing is as early as 2027 , not a guaranteed 2027 service start. The distinction matters commercially. A transport booking establishes a route to deployment; it does not demonstrate satellite commissioning, a reliable customer link, navigation performance, or recurring service revenue. The announcement does not disclose a delivery price, a customer service-level agreement, or a guaranteed date for the full network. Readers should not convert an undisclosed transport contract into an estimate of Lunar Connect backlog. One satellite is the first asset, not the whole constellation ispace still describes a constellation of at least five lunar satellites offering communications, positioning, observation, and space situational awareness. Its September release says the remaining satellites are expected to be deployed by 2030. It also names several possible delivery methods: ispace landers, the company's own orbital transfer vehicles, and third-party providers such as Argo. That flexibility can spread transportation risk, but each vehicle and payload interface still needs to be developed and verified. One relay cannot automatically supply continuous coverage everywhere on the Moon. Visibility depends on the satellite orbit, a user's location, terrain, ground-station access, and the rest of the network. A far-side lander and a rover working near a polar ridge have different link constraints. Positioning services also require demonstrated timing and geometry, not just the ability to send a message. The appropriate next question is what Alpine will deliver to its first users, rather than whether a five-satellite vision has already become a lunar equivalent of terrestrial mobile coverage. Moonlight cooperation is a study, not a transport award The October 6 memorandum with Leonardo and Telespazio expands a 2025 letter of intent. It covers potential cooperation in communications, positioning, navigation and timing, user terminals, space and ground segments, and transportation. The parties will evaluate integrated services that could increase coverage, capacity, and resilience. Leonardo's robotics and space AI capabilities broaden the potential scope, but the announcement does not establish a deployed cross-network capability. The same memorandum includes studying transport of ESA Moonlight satellites on an ispace orbital transfer vehicle. That should not be confused with Alpine's signed Argo delivery contract. Moonlight is a possible future application of the European cooperation, not a newly announced ESA launch or transport purchase from ispace. Nor does the memorandum show that Lunar Connect and Moonlight have merged. The practical work is to make independently developed terminals, spacecraft, ground systems, and services usable together. ULTRA has named thruster hardware, but qualification remains ahead A separate October 6 announcement gives a more concrete supply-chain update. ispace says it selected ArianeGroup pulsing thrusters and reaction-control-system thruster hardware for ULTRA and contracted related assembly, integration, and testing services. The broader memorandum explores future spacecraft cooperation and possible long-term production agreements. Selected hardware and contracted integration work are firmer commitments than an exploratory production framework. That release does not identify the replacement main descent engine as a completed, qualified propulsion system. Pulsing and attitude-control thruster selections should not be treated as proof that every propulsion decision described in March is resolved. ArianeGroup's component heritage is useful, but ULTRA still needs system-level verification of propulsion, power, thermal control, navigation, software, and landing operations as an integrated vehicle. ispace's current Mission 3 page keeps the first ULTRA launch planned for 2028, with Mission 4 planned for 2029. It describes a roughly 1,000-kilogram dry-mass lander and payload capacity of up to several hundred kilograms. The company reports that a structural thermal model underwent vibration, acoustic, and thermal-vacuum tests. Those are meaningful environmental-development milestones, not a declaration that a flight lander is certified or that a lunar landing has been demonstrated. The milestones that will change the risk assessment Mission 2.5: a published launch and transfer plan, completed spacecraft integration, delivery to the intended orbit, and commissioning results. Service performance: demonstrated customer links, coverage limits, timing performance, and operating procedures that work across organizations. European cooperation: technical interface agreements and any later definitive service or transport purchases, clearly separated from the October memorandum. ULTRA: flight-hardware integration, propulsion and navigation verification, and evidence that lessons from the two unsuccessful landing attempts have been incorporated. The strategic case is stronger when stated narrowly. Lunar Connect could give ispace an infrastructure business that does not depend on every customer flying on an ispace lander. Buying Alpine's ride from another operator demonstrates that separation. Yet it also introduces a transport-provider dependency, and the 2030 network remains a deployment plan. The decisive proof will be useful service delivered in lunar orbit, followed by reliable repeat missions, not the number of partnership announcements. Primary sources for this update ispace and Argo: definitive Alpine delivery agreement, September 17 ispace, Leonardo and Telespazio: scope of cooperation, October 6 ispace and ArianeGroup: selected thrusters and contracted AIT, October 6 ispace Mission 3: current ULTRA configuration and development milestones On March 27, 2026, ispace announced two major pivots in a single press conference in Tokyo's Nihonbashi district: a unified lander design called ULTRA and an entirely new business line, the Lunar Connect Service, targeting the emerging market for cislunar communications, navigation, and space situational awareness. The announcements came three days after NASA unveiled its Ignition plan for a permanent lunar base by 2030, and ispace made clear that timing was not coincidental. For a company that has crashed two landers on the Moon, the pivot toward infrastructure services represents a calculated bet that the revenue opportunity in keeping future missions connected could be at least as large as the transportation business itself. CEO Takeshi Hakamada put the addressable market at $3 billion annually by the 2040s and said ispace intends to capture it with a constellation of at least five satellites in lunar orbit by 2030. ispace's announcement at a press conference in Nihonbashi, Tokyo on March 27. The company plans its first Lunar Connect satellite by 2027. Credit: AI-generated illustration Starting Over: The ULTRA Lander The lander redesign was forced, at least in part, by an engine problem. ispace had been co-developing a new main engine called VoidRunner with U.S. propulsion startup Agile Space Industries since 2021. The engine was intended