Starlink asks every satellite operator to share maneuvers ahead of time
Starlink is encouraging every satellite operator to share maneuvers ahead of time, citing around 164,000 near-miss events in six months. It calls Stargaze free to all operators, though DatacenterDynamics describes the map behind it as proprietary.
The Product Desk
Starlink figures: an unannounced maneuver would have brought Starlink-32710 within 57 meters; an unnamed satellite passed within 134 meters of Starlink-2140, CDMs arriving 30 minutes before; around 164,000 near misses in six months came within four hours of an unannounced maneuver.
- 57 meters, within Starlink-32710's projected pass, unannounced maneuver, claim 9
- 134 meters, within Unnamed satellite's pass by Starlink-2140, August, claim 10 CDMs came 30 minutes before approach
- around 164,000 events Near misses within four hours of unannounced maneuvers, claim 8 last six months, as Starlink reports
| Figure | Value | Note | Claim |
|---|---|---|---|
| Starlink-32710's projected pass, unannounced maneuver | 57 meters, within | 9 | |
| Unnamed satellite's pass by Starlink-2140, August | 134 meters, within | CDMs came 30 minutes before approach | 10 |
| Near misses within four hours of unannounced maneuvers | 164,000 events, around | last six months, as Starlink reports | 8 |
What happened
- Stargaze was announced in February and now also goes by Space-Safety.com; Starlink published more detail about it in early October.
- Stargaze draws on 31,000 star trackers aboard Starlink's satellites and merges that data with radar and optical trackers run by specialist space data platforms.
- Starlink says its constellation met 650 unique third-party satellites in conjunctions in 2026, and only half of those satellites had shared ephemeris.
- On October 1, Starlink-32710 saw an unannounced maneuver that would have put it within 57 meters, then analyzed a new trajectory through Space-Safety.com in under an hour before burning to restore 1 km.
Why it matters
- Who's exposed exposure Maneuver plans sent to Stargaze reach a company that flies its own constellation and that DatacenterDynamics describes as very close to the Pentagon.
- What doesn't add up contradiction Starlink says it shares its own ephemeris publicly, but DatacenterDynamics describes those as registration-gated American databases that reserve the right to exclude users over security concerns.
- What it limits constraint Governments mostly keep their satellites' positions private and no global master system exists, so DatacenterDynamics says Starlink is claiming the coordinating role for itself.
A conjunction message that arrives 30 minutes before closest approach leaves little to do. In its October 6 presentation, Starlink said that was the warning Starlink-2140 received in August, and the satellite could only slew its chassis and solar arrays to a lower profile while an unnamed satellite passed within 134 meters [10]. Starlink insists the near miss could have been prevented if the other operator had told it what it planned to do that day [10].
The written request goes to every operator. "Not sharing satellite maneuvers ahead of time can result in dangerous close approaches that would otherwise have been easy to avoid," Starlink said in a statement [2]. It went on: "As the population of satellites in LEO continues to grow, we encourage every operator to adopt similar practices to prioritize the sharing of information and space safety" [3]. DatacenterDynamics frames this as an encouragement to share data with Stargaze [13].
Starlink pitches the exchange as shared safety, but according to DatacenterDynamics an operator appears to get back conjunction data messages, the texts warning that a satellite may be about to hit something, without full access to the database [17].
The case for sharing rests on counts. Of the third-party satellites Starlink met in conjunctions, roughly 325 did not share ephemeris [14]. The six-month near-miss tally works out to about 27,000 events a month [15]. Starlink defines each event by timing: the time of closest approach fell within four hours of an unannounced maneuver [8].
When it comes to its own data, Starlink shares selectively. Michael Nicolls, senior vice president of Starlink at SpaceX and xAI, said at the International Astronautical Congress in Antalya, Turkey, on October 6 that Starlink had begun sharing data with some Chinese satellite operators, but "there are many that we do not [share with]" [5].
We think an operator that maneuvers should publish its burn plans ahead of time to somebody. Where they go is a separate decision, and sending them to Stargaze means feeding a map whose full contents participants do not receive [17].
To see where your own operation falls, answer two questions. First: can you publish a burn plan more than four hours ahead? Starlink's count looks at closest approaches within four hours of an unannounced maneuver, so four hours is a workable dividing line [8]. Second: does what comes back include data you can inspect, or only warnings?
- Over four hours ahead, inspectable data back: share. - Over four hours ahead, warnings only: share, but get the exclusion and data-handling terms before you send anything. - Under four hours ahead, inspectable data back: share what you have. The return partly covers your short lead time. - Under four hours ahead, warnings only: shorten your own planning lead time first.
On DatacenterDynamics's reading of Stargaze, participants sit in the warnings-only rows [17].
What to watch
- Whether Starlink publishes the Space-Safety.com participation terms, including what exclusion rights it keeps.
- Whether the share of third-party satellites with shared ephemeris moves above the half Starlink reported for 2026.
- Whether Starlink releases miss distances for the 164,000 events it counted by timing.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence35
- Adoption
- Not scored
- Hype gap+30
- Incentives60
- Confidence50
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
In early October, Starlink released more information about its Stargaze situational awareness data project, which aims to share satellite pathing information 'free to all satellite operators.'
- [2]
Starlink's statement reads: 'Not sharing satellite maneuvers ahead of time can result in dangerous close approaches that would otherwise have been easy to avoid.'
- [3]
Starlink's statement continues: 'As the population of satellites in LEO continues to grow, we encourage every operator to adopt similar practices to prioritize the sharing of information and space safety.'
- [4]
DatacenterDynamics writes that virtually all governments prefer their nation's satellite positions to stay as private as possible, that no globally accessible master system exists as it does for ships or planes, and that Starlink is now claiming that responsibility.
- [5]
At the International Astronautical Congress in Antalya, Turkey, on October 6, Michael Nicolls, senior vice president of Starlink at SpaceX and xAI, said Starlink had begun to share data with some Chinese satellite operators, but specified 'there are many that we do not [share with].'
- [6]
Stargaze collects information from 31,000 star trackers in the 11,000+ satellite fleet and merges it with radar and optical satellite trackers from observatories on Earth managed by specialist space data platforms.
- [7]
In 2026, Starlink reports its constellation encountered conjunctions with 650 'unique third-party satellites,' only half of which shared ephemeris.
- [8]
Starlink reports around 164,000 near-miss events in the last six months, where the time of closest approach happened within four hours of an unannounced maneuver.
- [9]
In its October 6 presentation Starlink said Starlink-32710 saw an unannounced maneuver by 'an object' on October 1 that would bring it within 57 meters, analyzed a new trajectory through Space-Safety.com in less than an hour, and planned and executed a collision avoidance burn to restore a 1 km distance.
- [10]
In its October 6 presentation Starlink said Starlink-2140 had insufficient lead time for a near miss in August: CDMs arrived 30 minutes before close approach, so the satellite could only slew its chassis and solar arrays to a lower profile as an unnamed satellite passed within 134 meters. Starlink insists this could have been prevented had the other operator told it its plans.
- [11]
DatacenterDynamics describes Starlink as very close to the Pentagon.
- [12]
Stargaze was announced in February and is now also referred to as Space-Safety.com; Starlink published more information about it in early October.
- [13]
DatacenterDynamics headlines its report that Starlink encourages every satellite operator to share data with the Stargaze platform, for safety.
- [14]
Roughly 325 of the 650 third-party satellites Starlink met in conjunctions in 2026 did not share ephemeris (the source says 'only half' shared).
- [15]
Around 164,000 near-miss events in six months is about 27,000 a month.
- [16]
DatacenterDynamics writes that it appears Stargaze will compile a proprietary map of all satellites, informed by Starlink situational awareness technologies, participating operators that share their data, and space intelligence providers.
- [17]
DatacenterDynamics writes that the sharing, conditional on an operator's participation, appears to mean getting conjunction data messages (CDMs) that a satellite might be about to crash into something, rather than full access to the database.
- [18]
Starlink has started stating that it shares all its ephemeris (satellite trajectory and maneuver data) 'publicly.'
- [19]
DatacenterDynamics writes that Starlink's 'public' ephemeris sharing seems to mean data sent to proprietary American databases that users must register with to access and that reserve the right to exclude access in the case of security concerns.
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
1 independent publisher whose own reporting we read for this story.
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.
Topics
- Space Traffic ManagementFollow
- Space Situational AwarenessFollow
- Satellite ConstellationsFollow