Updated October 31, 2026 Version 5 is an interface baseline, not a coverage guarantee NASA’s specification page, checked for this October 31, 2026 refresh, identifies LunaNet Interoperability Specification Version 5, published February 7, 2025. It also links the Augmented Forward Signal recommended standard. Those are concrete documents a terminal designer can use, rather than a promise that a lunar internet is already available. NASA, ESA, and JAXA jointly develop the specification, which covers direct-with-Earth links as well as lunar relays and positioning, navigation, and timing. The distinction matters when comparing missions. Compatibility describes the interfaces a user and provider share. Availability depends on actual spacecraft, their orbits, functioning ground stations, and an agreed service window. A LunaNet-compatible radio does not by itself guarantee continuous coverage of a crater floor or a backup route during a relay outage. What NASA’s testbed actually verifies NASA’s current LCRNS project page describes its Interoperability and Performance Testbed as a hardware-in-the-loop facility emulating a universal lunar user terminal. The facility checks commercial relay performance against NASA’s service requirements and the relevant LunaNet sections. This is a more specific milestone than announcing support for the standard: the user-side hardware must exchange signals and data with a representative service under test. For mission planners, a useful acceptance checklist separates link compatibility, measured service performance, and mission coverage. Ask which specification revision was tested, which terminal configuration was used, what navigation or communications functions were demonstrated, and what happens when the link disappears. Ground validation is essential, but it is not the same evidence as an operational relay meeting its commitments in lunar orbit. Moonlight puts numbers on the architecture, not on service already delivered ESA’s published Moonlight architecture calls for five lunar satellites: one for high-data-rate communications and four for navigation, supported by three dedicated ground stations. Its October 2024 programme announcement prioritised the lunar south pole and described initial services by the end of 2028, full operations by 2030, and navigation interoperability tests in 2029. These are dated programme targets from that source, not independently verified launch or commissioning outcomes as of this refresh. That division of roles also explains why counting satellites is not enough. A communications relay and a navigation spacecraft do different jobs. The availability of a data path cannot be substituted for the geometry and timing quality needed to estimate position. A service proposal should state both capabilities separately, including the terrain and orbital assumptions behind its coverage claim. Three checks before buying a lunar network service First, tie the contract to an explicit interface baseline and tested user equipment. Second, request coverage and outage assumptions for the actual landing site or rover route, not a generic south-pole map. Third, separate service demonstration, initial availability, and full constellation operation in the schedule. Those checks preserve the promise of a multi-provider network without confusing a standards milestone with a finished utility. This refresh expands the engineering context rather than claiming a new launch. The earlier June update below remains a dated account of test-hardware work. The newly checked NASA pages confirm that interoperability and performance validation remain central to the project’s public description. Sources checked October 31, 2026: Primary reference ; Technical reference ; Supporting reference . The Moon still has no GPS, no cell towers, and no always-on data network. Every mission that heads there today has to fight for contact time, especially near the south pole and on the far side. LunaNet is NASA's effort to change that by setting the technical rules for a shared lunar communications and navigation layer. This is not one spacecraft or one contract. It is a framework that lets NASA systems, commercial relay satellites, and partner agencies exchange data in compatible ways. Since this article was first published, that framework has moved a step closer to hardware, with NASA's Lunar Communications Relay and Navigation Systems project continuing interoperability testing and Intuitive Machines pushing toward its first Lunar Data Network satellite. AI-generated image Concept art of a lunar lander routing data through orbital relay satellites. Credit: AI-generated What's New Since March NASA's LCRNS program continues validating relay interoperability for south-pole missions, LuGRE's lunar GPS experiment has become a real proof point for lunar navigation, and Intuitive Machines is preparing the first node in its commercial Lunar Data Network. LunaNet is still early, but it is no longer just a white paper. Why the Moon Needs Its Own Network Layer Apollo-era communications assumed short missions at low-latitude landing sites with direct visibility to Earth. Artemis and the broader cislunar economy are aiming somewhere much harder. The south pole has the water ice, the lighting advantages, and the strategic attention, but it also has terrible geometry for direct communications. Craters block line of sight. Ridges create intermittent links. Permanently shadowed regions can cut a rover off completely. Navigation is the second half of the problem. Earth orbit spacecraft can lean on GPS. Lunar vehicles cannot assume the routine GNSS availability that many Earth-orbiting spacecraft enjoy. Landers, rovers, and orbiters currently stitch together position estimates from star trackers, inertial systems, terrain-relative navigation, and periodic Earth contact. That works for isolated missions. It works poorly for a future with frequent cargo flights, crewed sorties, autonomous construction gear, and commercial surface operations all sharing the same region. 3 Service areas: communications, PNT, and information sharing 1.25M Miles from Earth covered by NASA's Near Space Network service region 2025 Year LuGRE got the first GNSS fix on the Moon 2026 Year NASA is tying relay testing more directly to Artemis-era operations What LunaNet Actually Is LunaNet is best understood as a standards stack, not a single network owner. NASA's LunaNet Interoperability Specification tells relay providers and users how to exchange data, time, and navigation services in a common way. That matters because the lunar network is unlikely to be built by one government alone. NASA, ESA, JAXA, commercial operators, and defense-adjacent providers all want pieces of the architecture. The logic is familiar. On Earth, internet users do not care which company owns every fiber segment between points A and B. They care that the system works end to end. LunaNet aims for that same kind of interoperability, but in a much harsher environment where delays are longer, geometry is awkward, and every kilogram launched still matters. NASA's Lunar Communications Relay and Navigation Systems, or LCRNS, is the programmatic bridge between the specification and real services. LCRNS is meant to support Artemis, science missions, robotic campaigns, and eventually routine surface activity by building commercial relay capacity into NASA's Near Space Network. LunaNet components in plain English Layer What it does Why it matters Relay services Moves voice, telemetry, commands, and science data between lunar users and Earth Keeps assets connected when Earth is below the horizon PNT services Provides positioning, navigation, and timing references Lets landers and rovers locate themselves without constant ground intervention Interoperability rules Defines compatible interfaces, signals, and performance expectations Allows multiple providers to serve the same lunar user base The 2026 Shift, From Concept to