Who Controls Starlink and Starshield Services Used by Ukraine?

Key Takeaways

• Ukraine reported restored Starlink and Starshield connectivity above 400 kilometers per hour on October 24.
• Terminal ownership, network operation, government procurement, and access authorization are distinct.
• Congressional inquiries are examining who authorized, implemented, and communicated the restrictions.

Ukraine’s October Restrictions and Restoration

On October 24, 2026, Ukraine’s Ministry of Defence reported that Starlink and Starshield connections were again operating at movement speeds above 400 kilometers per hour, approximately 249 miles per hour. Its monitoring systems had previously recorded restrictions. That announcement established a specific operational result: equipment on fast-moving platforms could maintain connectivity again.

The disruption had become public on October 14, when Ukrainian officials reported that terminals on platforms moving faster than 100 miles per hour, about 160 kilometers per hour, were losing service. An October 19 letter from four U.S. senators described the effect on Ukrainian drone operations. The issue concerned the speed at which connected equipment could move, rather than the internet download speed usually advertised to broadband customers.

That distinction changes the meaning of the event. A movement limit can affect an airborne terminal even when a stationary terminal retains connectivity. Describing the incident as the shutdown of Ukraine’s entire Starlink network would extend the evidence beyond the reported restriction. New Space Economy’s coverage of the October service disruption similarly distinguished affected military applications from the status of civilian subscribers and other service arrangements.

Responsibility became a separate dispute. In its November 2 analysis, the Center for Strategic and International Studies, or CSIS, described conflicting accounts involving SpaceX and U.S. officials. The analysis by Clayton Swope, Lauryn Williams, and Alexei Hoffman examined how a country’s access to a privately operated communications service intersects with decisions made by the provider and its home government.

The resulting question about control has several parts. Operating the satellites, approving a terminal, purchasing a service, authorizing a military use, and directing a change are different functions. Ukraine’s documented experience includes actions by its own ministries, SpaceX, and U.S. government customers. Those arrangements explain why possession of a terminal is only one component of access.

Restoration also has a precise date. The October 24 ministry notice supersedes descriptions of the restriction as an ongoing condition during the preceding days. It does not identify the individual who authorized the earlier change; it reports the connection behavior observed after service was restored.

How a Satellite Connection Reaches Its User

Starlink connects user equipment to a constellation of satellites in low Earth orbit. A user terminal sends and receives radio signals, and the network carries the resulting traffic toward its destination. The useful product is the complete connection between the user and the application, including the parts of the route that operate on Earth.

Low orbital altitude reduces the distance a signal travels compared with a geostationary satellite, which remains above the same region of Earth from an altitude of approximately 35,786 kilometers. Shorter travel distance reduces one component of latency, the delay involved in exchanging information. This helps explain the attraction of low-orbit networks for interactive communications.

SpaceX’s technical explanation of Starlink latency identifies several additional contributors. They include scheduling radio transmissions, processing information, moving traffic through terrestrial networks, and routing through intersatellite laser links. The satellites’ altitude does not determine the entire response time. A connection also depends on the route through gateways and onward internet connections.

A gateway is a ground facility connecting satellite traffic with terrestrial infrastructure. Optical intersatellite links allow traffic to pass between spacecraft before reaching an appropriate ground connection. These are different segments of the communications path, and each performs a different function. Satellite availability alone is not a complete description of service.

For a remotely operated platform, the distinction between throughput and latency is practical. Throughput describes how much information can be transmitted during an interval. Latency describes how long an exchange takes. A connection can carry substantial amounts of data and still introduce delay, just as a prompt connection can have limited capacity.

Continuity adds another dimension. It describes whether the connection remains available over the required period. The October dispute involved conditions under which connected equipment could operate, making a simple comparison of advertised broadband speeds inadequate to explain it.

New Space Economy’s account of space infrastructure places user equipment, communications facilities, operations software, and terrestrial support within the same service system. Applied to Ukraine, that framework explains why access depends on an operating network and authorized service as well as functioning hardware. The terminal provides the local connection; it does not independently reproduce the satellites, gateways, management systems, or permissions behind it.

How Starlink and Starshield Differ

SpaceX presents Starshield as a government-focused offering built using its Starlink technology and launch capabilities. Its published description covers communications, Earth observation, and hosted payloads. A hosted payload is equipment carried on a spacecraft that supplies supporting functions such as power and communications.

The breadth of that description matters when interpreting references to Starshield. The name can refer to a family of government capabilities rather than one uniform subscription. SpaceX describes additional cryptographic capabilities for government missions and the integration of customer payloads. Those features concern security and system design, but a product description is not the individual agreement governing every customer’s access.

SpaceX’s government purchasing guidance makes a separate commercial distinction. It recommends Starlink for civilian government agencies and directs U.S. national-defense applications toward Starshield Communications Services. It identifies the U.S. Space Force’s Commercial Satellite Communications Office as the principal procurement route through its proliferated low-Earth-orbit contract.

The published Starlink acceptable-use policy also separates ordinary service from specially authorized applications. It prohibits remote control of aerial drones or unmanned vehicles unless SpaceX contractually permits that use. It separately restricts military activity, with an exception for approved leisure and welfare programs for military personnel. These are published commercial-service conditions, not a substitute for a particular government agreement.

A contractual permission changes the authorized use of a service without requiring the customer to own the entire network. That is why a drone application, a civilian government office, and a military welfare connection can involve related equipment but different permitted activities. The hardware’s ability to exchange information does not itself establish permission for every application.

The distinction also prevents a misleading inference from encryption. Encryption addresses how information is protected against unauthorized reading. Access rules address whether a user or application may communicate through the network. Stronger protection of data does not, by itself, identify who can approve a service change.

For Ukraine, the relevant relationship joins a government-oriented capability with a commercial operator’s technology. Understanding that arrangement requires keeping the product category, permitted application, purchasing authority, and network operation distinct. Treating the words Starlink and Starshield as interchangeable obscures those differences.

Ukraine’s Terminal Approval System

Ukraine’s February 2026 terminal-verification program provides a concrete example of shared access administration. On February 3, the Ministry of Defence explained that only registered and verified terminals would be permitted to operate under a new whitelist system. It described the measure as a response to Russian use of commercially available terminals on drones.

A whitelist, also called an allowlist, identifies equipment authorized to receive service. This reverses the assumption that every device capable of connecting should be accepted unless individually blocked. In the Ukrainian arrangement, approval became a condition of operation within the country.

Starlink’s February 4 service notice stated that the measures were coordinated with Ukraine’s defense and digital-transformation ministries. It explained that a terminal lacking government approval could not receive service in Ukraine, even if its account remained active and continued to incur charges. Account status and geographic authorization were separate administrative conditions.

The ministry’s terminal-identification instructions identified the equipment using its kit number or terminal identifier. The kit number could be found on the shipping label, and the terminal identifier through the application. Identifiers allow an approval process to refer to particular equipment rather than relying only on the identity of the person carrying it.

For military users, a February 4 ministry notice directed submission through DELTA. It also stated that service members did not have to transfer personally owned terminals onto a military unit’s balance sheet or provide account credentials. Registration could authorize the equipment without changing its ownership.

On February 5, the ministry reported that the first group of approved terminals was operating and that Russian terminals had been blocked. It said updates were being processed daily at that stage, with work continuing toward real-time submission. Those statements describe the rollout in February, rather than an assertion that the same processing schedule remained in place throughout the year.

This episode demonstrates Ukrainian participation in access decisions. Its institutions organized verification and supplied authorization information, and the network provider applied service restrictions. It is a more specific description than saying Ukraine either controlled Starlink completely or had no involvement in its operation.

The registration system also separates equipment ownership from network permission. A privately owned device could serve a military user and enter an approved list without becoming military property. Conversely, an active commercial account could fail to receive service within Ukraine if the terminal lacked the required approval. Both distinctions are directly relevant to interpreting later disputes about access.

What Government Procurement Purchases

Government procurement introduces another actor into the service relationship: the organization purchasing capability on behalf of an operational user. In a commercial subscription, the subscriber and user may be the same person. In defense assistance, the buyer, network operator, and beneficiary can be separate institutions.

The U.S. purchasing mechanism identified in SpaceX’s government guidance is an indefinite-delivery, indefinite-quantity contract. This type of arrangement establishes a framework under which agencies can place orders as requirements and funding develop. It does not mean that every listed service has already been purchased in the largest possible amount.

Space Systems Command’s September 2025 account of its proliferated low-Earth-orbit procurement described an initial 2023 award covering 16 vendors and a $900 million ceiling. The command said the ceiling subsequently increased to $13 billion and participation to 20 vendors. These were historical figures describing the purchasing vehicle, not the value of a single Ukraine agreement.

The difference between a ceiling and an expenditure is central to interpreting those numbers. A ceiling limits the aggregate value that may be ordered under the arrangement. Actual purchases depend on individual orders and their funding. Assigning the full ceiling to SpaceX, to Starshield, or to Ukraine would misstate what the command reported.

The same command account described demand aggregation across the Defense Department. Combining requirements within a common purchasing mechanism gives the government a way to arrange services for multiple customers. The mechanism also accommodates competition among participating suppliers instead of identifying a single supplier for every subsequent requirement.

This structure explains why a service’s commercial brand does not reveal its full purchasing chain. A government office can place an order, a provider can operate the network, and another military organization can use the resulting connectivity. Their responsibilities are related, but they are not identical.

New Space Economy’s discussion of satellite communications for defense customers emphasizes the operational service being purchased: mobile coverage, secure traffic paths, continuity, and managed support. In Ukraine’s case, the procurement question concerns which capabilities were ordered and which authority governs their alteration, rather than simply who paid for an antenna.

What the Congressional Inquiries Examine

On October 19, Senators Richard Blumenthal, Sheldon Whitehouse, Jeanne Shaheen, and Chris Coons sought information from SpaceX about the reported restrictions. Their letter addressed the respective operational and contractual roles of the company and the U.S. government. It also recorded Musk’s position that Starshield was controlled by the government.

Blumenthal announced a further inquiry on October 22 in his capacity as ranking member of the Senate Permanent Subcommittee on Investigations. Letters went to Defense Secretary Pete Hegseth and Musk. The announcement framed the inquiry around the restriction, the decision process, and federal reliance on the company’s communications capabilities.

The letter to the defense secretary requested dates and duration, identification of personnel involved, and an account of how any decision reached the department. It separately requested an explanation of implementation and advance notification to Ukraine. Separating authorization from implementation allows an inquiry to examine who directed a change and who carried it out.

The correspondence also addressed contractual authority to activate, restrict, geographically limit, or stop service. A geographic limitation, often called geofencing, associates permission with a defined area. It is different from a movement-speed limit, although both can determine whether a terminal operates under particular conditions.

The letter to SpaceX requested corresponding information about company personnel, communications, implementation, and contractual powers. Both October 22 letters requested written responses by November 5. That deadline identifies a documented next step in the inquiry; it is not evidence that answers had already been provided.

These documents are records of congressional requests and the senators’ stated concerns. They do not constitute a completed determination assigning responsibility. Reporting their allegations as established investigative findings would remove the distinction between initiating an inquiry and resolving it.

Their structure clarifies the control issue. The questions concern policy direction, technical execution, notice to the operational user, and rights under an agreement. A company may operate infrastructure used under government arrangements, making each of those relationships relevant to the same service event.

The inquiry addresses a communications system through both operational records and procurement records. Its subject is the relationship between the capability supplied to Ukraine and the authorities exercised over that capability, with the decision chain examined separately from the observed interruption.

How Continuity Duties Enter Defense Contracts

U.S. defense procurement already contains a framework for continuity of designated contractor services. The Defense Federal Acquisition Regulation Supplement, or DFARS, includes a clause titled Continuation of Essential Contractor Services. It concerns services supporting functions whose interruption could seriously impair defense operations.

The accompanying service-contracting policy states that the designation generally applies to identified service functions rather than automatically to an entire contract. That distinction matters for a supplier providing multiple activities. A determination that one function is essential does not necessarily give the same status to everything the company sells.

Under the policy, contractors supplying government-designated essential services provide a written continuity plan for incorporation into the contract. The contracting officer reviews the plan with a functional manager. Activation during a crisis follows the specified government authority rather than occurring solely because a customer describes its service as important.

The clause requires contractors to maintain the plan and submit updates for approval. It also provides for participation in exercises and for continued performance of identified services during a crisis when directed. If a contractor anticipates being unable to perform, the clause requires prompt notification and cooperation with government continuity efforts.

These provisions distinguish a commitment to maintain service from a guarantee that no interruption can occur. They establish responsibilities for planning, direction, performance, and communication. The existence of this general framework does not establish which provisions appear in a particular Ukraine-related Starshield agreement.

The CSIS analysis proposes additional arrangements for services supplied to allies and partners. Its suggestions include defined government review before material restrictions and congressional notification of government-directed changes, with an analogy to arms-sale notification procedures. These are the authors’ policy proposals, not a description of newly enacted requirements.

There are two different governance subjects here. Continuity provisions address performance of contracted functions during a crisis. Review and notification proposals address the decision to change an ally’s access to a service. One concerns maintaining an agreed capability; the other concerns approval of a deliberate alteration.

Keeping those subjects separate explains how procurement can specify more than throughput and coverage. It can also assign procedural duties around the service. The relevant duties arise from the applicable rules and agreements, rather than from the public-facing name of a communications product.

Ukraine’s Proposed Nationally Controlled Communications

Ukraine has also announced work on a different ownership arrangement. On October 22, ICEYE and Nokia signed a letter of intent with Ukraine’s Ministry of Defence to explore cooperation in space, particularly sovereign satellite communications. The announcement accompanied a visit by Finland’s prime minister.

The proposed relationship builds on an ICEYE-Nokia partnership announced October 1. The companies described systems in which government customers would own and control satellites, ground infrastructure, and user terminals. They identified defense, border security, emergency services, and disaster response as intended applications.

The ownership model changes what the customer buys. Purchasing connectivity supplies access to an operator’s network under an agreement. Purchasing a nationally controlled system encompasses infrastructure and operational authority over the specified components. Those are different products even if both provide broadband communications.

ICEYE and Nokia described their systems as complementing existing commercial and military networks. Their announced design focuses capacity on priority mission areas, and their October announcement identified 2028 as the expected first launch year for the broader communications partnership. The Ukrainian letter of intent is an agreement to explore cooperation, not an announcement of an already operating Ukrainian constellation.

New Space Economy’s coverage of the Ukrainian agreement connects the ownership proposal to the ground segment and terminals as well as spacecraft. That is a substantive distinction because network management and user access involve equipment and software outside orbit. A satellite alone is not the entire communications service.

Its separate examination of sovereign LEO networks explains additional commercial arrangements, including dedicated capacity and national ownership of a system. Those approaches allocate responsibility differently. Dedicated capacity can reserve a portion of a provider’s service, whereas ownership transfers specified assets and associated operating responsibilities to the customer.

Ownership also changes the financial activity involved. A service purchaser pays for agreed access and support. A system owner funds the assets and their continuing operation, whether those activities are performed internally or contracted to suppliers. The economic distinction concerns what is purchased and managed, rather than a universal ranking of one model over another.

The Ukrainian initiative addresses control through system development and ownership. It accompanies the existing use of purchased satellite services and gives a concrete example of how a government can pursue a different allocation of operational authority through its industrial partnerships.

Europe’s Public-Private Approach to Secure Connectivity

Europe’s IRIS² program illustrates another arrangement: a public-private concession for a communications system intended to serve governmental and commercial users. The European Commission signed the concession contract with SpaceRISE on December 16, 2024. The consortium includes SES, Eutelsat, and Hispasat.

The Commission’s announcement described a 12-year partnership to develop, deploy, and operate the system. The European Union would serve as an anchor customer, with public funding alongside private investment. This combines government demand and program governance with the participation of commercial operators and suppliers.

The design subsequently changed. On August 7, 2026, the EU Agency for the Space Programme reported an implementation agreement that increased the main constellation to 348 satellites: 330 in low Earth orbit and 18 in medium Earth orbit. The agency described first launches and progressive operational connectivity from 2029 as planned steps.

That update also described a dedicated additional layer of 66 satellites and projected increased governmental capacity. These are program-design and planned-capacity statements. They describe the system being developed, rather than an available replacement for every Ukrainian application.

The institutional arrangement differs from both an ordinary commercial subscription and an entirely national network purchase. Under a concession, responsibilities for development and operation are specified through a longer-term agreement. An anchor customer provides a substantial initial demand base around which infrastructure and commercial services can be organized.

This comparison makes the meaning of sovereignty more precise. A government can influence a communications service through ownership, procurement rights, reserved capacity, program governance, or a combination of those arrangements. These forms of control concern different assets and decisions and do not reduce to the nationality of the company supplying hardware.

For Ukraine’s access question, the relevant connection is the allocation of authority. The ICEYE-Nokia proposal describes customer ownership across a system, and IRIS² describes a European institutional partnership with commercial operators. Starshield procurement describes government-oriented services supplied using SpaceX capabilities. Each arrangement connects the user to infrastructure through a different set of operational and contractual relationships.

Summary

Ukraine’s Starlink access is administered through several distinct relationships. The terminal-verification program documents Ukrainian government approval working with SpaceX network authorization. Government purchasing arrangements add a buyer whose contractual rights are separate from the user’s possession of equipment. The October disruption brought the authority to alter an agreed service into congressional scrutiny.

The documented sequence includes the reported movement-speed restriction, the October inquiries, and Ukraine’s October 24 restoration notice. It also includes development initiatives with different ownership structures. These are separate events with different purposes: restoring an existing connection, investigating a decision, and exploring future infrastructure.

The question of control is consequently answered by identifying the particular function. Equipment ownership, network operation, user authorization, procurement, and policy direction each describe a different power. The announced congressional inquiry is examining how those powers were exercised in October, with written responses requested by November 5.

Appendix: Top Questions Answered in This Article

Who Controls Ukraine’s Starlink Access?

Control involves several functions rather than a single relationship. SpaceX operates the network, Ukrainian authorities participate in terminal authorization, and government purchasers establish service arrangements. The October congressional inquiries specifically address who held and exercised authority to change the affected military service.

What Did the October Movement Restriction Affect?

Ukrainian officials reported that terminals on platforms moving above 100 miles per hour were losing connectivity. This concerned the physical movement of connected equipment, not broadband download speed. The reported condition affected drone applications and should not be described as evidence that every Ukrainian Starlink connection stopped working.

When Did Ukraine Report Restored Service?

Ukraine’s Ministry of Defence published its restoration notice on October 24, 2026. It reported stable connectivity at movement speeds exceeding 400 kilometers per hour. The statement described observations from ministry monitoring systems and identified the restored capability as relevant to drones, logistics, and communications.

How Does Starshield Differ From Starlink?

SpaceX describes Starlink as a consumer and commercial service and Starshield as a government-focused offering. Starshield includes communications, Earth observation, and hosted-payload activities, with additional security capabilities. The applicable government agreement determines the purchased service; the product name alone does not specify every customer’s rights.

What Is Ukraine’s Terminal Allowlist?

The allowlist identifies terminals approved to receive service in Ukraine. The February 2026 program combined Ukrainian government verification with network authorization implemented through cooperation with SpaceX. Approval concerned particular equipment, and the published military registration instructions did not require service members to surrender ownership of personally held terminals.

Does a $13 Billion Contract Ceiling Represent Spending on Ukraine?

No. Space Systems Command described that figure as the ceiling of a purchasing arrangement involving multiple vendors. A ceiling establishes the maximum potential ordering value under the arrangement. It is not evidence that the entire amount was spent, awarded to SpaceX, or allocated to Ukraine.

What Are the Congressional Inquiries Examining?

The October correspondence requested information about the restrictions’ timing, authorization, implementation, contractual basis, and notification to Ukraine. Separate letters addressed SpaceX and the Defense Department. These requests are investigative steps, not completed findings establishing which individual or organization directed the service change.

What Do Essential-Service Contract Provisions Cover?

The DFARS framework covers designated contractor functions supporting mission-essential activities. It provides for continuity planning, government direction during crises, performance responsibilities, and notification when a contractor anticipates being unable to perform. Its general existence does not establish which clauses govern a particular Starshield agreement.

What Did Ukraine Announce With ICEYE and Nokia?

The parties signed an October 22 letter of intent to explore cooperation, particularly sovereign satellite communications. The companies’ broader partnership proposes customer ownership and control of satellites, ground infrastructure, and terminals. The Ukrainian announcement describes intended cooperation rather than delivery of an operating national constellation.

How Does IRIS² Approach Government Control?

IRIS² combines European institutional governance and demand with commercial operators through a public-private concession. Its August 2026 implementation update described a planned main constellation of 348 satellites. The arrangement differs from a standard subscription because development, deployment, and operation form part of a longer-term program agreement.

Appendix: Glossary of Key Terms

Latency

The time taken for information to travel through a communications system. Internet measurements often describe the round-trip delay between sending a request and receiving a response. Satellite distance, routing, processing, and network congestion can all contribute to that delay.

Gateway

A ground facility that connects satellite communications with terrestrial networks. It receives or transmits traffic between space and Earth and connects that traffic to onward systems. A user’s complete connection can involve gateways, terrestrial telecommunications, and additional network facilities.

Throughput

The amount of information successfully transferred during a given period, commonly expressed in bits per second. Throughput differs from latency, which measures delay. A communications service can offer substantial transfer capacity but still introduce delays affecting interactive applications.

Hosted Payload

Equipment carried on a spacecraft that provides supporting resources such as electrical power, communications, and physical accommodation. The payload performs its particular mission using those shared resources. Its ownership or operating arrangements can differ from those of the spacecraft carrying it.

Encryption

A method of transforming information so that it cannot readily be read without the appropriate cryptographic key. Encryption protects the content of communications. It is separate from authorization, which determines whether a user or application is permitted to access a service.

Allowlist

A list identifying users, accounts, or devices permitted to access a system. Equipment absent from the list can be denied service even if technically capable of connecting. Ukraine’s terminal-verification program used this approach to distinguish authorized equipment from other terminals.

Indefinite-Delivery, Indefinite-Quantity Contract

A purchasing arrangement used when the exact timing or quantity of future orders is not fully established at the outset. It creates a framework for subsequent orders within defined limits. Its maximum value is distinct from the amount actually ordered or spent.

Geofencing

The application of a rule based on a defined geographic area. In communications, it can determine where equipment is authorized to receive service. A geographic restriction differs from a rule based on movement speed, although both can affect connection availability.

Anchor Customer

A substantial early customer whose expected demand supports development or operation of a product or infrastructure system. In satellite communications, a government can serve this role through contracted service purchases. Being an anchor customer does not automatically mean owning every asset.