A Russian Satellite’s Uninvited Approach to a Commercial Radar Satellite Exposes a Gap in Space Rules

Between Oct. 15 and Oct. 19, 2026, the Russian military satellite Kosmos 2612 closed from hundreds of kilometers away to within roughly 500 meters of ICEYE-X36, and probably closer. ICEYE-X36 is a commercial radar satellite owned by ICEYE US, the American subsidiary of the Finnish company ICEYE. That is the account of the space-tracking company LeoLabs, which followed the event with its own radars and said repeated maneuvers and difficult tracking geometry make the exact separation uncertain [1][2][3][21].

Satellites pass near each other every day, usually by chance and at high relative speed. LeoLabs instead described a controlled approach, close-proximity loitering and a controlled departure, “consistent with sophisticated rendezvous and proximity operations (RPO).” Adam Marsh, LeoLabs’ vice president for technical solutions, said it was the first time the company had seen such an operation in low Earth orbit carried out without consent [2]. STC has written about disrupting a constellation locally [16] and verifying what states put in orbit [17]; this is a concrete case of both.

Within a week, the departure looked more like a pause. As of Oct. 24, Kosmos 2612 had stopped drifting away and was holding in ICEYE-X36’s orbit, hundreds of kilometers behind it [7][31]. The analysis firm Integrity ISR said on Oct. 23 that two of its sibling satellites would soon line up with the orbit of a second ICEYE satellite [32]. The public orbital data show why that matters: the expensive part of this campaign has already been paid for.

What happened, and when

Kosmos 2612 is one of six Russian military satellites, Kosmos 2609 through 2614, launched together from Plesetsk on April 16, 2026; ICEYE-X36 was launched in March 2024 [9].

In May, according to the U.S. Space Force, Russia “executed fuel-intensive orbital maneuvers to position four military satellites (Cosmos 2610 through 2613) close to a Western commercial radar satellite used by Ukraine for imagery intelligence” [10]. The Center for Strategic and International Studies (CSIS), working from commercial tracking data, tied that activity to the satellite Kosmos 2612 approached in October [6].

Starting on Sept. 30, Kosmos 2612 made a series of maneuvers that, CSIS wrote, “brought it back into coplanar alignment and placed it at nearly the same altitude as the commercial satellite” [6].

LeoLabs’ account, released Oct. 19, runs as follows:

• On Oct. 15, Kosmos 2612 began closing quickly from a separation of hundreds of kilometers.
• By Oct. 16 it was holding station 2 to 3 km from ICEYE-X36.
• Over the following days it repositioned ahead of and behind the satellite, making small adjustments to hold a close relative position.
• At times the two objects were difficult for LeoLabs’ radars to tell apart.
• Kosmos 2612 then moved away, and the close-proximity activity ended [1][2][3][4].

Marsh told Ars Technica the two were within 500 meters over the weekend of Oct. 17-18, and “likely quite a bit closer than that” [2].

The departure took more than one burn. Around 01:52 UTC on Oct. 18, near the closest approach, the Dutch satellite tracker Marco Langbroek saw signs of a small maneuver in public orbital elements [36]. The tracking site KeepTrack describes a burn of “a fraction of a meter per second” that “started a slow backward drift,” leaving Kosmos 2612 about 150 meters higher and 5.1 km behind by 07:38 UTC [23], a drift of roughly 20 km a day by STC’s arithmetic. At about 12:26 UTC (12:30 by the space-tracking firm COMSPOC’s timing), a burn of about 1.3 m/s raised its orbit about 2.3 km, KeepTrack estimates. That widened the gap with ICEYE-X36 at roughly 350 km a day, to 292 km by 07:32 UTC on Oct. 19 [7][23][31]. KeepTrack calls this the departure burn; COMSPOC says Kosmos 2612 “burned away” then [23][31]. LeoLabs said it “has drifted away from ICEYE-X36 since October 18” [25].

Marsh told Ars Technica that as of Oct. 19 the two were separating at about 17 km/h (10 mph), under 5 m/s, a relative speed rather than the size of a burn [2]. The New York Times, citing LeoLabs data, gave about 10 miles an hour [22]. During the closest passes, COMSPOC put the relative speed at 0.15 to 0.9 m/s, “walking pace or slower.” ICEYE-X36 did not maneuver, COMSPOC said [31].

The orbital mechanics of a quiet approach

The expensive part of such an approach is matching the orbital plane, not closing the distance. At about 550 km altitude, tilting an orbit by one degree costs about 130 m/s of velocity change, a large share of a small satellite’s propellant. KeepTrack estimates Kosmos 2612’s May plane change at about 117 m/s, cheaper than it might have been because the satellite was launched into a plane that drifted toward ICEYE-X36’s on its own [23]. Both satellites fly near-sun-synchronous orbits inclined about 97.85 degrees [9], roughly 0.3 degree above the exactly sun-synchronous value for their altitude, by STC’s calculation. Once two satellites share a plane and an altitude, Earth’s oblateness turns both planes at the same rate, so they stay aligned almost for free.

Closing along the orbit is cheap. A satellite in a slightly lower orbit circles the Earth slightly faster: each kilometer of altitude difference opens or closes roughly 9 km of separation per orbit, more than 100 km a day. On Oct. 15 a burn of under 2 m/s dropped Kosmos 2612 2.3 km lower, and the gap shrank from about 425 km to 35 km in a little over a day; on Oct. 16 a matching burn stopped it about 3 km behind [23]. COMSPOC counts seven small burns totaling about 5 m/s between Oct. 13 and 16 [31].

The cost of doing it again

On top of the 117 m/s plane change, KeepTrack estimates Kosmos 2612 has spent about 60 m/s since Sept. 30 [23]. Late on Oct. 19 it maneuvered back to ICEYE-X36’s altitude, which Langbroek said “could suggest” it is not done with the satellite; COMSPOC reported on Oct. 24 that it had braked that day and was then holding position in the same orbit [7][31].

Langbroek put the gap at about 480 km on Oct. 21, as did COMSPOC on Oct. 24 [7][31]. Defense News, citing Greg Gillinger of Integrity ISR, reported it holding roughly 400 km behind on Oct. 21 [32]. None has explained the difference, and all describe the same geometry: same altitude, same plane, a steady gap. Gillinger said Russia could “easily close that gap again at the time and place of their choosing” [32]. The numbers support him. Repeating the Oct. 15-16 sequence would bring Kosmos 2612 back within a few kilometers in a little over a day, for under 4 m/s, about 2 percent of what it has already spent (STC estimate from KeepTrack’s figures [23]).

The pattern may be spreading, though public data does not yet show it. Gillinger has told readers to “watch Cosmos 2611 and 2613, whose planes are converging on ICEYE X37’s,” ICEYE-X36’s launch sibling [23][32]. KeepTrack’s archive puts those plane alignments around Nov. 5 for Kosmos 2613 and Nov. 13 for Kosmos 2611; they are orbital-plane crossings, not close passes, and as of Nov. 2 KeepTrack showed no pass within 4,000 km through Dec. 3 unless the satellites maneuver [23].

A crossing is not a rendezvous. Between May and September, Kosmos 2613 passed within about 4 km of ICEYE-X36 three times; KeepTrack attributes two of those passes to the natural cycle and the July one to a 6 km orbit raise [23]. What set Kosmos 2612 apart was the Oct. 12 burn that put it 0.2 km below its target’s orbit with matching eccentricity, and the burns that then held it close [23]. So the signal to watch for around those Nov. 5 and Nov. 13 alignment windows is a step in Kosmos 2611’s or 2613’s altitude that matches ICEYE-X37’s, or a drop of a few kilometers by Kosmos 2612, which would start it closing on ICEYE-X36 at hundreds of kilometers a day. In October, KeepTrack notes, every step of the campaign appeared in public element sets days before the closest pass [23].

What a close look can and cannot reveal

At a few hundred meters, a 10 cm camera aperture could in principle resolve features a few millimeters across; in practice, enough to show antennas, solar panels and deployable structures. Loitering near a radar satellite could also reveal its emissions and operating schedule. LeoLabs said the behavior demonstrated capabilities that “could support intelligence collection, on-orbit inspection, coercive signaling, interference, or preparation for future counterspace operations,” but “do not establish hostile intent” [3]. CSIS argued that policymakers should assume Kosmos 2612 could threaten the commercial satellite, given Russia’s record of testing on-orbit weapons [6]. ICEYE has agreements to supply Ukraine’s military but has not said which satellites serve which customers [3][5][32].

Why the distance itself is uncertain

Estimates from commercial tracking data range from COMSPOC’s roughly 60 meters (uncertainty up to about 950 meters), posted on X on Oct. 24 [31], to LeoLabs’ roughly 500 meters, likely closer [3]. COMSPOC’s solution has three close passes: about 220 meters on Oct. 16, 60 meters on Oct. 17 and 260 meters early on Oct. 18 [31]. The astrophysicist Jonathan McDowell, sharing it, noted COMSPOC has “access to tracking data I don’t” [37]. An image from the commercial imaging company Vantor, first published by Axios on Oct. 22, shows the two less than a mile apart on Oct. 17 [33]; Ars Technica, which also ran the image, put the gap at about 1 km [26].

Two-line element sets (TLEs), the public orbital data most amateur and open-source trackers use, are coarser. Langbroek cautioned that one of his own computed separations was “within TLE uncertainty, could be up to 1-2 km” [8]. KeepTrack’s reconstruction from about 3,200 archived sets put the closest approach between about 150 and 650 meters early on Oct. 18 UTC, “and no tighter figure.” That pass fell in a gap with no published Kosmos 2612 element sets, from 17:18 UTC on Oct. 17 to 07:38 UTC on Oct. 18, and Kosmos 2612 maneuvered during it [23]. The analyses also disagree on timing: COMSPOC’s closest pass falls on the afternoon of Oct. 17, when KeepTrack’s element sets place Kosmos 2612 between 2.1 and 0.85 km behind [23][31].

Much smaller figures have circulated. Orbital Radar’s automated screening predicted about 26 meters for 16:07 UTC on Oct. 19, after Kosmos 2612 had left, and as of Oct. 21 marked it “not re-confirmed” [23][24]. Reports of an approach within meters, such as Meduza’s Oct. 25 headline that the satellite may have come closer than 30 meters, trace to Langbroek’s public-data estimates, which Meduza gave as 26 to 470 meters [35]. Langbroek has said such nominal values ignore uncertainty and that “values like ’26 meter’ quoted by some have very little real value” [34].

For a commercial operator, all this means learning of an approach late and imprecisely, from an approacher that shares no planned trajectory: the worst case for deciding whether to maneuver.

What a commercial operator can actually do

ICEYE US said: “We are aware of the situation and tracking it closely. Our constellation architecture is designed for continuity and resilience” [2][4]. In a constellation of dozens, losing one satellite would have little effect on ICEYE’s capacity, Ars noted [2]. Maneuvering away is possible but limited: small satellites carry little propellant, every burn shortens their life, and a pursuer with more propellant can follow. ICEYE’s chief executive, Rafal Modrzewski, told Reuters that after May the company moved its satellite and further Russian maneuvers followed [11].

Insurance may help less than hoped. Lloyd’s requires war-peril exclusions unless a syndicate has express agreement to write such cover [20], one Chinese satellite policy excludes hostile government acts and anti-satellite devices [15], and a U.S. broker describes deliberate-interference cover as an optional specialist line [19].

The norms gap

No international agreement sets how close one satellite may come to another or requires the target’s consent. Writing in the Air University journal Æther in 2022, researchers from CSIS, MIT and Secure World Foundation pointed to the “lack of existing norms or international agreements on common standards and practices for conducting RPOs,” and noted that under the Outer Space Treaty, states “cannot prevent another country from approaching their satellite(s)” [38]. The Outer Space Treaty’s obligations are general: states must act with “due regard” to others’ interests, consult before activities they believe could cause “potentially harmful interference,” and authorize and continually supervise their companies’ activities [12]. Secure World Foundation’s Victoria Samson noted that the United States is ICEYE-X36’s launching state and asked why Washington was silent [1].

That changed on Oct. 21 at the UN General Assembly’s First Committee, in what Ars Technica called the first U.S. government comments on the event [26]. The U.S. representative said Kosmos 2612 “exhibited threatening behavior by intentionally maneuvering dangerously close to a commercial satellite,” and that its actions appeared consistent with an on-orbit weapons operation, according to the UN summary [28]. Ars identified the speaker as Brian Hardesty, a State Department official; RFE/RL described him as an adviser to the U.S. delegation to the Conference on Disarmament. Both quoted him: “The decision to conduct these activities was deliberately reckless” [26][27]. Under Secretary of State Thomas DiNanno echoed him on X [29].

Jessup Taylor, the U.S. deputy permanent representative to the Conference on Disarmament, said Russia had not explained why its satellite “moved within tens of meters” of the commercial one, Ars reported, paraphrasing him as suggesting it may have closed to within about 100 feet [26]. That official claim has not been independently confirmed.

Russian delegate Konstantin Vorontsov called the concerns “unfounded” and said Russian space activity, including Kosmos 2612’s, is “purely peaceful in character,” Ars reported [26]. RFE/RL reported that the Russian representative did not directly address the accusation, and the Foreign Ministry’s published text of Vorontsov’s reply does not mention the satellite [27][30].

The main multilateral forum, the UN open-ended working group on preventing an arms race in outer space, is scheduled to hold its fourth session Nov. 23-27 in Geneva [13]. Proposals so far are not in force: voluntary U.S. norms restated in July, including “safe separation and safe trajectory” [14], and Secure World Foundation’s suggested commitment “to refrain from non-consensual and uncoordinated rendezvous and close-proximity operations” [18]. Russia and China back a legally binding treaty banning weapons of any kind in space [30], proposals the U.S. representative called unverifiable and hypocritical [28].

What is established is narrow: an uninvited, multi-day approach to within a few hundred meters or less, then a controlled departure. Washington calls it consistent with an on-orbit weapons operation; Moscow calls it peaceful. LeoLabs said on Oct. 20 that it was possible the spacecraft “will resume its RPO activity — or another one will” [25]. Kosmos 2613’s orbital plane lines up with ICEYE-X37’s around Nov. 5, and Kosmos 2611’s around Nov. 13 — alignments rather than close passes [23]. After that Nov. 5 window, the next dates to watch are around Nov. 13 and Nov. 23, when the working group meets [13].

Sources

1. Theresa Hitchens, “Russian satellite stalked ICEYE spacecraft in potentially dangerous on-orbit maneuvers,” Breaking Defense, Oct. 19, 2026. https://breakingdefense.com/2026/10/russian-satellite-stalked-iceye-spacecraft-in-potentially-dangerous-on-orbit-maneuvers/
2. Stephen Clark, “Russian spacecraft maneuvers in ‘extreme proximity’ to satellite used by Ukraine,” Ars Technica, Oct. 19, 2026. https://arstechnica.com/space/2026/10/russian-spacecraft-maneuvers-in-extreme-proximity-to-satellite-used-by-ukraine/
3. Jackie Wattles, “Russian satellite makes possibly unprecedented approach to another spacecraft without permission,” CNN, Oct. 19, 2026. https://www.cnn.com/2026/10/19/science/russian-satellite-iceye-x36-approach
4. Rachel Jewett, “Russian Satellite Maneuvered Within ‘Extreme Proximity’ of Iceye Satellite, LeoLabs Reports,” Via Satellite, Oct. 19, 2026. https://www.satellitetoday.com/government-military/2026/10/19/russian-satellite-maneuvered-within-extreme-proximity-of-iceye-satellite-leolabs-reports/
5. Thomas Novelly, “Russian space satellite approaches U.S. satellite, raising alarms about intent,” Axios, Oct. 17, 2026. https://www.axios.com/2026/10/17/russia-ukraine-satellite-space
6. Clayton Swope and Chantal Li, “Could Russia Be Poised to Use an On-Orbit Weapon Against a Commercial Satellite?,” CSIS, Oct. 15, 2026 (page last modified Oct. 19, 2026). https://www.csis.org/analysis/could-russia-be-poised-use-orbit-weapon-against-commercial-satellite
7. Marco Langbroek, “KOSMOS 2612 and ICEYE-X36: a worrisome cat-and-mouse-game in Space,” SatTrackCam Leiden, Oct. 17, 2026, updated Oct. 18, 19 and 21. https://sattrackcam.blogspot.com/2026/10/kosmos-2612-and-iceye-x36-worrisome-cat.html
8. Marco Langbroek, “Re: Cosmos-2612 closing in on ICEYE-X36,” SeeSat-L mailing list, Oct. 18, 2026. https://www.satobs.org/seesat/Oct-2026/0065.html
9. CelesTrak SATCAT records for COSMOS 2612 (NORAD 68762) and ICEYE-X36 (NORAD 59103). https://celestrak.org/satcat/records.php?CATNR=68762 and https://celestrak.org/satcat/records.php?CATNR=59103
10. U.S. Space Force, “Space Threat Fact Sheet” (current as of July 2026). https://www.spaceforce.mil/About-Us/Fact-Sheets/Article/4297159/space-threat-fact-sheet/
11. Cassell Bryan-Low and John Irish, “Russian satellite activity raises concerns for Starlink, German space commander says,” Reuters, Oct. 9, 2026 (as republished by The Star). https://www.thestar.com.my/news/world/2026/10/09/russian-satellite-activity-raises-concerns-for-starlink-german-space-commander-says
12. Treaty on Principles Governing the Activities of States in the Exploration and Use of Outer Space (Outer Space Treaty), Articles VI and IX, UNOOSA. https://www.unoosa.org/oosa/en/ourwork/spacelaw/treaties/outerspacetreaty.html
13. UNODA, “Open-ended Working Group on Prevention of an Arms Race in Outer Space (2025).” https://meetings.unoda.org/meeting/74867
14. U.S. Mission Geneva, “U.S. Statement to the Open-ended Working Group on Prevention of an Arms Race in Outer Space,” July 6, 2026. https://geneva.usmission.gov/2026/07/06/u-s-statement-to-the-open-ended-working-group-on-prevention-of-an-arms-race-in-outer-space/
15. China United Property Insurance, satellite launch and initial operation insurance clauses (policy wording, in Chinese). https://property.cic.cn/u/cms/zhcaixian/202101/29143139ngc0.pdf
16. STC, “Countering Starlink: Strategies for Disruption,” Aug. 17, 2026. https://spacetechchronicles.com/starlink-counterspace-vulnerability-boomerang/
17. STC, “Innovative Methods for Outer Space Treaty Verification,” Aug. 9, 2026. https://spacetechchronicles.com/cosmic-protons-nuclear-warheads-in-orbit-verification/
18. Secure World Foundation, “July 2026 — Statement to the Open-ended Working Group on the Prevention of an Arms Race in Outer Space in All its Aspects.” https://www.swfound.org/publications-and-reports/july-2026-oewg-swf-statement-paros-tcbm
19. RiskCube, “Commercial Space Insurance” (industry overview). https://riskcube.com/industry/space/
20. Lloyd’s, “War & NCBR Exposures,” Lloyd’s Requirements of the Council: Performance Management. https://www.lloyds.com/market-resources/requirements-and-standards/lloyds-requirements-of-the-council/operating-at-lloyds/performance-management/wr-nbbr-exposures
21. Joseph Trevithick and Howard Altman, “Russian Satellite’s Unprecedented Shadowing Of A Very Particular Radar Imaging Satellite Is A Big Deal,” The War Zone, Oct. 19, 2026. https://www.twz.com/news-features/russias-satellite-unprecedented-shadowing-of-a-very-particular-radar-imaging-satellite-is-a-big-deal
22. Kenneth Chang, “Russian Satellite Makes a Menacing Approach to Another Craft in Orbit,” The New York Times, Oct. 19, 2026. https://www.nytimes.com/2026/10/19/science/russia-satellite-kosmos-2612.html
23. Theodore Kruczek, “How Cosmos 2612 Ran Down ICEYE-X36,” KeepTrack, Oct. 19, 2026, updated Oct. 23, 2026 (corrections dated Oct. 26 and Nov. 3, 2026). https://keeptrack.space/deep-dive/cosmos-2612-iceye-x36-rendezvous
24. Orbital Radar, “COSMOS 2612 / ICEYE-X36” close-approach page (automated screening; accessed Oct. 21, 2026). https://orbitalradar.com/conjunction/59103-68762
25. LeoLabs (@LeoLabs_Space), post on X, Oct. 20, 2026. https://x.com/LeoLabs_Space/status/2112650568133190078
26. Stephen Clark, “US official: Russia’s stalker satellite sure looks like an orbital weapon,” Ars Technica, Oct. 22, 2026. https://arstechnica.com/space/2026/10/russia-claims-its-stalker-satellite-is-purely-peaceful-in-character/
27. Mike Eckel, “US Accuses Russia Of ‘Deliberately Reckless’ Move With Military Satellite Flyby,” RFE/RL, Oct. 22, 2026. https://www.rferl.org/a/russia-us-satellite-accusation-intelligence-threat/33881569.html
28. UN Meetings Coverage, “First Committee Debates Pathways to Prevent Weaponization of Outer Space,” GA/DIS/3774, Oct. 21, 2026. https://press.un.org/en/2026/gadis3774.doc.htm
29. Under Secretary of State Thomas G. DiNanno (@UnderSecT), post on X, Oct. 21, 2026. https://x.com/UnderSecT/status/2112955751409025476
30. Russian Ministry of Foreign Affairs, statement by Konstantin Vorontsov in exercise of the right of reply, thematic discussion on outer space, First Committee, New York, Oct. 21, 2026 (in Russian). https://www.mid.ru/ru/foreign_policy/news/2156592/
31. COMSPOC (@COMSPOC_OPS), “COSMOS 2612 (SSC.68762) walks up to ICEYE-X36 (SSC.59103),” post on X, Oct. 24, 2026. https://x.com/COMSPOC_OPS/status/2114105397481177191
32. Katie Livingstone, “‘The West can’t stop me’: Space wars heat up as Russia tails a Ukraine-linked US satellite,” Defense News, Oct. 23, 2026. https://www.defensenews.com/space/2026/10/23/the-west-cant-stop-me-space-wars-heat-up-as-russia-tails-a-ukraine-linked-us-satellite/
33. Thomas Novelly, “Exclusive: New image shows Russian approach of U.S. satellite,” Axios, Oct. 22, 2026. https://www.axios.com/2026/10/22/space-weapons-russia-iceye-satellites
34. Marco Langbroek (@Marco_Langbroek), post on X, Oct. 19, 2026. https://x.com/Marco_Langbroek/status/2112292647238853110
35. “Кремль обостряет звездные войны с Западом: российский спутник, возможно, подлетел к финско-американскому аппарату на орбите ближе чем на 30 метров” (“The Kremlin escalates star wars with the West: a Russian satellite may have come closer than 30 meters to a Finnish-American spacecraft in orbit”), Meduza, Oct. 25, 2026 (in Russian). https://meduza.io/feature/2026/10/25/kreml-obostryaet-zvezdnye-voyny-s-zapadom-rossiyskiy-sputnik-vozmozhno-podletel-k-finsko-amerikanskomu-apparatu-na-orbite-blizhe-chem-30-metrov
36. Marco Langbroek, “Re: Cosmos-2612 closing in on ICEYE-X36,” SeeSat-L mailing list, Oct. 18, 2026 (14:03 UTC update). https://www.satobs.org/seesat/Oct-2026/0068.html
37. Jonathan McDowell (@planet4589), post on X quoting COMSPOC, Oct. 24, 2026. https://x.com/planet4589/status/2114106168691798229
38. Kaitlyn Johnson, Thomas G. Roberts and Brian Weeden, “Mitigating Noncooperative RPOs in Geosynchronous Orbit,” Æther: A Journal of Strategic Airpower & Spacepower, vol. 1, no. 4 (Winter 2022), pp. 79-94. https://www.airuniversity.af.edu/Portals/10/AEtherJournal/Journals/Volume-1_Number-4/Weeden_Mitigating_Noncooperative_RPOs_.pdf