This support belongs to the Starlink assessment published on 18 October 2026. Its evidence cutoff is 17 October 2026 at 20:49 UTC. Public references and qualified reporting are distinguished from this publication’s interpretation. All 108 evidence entries are retained. Inclusion does not mean that a reported claim is independently verified or equally important.
Read the assessment · Sources · Full comparison · Judgements
Evidence 01–20
E01 · Reports place the disruption overnight on 13–14 October.
Type: Reported claim · Source chain: S-UP-FRONT, S-UP-MOD
Source references: S-UP-FRONT, S-UP-MOD.
Locator: Front report lead; ministry details.
Qualification: Accounts support reported timing, not an authenticated system-change timestamp.
E02 · Beskrestnov attributes the change to SpaceX.
Type: Reported claim · Source chain: S-UP-ADVISER, S-BESK-POST
Source references: S-UP-ADVISER, S-BESK-POST.
Locator: Opening attributed statement; linked post public description.
Qualification: The public description exposes the initial attributed statement; this is evidence of his attribution, not independent technical confirmation of SpaceX action.
Used in: Context or a recorded limitation. Comparison tests: D01.
E03 · Sternenko publicised the problem before the adviser report.
Type: Reported claim · Source chain: S-UP-FRONT, S-UP-ADVISER
Source references: S-UP-FRONT, S-UP-ADVISER.
Locator: Front source line; adviser background.
Qualification: Publication is supported. Independence from the adviser and military sources is not established.
Used in: Context or a recorded limitation. Comparison tests: D04.
E04 · UP says it consulted four frontline sources.
Type: Reported claim · Source chain: S-UP-FRONT
Source references: S-UP-FRONT.
Locator: Source line.
Qualification: Four named-to-the-newsroom sources are not four independently authenticated observations.
E05 · UP reports receiving a commander’s two-drone video.
Type: Reported claim · Source chain: S-UP-FRONT
Source references: S-UP-FRONT.
Locator: Details after two source quotations.
Qualification: The underlying video, capture time and technical cause were not independently examined.
E06 · Sources identify the affected higher-speed military service as Starshield.
Type: Reported claim · Source chain: S-UP-FRONT, S-UP-MOD
Source references: S-UP-FRONT, S-UP-MOD.
Locator: Source 2 and service explanation; ministry details.
Qualification: Service identification is attributed. Equipment model, satellite network, account entitlement and actual contract are separate unresolved questions.
E07 · The reported threshold is approximately 100 mph/160 km/h.
Type: Reported claim · Source chain: S-UP-FRONT, S-UP-ADVISER, S-REUTERS-14, S-BESK-POST
Source references: S-UP-FRONT, S-UP-ADVISER, S-REUTERS-14, S-BESK-POST.
Locator: Front Source 2; adviser opening; wire threshold paragraph; linked post public description.
Qualification: Other observations differ. The conversion is approximate; no single technical enforcement threshold is established for every affected terminal.
E08 · The corps reports disruptions at 110–120 km/h.
Type: Reported claim · Source chain: S-UP-ADVISER, S-REUTERS-14
Source references: S-UP-ADVISER, S-REUTERS-14.
Locator: 11:25 update; wire corps statement.
Qualification: The two publications repeat the same unit account; do not count them as independent observations.
E09 · The same account reports 10–20-second interruptions.
Type: Reported claim · Source chain: S-UP-ADVISER, S-REUTERS-14
Source references: S-UP-ADVISER, S-REUTERS-14.
Locator: 11:25 update; same wire corps statement.
Qualification: This describes the E08 event chain, not a separate corroborating source.
E10 · Sternenko relays reports of disruptions at 60–70 km/h.
Type: Reported claim · Source chain: S-UP-ADVISER
Source references: S-UP-ADVISER.
Locator: Untimed update before 11:25 update.
Qualification: A relayed, later update; operator identities, exact times and shared causes are unverified.
Used in: Context or a recorded limitation. Comparison tests: D02.
E11 · A unit’s missions were reportedly cancelled.
Type: Reported claim · Source chain: S-UP-ADVISER, S-REUTERS-14
Source references: S-UP-ADVISER, S-REUTERS-14.
Locator: 11:25 update; wire corps paragraph.
Qualification: Same corps chain as E08/E09; exact mission count and independent records absent.
E12 · The corps assesses that slower drones are more vulnerable.
Type: Reported claim · Source chain: S-UP-ADVISER
Source references: S-UP-ADVISER.
Locator: Corps discussion in 11:25 update.
Qualification: An attributed operational judgement, not a measured general effect or proof of this incident’s cause.
E13 · Sternenko says standard Starlink terminals still function.
Type: Reported claim · Source chain: S-UP-ADVISER
Source references: S-UP-ADVISER.
Locator: Background attributed to Sternenko.
Qualification: The checked passage does not specifically establish stationary use or a representative nationwide sample. Retain a narrower attributed claim.
E14 · Ministry sources report logistics and unmanned-operation effects.
Type: Reported claim · Source chain: S-UP-MOD, S-REUTERS-14
Source references: S-UP-MOD, S-REUTERS-14.
Locator: Ministry details; wire ministry-source paragraph.
Qualification: Possible overlap between unnamed ministry sources remains unknown; impact extent is unquantified.
E15 · Beskrestnov says no advance warning was received.
Type: Reported claim · Source chain: S-UP-ADVISER, S-REUTERS-14, S-BESK-POST
Source references: S-UP-ADVISER, S-REUTERS-14, S-BESK-POST.
Locator: Adviser statement; wire quotation; linked post public description.
Qualification: His statement is readable in public post metadata; notification delivery to all recipients was not audited.
Used in: Context or a recorded limitation. Comparison tests: D05.
E16 · Sources describe data collection and requests for clarification.
Type: Reported claim · Source chain: S-UP-MOD, S-REUTERS-14
Source references: S-UP-MOD, S-REUTERS-14.
Locator: Ministry quotation; wire clarification paragraph.
Qualification: This supports an unresolved response, but not the exact preserved wording about a separate investigation of precise restrictions.
Used in: Context or a recorded limitation. Comparison tests: D05.
E17 · Reuters reports no immediate SpaceX response outside US business hours.
Type: Reported claim · Source chain: S-REUTERS-14
Source references: S-REUTERS-14.
Locator: Request-for-comment paragraph.
Qualification: Keep this bounded to this reporting version; it does not establish universal silence or lack of any explanation at other times.
Used in: Context or a recorded limitation. Comparison tests: D05.
E18 · Beskrestnov suspects politics; Sternenko suggests Trump-administration involvement.
Type: Reported claim · Source chain: S-UP-ADVISER, S-UP-FRONT, S-BESK-POST
Source references: S-UP-ADVISER, S-UP-FRONT, S-BESK-POST.
Locator: Adviser political comment; Sternenko quotation; linked post public description.
Qualification: These are attributed suspicions, not independent evidence of motive or an instruction.
Used in: Context or a recorded limitation. Comparison tests: D06.
E19 · Beskrestnov says interceptor-drone capability is affected.
Type: Reported claim · Source chain: S-UP-ADVISER
Source references: S-UP-ADVISER.
Locator: 12:05 update.
Qualification: A later attributed impact judgement; not automatically present in the first publication or at V1’s unknown time.
E20 · Several accounts describe disruptions within the same broad overnight/day window.
Type: Analytical inference · Source chain: S-UP-FRONT, S-UP-ADVISER, S-UP-MOD, S-REUTERS-14
Source references: S-UP-FRONT, S-UP-ADVISER, S-UP-MOD, S-REUTERS-14.
Locator: Analytical comparison of the cited reports.
Qualification: National scope, independent unit count, exact synchronisation and one common mechanism are not established. This is a new review of an imported inference.
Used in: Context or a recorded limitation. Comparison tests: D03.
Evidence 21–40
E21 · Sources describe activation at the start of the 2022 invasion.
Type: Reported claim · Source chain: S-ARMY-JAN30, S-REUTERS-FEB1
Source references: S-ARMY-JAN30, S-REUTERS-FEB1.
Locator: Minister recollection and wire background.
Qualification: Historical recollection/reporting, not the original activation log or exact minute.
Used in: Context or a recorded limitation. Comparison tests: D19.
E22 · Sources support large-scale terminals and several support arrangements.
Type: Reported claim · Source chain: S-REUTERS-FEB1, S-PL-FUNDING, S-2024-CONTRACT-REPORT
Source references: S-REUTERS-FEB1, S-PL-FUNDING, S-2024-CONTRACT-REPORT.
Locator: Wire scale; official Polish funding; prior contract preview.
Qualification: Do not add planned procurement to delivered totals, equate connections with terminals, or claim a complete public/private/allied reconciliation.
Used in: Context or a recorded limitation. Comparison tests: D19.
E23 · Reports describe major military communications dependence.
Type: Reported claim · Source chain: S-REUTERS-FEB1, S-REUTERS-14
Source references: S-REUTERS-FEB1, S-REUTERS-14.
Locator: Wire background.
Qualification: An assessed dependence claim; no full command-system or substitution measurement.
Used in: Context or a recorded limitation. Comparison tests: D19.
E24 · Reports cover several drone and logistics uses.
Type: Reported claim · Source chain: S-REUTERS-14, S-UP-MOD
Source references: S-REUTERS-14, S-UP-MOD.
Locator: Existing incident report and ministry-source effects.
Qualification: Reported uses, not independent verification of every unit or mission.
Used in: Context or a recorded limitation. Comparison tests: D19.
E25 · Starshield is described for national-security/government use.
Type: Reported claim · Source chain: S-SHIELD-PROSPECTUS
Source references: S-SHIELD-PROSPECTUS.
Locator: Official PDF p116, Government Solutions.
Qualification: Product scope is supported; it does not establish a physically distinct network or signed terms for the particular affected service.
Used in: Context or a recorded limitation. Comparison tests: D07.
E26 · 2024 reporting describes Ukrainian Starshield access, without proving higher-speed drone use.
Type: Reported claim · Source chain: S-2024-CONTRACT-REPORT, S-UP-FRONT
Source references: S-2024-CONTRACT-REPORT, S-UP-FRONT.
Locator: 2024 public newsroom excerpt; already captured 2026 UP service explanation.
Qualification: Only the first component of the compound historical claim is supported. The excerpt is not the contract or flight/use evidence. This is a new candidate source, not a recovered original citation.
Used in: Context or a recorded limitation. Comparison tests: D07.
E27 · Vendor pages state 100 mph for specified commercial plans in authorised locations.
Type: Reported claim · Source chain: S-MOTION-RULES, S-PLAN-ALERTS
Source references: S-MOTION-RULES, S-PLAN-ALERTS.
Locator: Rendered movement introduction; commercial speed table.
Qualification: Name Roam, Local Priority and Global Priority specifically. Current AU-localised rules do not establish military entitlements, incident implementation or the exact historical version.
Used in: Context or a recorded limitation. Comparison tests: D07.
E28 · Separate commercial aviation plans are listed at 300 and 450 mph.
Type: Reported claim · Source chain: S-AVIATION-PLANS, S-MOTION-RULES
Source references: S-AVIATION-PLANS, S-MOTION-RULES.
Locator: Rendered aviation comparison and movement-plan list.
Qualification: Availability and activation conditions vary. Existence does not show that affected military terminals held or could use these commercial entitlements.
Used in: Context or a recorded limitation. Comparison tests: D07.
E29 · Official documents describe account, location and movement-based service restrictions.
Type: Reported claim · Source chain: S-PLAN-ALERTS, S-MOD-AUTH
Source references: S-PLAN-ALERTS, S-MOD-AUTH.
Locator: Rendered restriction definitions; official ministry opening and caution paragraph.
Qualification: This establishes policy/control capability, not which control was used in October, its exact implementation, who ordered it or its purpose. February authorisation measures are not a demonstrated link to October.
E30 · The frontline account implies prior higher-speed capability; it supplies no before/after measurements.
Type: Analytical inference · Source chain: S-UP-FRONT
Source references: S-UP-FRONT.
Locator: Existing capture: service comparison and reported change.
Qualification: Do not promote a reported service distinction into verified operating history, entitlement, exact speed or a known configuration change.
Used in: Context or a recorded limitation. Comparison tests: D07.
E31 · Applicable signed speed/service-level terms were not established in this audit.
Type: Evidence gap · Source chain: No original source established
Source references: None established..
Locator: Bounded contract search/access record and current retained inventory.
Qualification: Replace universal unavailable with a scoped access gap. A matching contract/annex and applicable historical service settings would clear it; no package-wide stop is required.
Used in: Context or a recorded limitation. Comparison tests: D07.
E32 · Polish funding and reported US defence contracting are supported.
Type: Reported claim · Source chain: S-PL-FUNDING, S-2024-CONTRACT-REPORT
Source references: S-PL-FUNDING, S-2024-CONTRACT-REPORT.
Locator: Dated official Polish funding discussion; US contract preview.
Qualification: Procurement, subscription payments and authority over affected military use are distinct; the public preview is not the contract.
Used in: Context or a recorded limitation. Comparison tests: D19.
E33 · Sources describe Russian use as unauthorised.
Type: Reported claim · Source chain: S-MOD-AUTH, S-REUTERS-FEB1
Source references: S-MOD-AUTH, S-REUTERS-FEB1.
Locator: Official rationale and vendor statement reported by wire.
Qualification: Does not authenticate each acquisition channel or equipment chain of custody.
Used in: Context or a recorded limitation. Comparison tests: D08.
E34 · Official accounts identify Starlink equipment on Russian drones.
Type: Reported claim · Source chain: S-ARMY-JAN30, S-MOD-AUTH
Source references: S-ARMY-JAN30, S-MOD-AUTH.
Locator: Official agency identification and ministry rationale.
Qualification: Underlying specimens/images not independently authenticated in this audit.
Used in: Context or a recorded limitation. Comparison tests: D08.
E35 · Agency reports Molniya and BM-35 use.
Type: Reported claim · Source chain: S-ARMY-JAN30
Source references: S-ARMY-JAN30.
Locator: Official agency discussion of identified drone types.
Qualification: Reported identification and precision claims, not independently observed attacks or general effectiveness.
Used in: Context or a recorded limitation. Comparison tests: D08.
E36 · Sources describe resistance to some electronic-warfare countermeasures.
Type: Reported claim · Source chain: S-ARMY-JAN30, S-MOD-AUTH
Source references: S-ARMY-JAN30, S-MOD-AUTH.
Locator: Attributed technical effects.
Qualification: Do not convert attributed resistance or absolute rhetoric into a universally unjammable system or a tested mechanism.
Used in: Context or a recorded limitation. Comparison tests: D08.
E37 · Official agency records cooperation announced on 29 January.
Type: Reported claim · Source chain: S-ARMY-JAN30
Source references: S-ARMY-JAN30.
Locator: Dated report attributing minister statement to 29 January.
Qualification: A public cooperation statement, not the later system’s completion.
Used in: Context or a recorded limitation. Comparison tests: D08.
E38 · Sources record public thanks to provider leadership.
Type: Reported claim · Source chain: S-ARMY-JAN30, S-MOD-FEB1
Source references: S-ARMY-JAN30, S-MOD-FEB1.
Locator: Attributed thanks and official cooperation statement.
Qualification: A statement about cooperation, not independent proof of all claimed outcomes.
Used in: Context or a recorded limitation. Comparison tests: D08.
E39 · Wire records Musk saying measures seemed effective.
Type: Reported claim · Source chain: S-REUTERS-FEB1
Source references: S-REUTERS-FEB1.
Locator: Dated attributed Musk statement.
Qualification: The apparent-effectiveness statement is supported as attributed; original post and effect size not authenticated.
Used in: Context or a recorded limitation. Comparison tests: D08.
E40 · Official records announce authorisation/whitelisting.
Type: Reported claim · Source chain: S-MOD-FEB1, S-MOD-AUTH
Source references: S-MOD-FEB1, S-MOD-AUTH.
Locator: 1–2 February announcement and instructions.
Qualification: Announcement is distinct from provider’s 4 February effective measures and later operational registration.
Used in: Context or a recorded limitation. Comparison tests: D08.
Evidence 41–60
E41 · The notice describes stationary/low-speed restrictions during implementation.
Type: Reported claim · Source chain: S-MOD-AUTH
Source references: S-MOD-AUTH.
Locator: Existing captured official caution paragraph.
Qualification: No exact universal speed or October application follows from this notice.
Used in: Context or a recorded limitation. Comparison tests: D08.
E42 · Exact preserved 90 km/h report not located.
Type: Evidence gap · Source chain: No original source established
Source references: None established..
Locator: Bounded search/access gap in source-observations.json.
Qualification: Keep the historical number unchanged but do not rely on it as checked evidence. Other checked figures belong to their own accounts.
Used in: Context or a recorded limitation. Comparison tests: D08.
E43 · Preview reports 75 km/h.
Type: Reported claim · Source chain: S-AVIATIONWEEK-FEB2
Source references: S-AVIATIONWEEK-FEB2.
Locator: Public original-newsroom preview, 2 February.
Qualification: Subscriber remainder not accessed. Together with a separate 80 km/h account this shows reporting differences, not proven implementation variation or a recovered basis for E42.
Used in: Context or a recorded limitation. Comparison tests: D08.
E44 · Sources report effects on Russian access/operations.
Type: Reported claim · Source chain: S-MOD-FEB5, S-ATLANTIC-FEB27
Source references: S-MOD-FEB5, S-ATLANTIC-FEB27.
Locator: Official result statement and original reporting.
Qualification: Provider/ministry and military accounts are interested/attributed evidence; no independent effect measurement.
Used in: Context or a recorded limitation. Comparison tests: D08.
E45 · A Ukrainian unit’s disruption and registration waits are described.
Type: Reported claim · Source chain: S-ATLANTIC-FEB27, S-MOD-FEB5
Source references: S-ATLANTIC-FEB27, S-MOD-FEB5.
Locator: Unit disruption account; registration-delay notice.
Qualification: Unintended purpose is not established merely by an adverse effect; registration conditions, delay and misapplication are different possibilities.
Used in: Context or a recorded limitation. Comparison tests: D08.
E46 · Records support government-coordinated whitelist measures in February.
Type: Reported claim · Source chain: S-STARLINK-FEB4, S-MOD-FEB1, S-MOD-FEB5
Source references: S-STARLINK-FEB4, S-MOD-FEB1, S-MOD-FEB5.
Locator: Provider’s effective-date paragraph and official progression.
Qualification: Keep announcement, software implementation, registration and working service as separate dated milestones.
Used in: Context or a recorded limitation. Comparison tests: D08.
E47 · Ministry reports first approved terminals working and Russian terminals blocked.
Type: Reported claim · Source chain: S-MOD-FEB5
Source references: S-MOD-FEB5.
Locator: First-batch operation and waiting-user paragraphs.
Qualification: It also says some submitted terminals are not yet operational. Do not generalise to all registered terminals or guaranteed uninterrupted service.
Used in: Context or a recorded limitation. Comparison tests: D08.
E48 · Provider expressly names coordination with both Ukrainian ministries.
Type: Reported claim · Source chain: S-STARLINK-FEB4
Source references: S-STARLINK-FEB4.
Locator: Rendered provider security paragraph.
Qualification: The page concerns February; it does not identify the October instruction.
Used in: Context or a recorded limitation. Comparison tests: D08.
E49 · The record supports category-based controls introduced over days.
Type: Analytical inference · Source chain: S-STARLINK-FEB4, S-MOD-FEB1, S-MOD-FEB5, S-ATLANTIC-FEB27
Source references: S-STARLINK-FEB4, S-MOD-FEB1, S-MOD-FEB5, S-ATLANTIC-FEB27.
Locator: Current synthesis of dated records.
Qualification: A current inference about this example, not proof of unrestricted control, all-terminal reach, identical military rights or the October cause.
Used in: Context or a recorded limitation. Comparison tests: D08.
E50 · No October-to-February instruction link established in this audit.
Type: Evidence gap · Source chain: No original source established
Source references: None established..
Locator: Scoped absence/link gap in source-observations.json.
Qualification: Non-exhaustive source scope. Missing public evidence is not proof of no request or a negative likelihood conclusion.
Used in: Context or a recorded limitation. Comparison tests: D08.
E51 · Reuters reports an alleged late-September 2022 Kherson order.
Type: Reported claim · Source chain: S-REUTERS-KHERSON
Source references: S-REUTERS-KHERSON.
Locator: Dated source passages identified in source-observations.json..
Qualification: Disputed report, not an authenticated order.
Used in: Context or a recorded limitation. Comparison tests: D09.
E52 · Report identifies three command-familiar sources and battlefield accounts.
Type: Reported claim · Source chain: S-REUTERS-KHERSON
Source references: S-REUTERS-KHERSON.
Locator: Dated source passages identified in source-observations.json..
Qualification: Multiple sources within one investigation are not multiple independent publications; identities and overlap cannot be independently checked.
Used in: Context or a recorded limitation. Comparison tests: D09.
E53 · The article records a SpaceX inaccuracy objection without specified errors.
Type: Reported claim · Source chain: S-REUTERS-KHERSON
Source references: S-REUTERS-KHERSON.
Locator: Dated source passages identified in source-observations.json..
Qualification: Bound this to the response reported by this article, not a global assertion that no detailed rebuttal exists.
Used in: Context or a recorded limitation. Comparison tests: D09.
E54 · Separate Crimea biography account was corrected from shutdown to refusal to enable.
Type: Reported claim · Source chain: S-REUTERS-KHERSON
Source references: S-REUTERS-KHERSON.
Locator: Dated source passages identified in source-observations.json..
Qualification: Do not merge Crimea and Kherson or use the correction to disprove/verify the other incident.
Used in: Context or a recorded limitation. Comparison tests: D09.
E55 · Executive acknowledged some offensive-drone restrictions in February 2023.
Type: Reported claim · Source chain: S-REUTERS-SHOTWELL
Source references: S-REUTERS-SHOTWELL.
Locator: Dated source passages identified in source-observations.json..
Qualification: Mechanism and scope unspecified; not proof of every prior disruption.
Used in: Context or a recorded limitation. Comparison tests: D09.
E56 · Executive distinguished military communications from weaponising drones.
Type: Reported claim · Source chain: S-REUTERS-SHOTWELL
Source references: S-REUTERS-SHOTWELL.
Locator: Dated source passages identified in source-observations.json..
Qualification: Public explanation and humanitarian agreement account do not establish affected October military terms.
Used in: Context or a recorded limitation. Comparison tests: D09.
E57 · Reuters reported a threat during minerals talks.
Type: Reported claim · Source chain: S-REUTERS-MINERALS
Source references: S-REUTERS-MINERALS.
Locator: Dated source passages identified in source-observations.json..
Qualification: Disputed allegation of possible loss; no demonstrated implementation.
Used in: Context or a recorded limitation. Comparison tests: D10.
E58 · Musk denied the minerals report; Rubio denied threats.
Type: Reported claim · Source chain: S-REUTERS-MINERALS, S-REUTERS-MARCH9
Source references: S-REUTERS-MINERALS, S-REUTERS-MARCH9.
Locator: Dated source passages identified in source-observations.json..
Qualification: Denials and reported allegation both retained; neither independently resolves the dispute.
Used in: Context or a recorded limitation. Comparison tests: D10.
E59 · Official joint statement acknowledges pause and announces assistance/intelligence resumption.
Type: Reported claim · Source chain: S-JEDDAH-2025
Source references: S-JEDDAH-2025.
Locator: Dated source passages identified in source-observations.json..
Qualification: Policy acknowledgement, not a measured delivery timeline or Starlink action.
Used in: Context or a recorded limitation. Comparison tests: D10.
E60 · Musk publicly promised no shutoff/bargaining.
Type: Reported claim · Source chain: S-REUTERS-MARCH9
Source references: S-REUTERS-MARCH9.
Locator: Dated source passages identified in source-observations.json..
Qualification: Reported pledge, not proof of future adherence or a resolution of earlier allegations.
Used in: Context or a recorded limitation. Comparison tests: D10.
Evidence 61–80
E61 · AP reports a July request for help securing provider permission.
Type: Reported claim · Source chain: S-AP-JULY
E62 · AP reports Trump did not commit.
Type: Reported claim · Source chain: S-AP-JULY
E63 · The request supports an inference that Ukraine perceived approval as important.
Type: Analytical inference · Source chain: S-AP-JULY
E64 · Cooperation and selective restrictions can coexist.
Type: Analytical inference · Source chain: S-STARLINK-FEB4, S-REUTERS-SHOTWELL, S-REUTERS-FEB1
Source references: S-STARLINK-FEB4, S-REUTERS-SHOTWELL, S-REUTERS-FEB1.
Locator: Dated source passages identified in source-observations.json..
Qualification: Current synthesis of separate examples, not an identified October arrangement.
Used in: Context or a recorded limitation. Comparison tests: D11.
E65 · The report describes refinery damage and supply disruption.
Type: Reported claim · Source chain: S-WIRE-DIESEL-9
Source references: S-WIRE-DIESEL-9.
Locator: Refinery damage and export/supply discussion.
Qualification: Supports reported energy effects; does not independently measure the full production/logistics effect or prove a particular actor’s motive.
Used in: Context or a recorded limitation. Comparison tests: D12.
E66 · The report links the fuel supply shock to domestic price/election pressure.
Type: Reported claim · Source chain: S-WIRE-DIESEL-9
Source references: S-WIRE-DIESEL-9.
Locator: Fuel-price and election context.
Qualification: Reported context, not an estimate of causal shares or authenticated motivation for the satellite decision.
Used in: Context or a recorded limitation. Comparison tests: D12.
E67 · Unnamed US official describes repeated requests.
Type: Reported claim · Source chain: S-AXIOS-10
Source references: S-AXIOS-10.
Locator: Lead and request discussion.
Qualification: Anonymous attributed account, not an authenticated presidential instruction or a demonstrated Starshield link.
E68 · The 9 October report records Trump announcing the arrangement.
Type: Reported claim · Source chain: S-WIRE-DIESEL-9
Source references: S-WIRE-DIESEL-9.
Locator: Dated lead and attributed announcement.
Qualification: Announcement is distinct from delivered fuel, fulfilled terms or effects.
Used in: Context or a recorded limitation. Comparison tests: D12.
E69 · The dated licence authorises specified diesel transactions with limits.
Type: Reported claim · Source chain: S-OFAC-135
Source references: S-OFAC-135.
Locator: Paragraphs (a)–(b) and date.
Qualification: A limited administrative act; do not broaden to all sanctions or all Russian trade.
Used in: Context or a recorded limitation. Comparison tests: D12.
E70 · The wire reports Trump’s criticism of the refinery campaign.
Type: Reported claim · Source chain: S-WIRE-INTEL-13, S-WIRE-14-UPDATED
Source references: S-WIRE-INTEL-13, S-WIRE-14-UPDATED.
Locator: Public-criticism context.
Qualification: Attributed public statements, not a specific satellite order.
E71 · The report says he called for replacing Ukraine’s leader.
Type: Reported claim · Source chain: S-WIRE-14-UPDATED
Source references: S-WIRE-14-UPDATED.
Locator: Public-criticism paragraph.
Qualification: This source does not establish the exact 10 October timestamp of the preserved claim.
Used in: Context or a recorded limitation. Comparison tests: D13.
E72 · A published account attributes a supportive comment to Musk.
Type: Reported claim · Source chain: S-LRT-MUSK
Source references: S-LRT-MUSK.
Locator: Source report and embedded-post attribution.
Qualification: The available source version differs from the recorded account; date/post content remains mediated and not directly authenticated.
Used in: Context or a recorded limitation. Comparison tests: D13.
E73 · The wire reports an immediate-truce announcement on 11 October.
Type: Reported claim · Source chain: S-WIRE-FT-11
Source references: S-WIRE-FT-11.
Locator: Final announcement paragraphs.
Qualification: A reported announcement is not evidence that both sides accepted or implemented it.
Used in: Context or a recorded limitation. Comparison tests: D12.
E74 · The reports say both sides had not confirmed the truce.
Type: Reported claim · Source chain: S-WIRE-INTEL-13, S-WIRE-14-UPDATED
Source references: S-WIRE-INTEL-13, S-WIRE-14-UPDATED.
Locator: Truce-status paragraphs.
Qualification: Time-bounded reporting, not a universal search for every acceptance channel.
Used in: Context or a recorded limitation. Comparison tests: D12.
E75 · The report attributes a reciprocal condition to Zelenskyy.
Type: Reported claim · Source chain: S-WIRE-INTEL-13
Source references: S-WIRE-INTEL-13.
Locator: Reciprocal-restraint discussion.
Qualification: A stated position, not verified implementation by either side.
Used in: Context or a recorded limitation. Comparison tests: D12.
E76 · Reuters relays FT reporting of intelligence and PURL threats.
Type: Reported claim · Source chain: S-WIRE-FT-11, S-WIRE-14-UPDATED
Source references: S-WIRE-FT-11, S-WIRE-14-UPDATED.
Locator: FT-attributed lead and weapons/intelligence paragraph; later threat discussion.
Qualification: The 11 October wire explicitly says it could not independently verify the report. European interlocutors may be direct recipients or briefed; later newsroom overlap is unknown. Keep the attributed threat separate from an implemented cutoff or the October satellite motive.
E77 · Ukrainian alleges intelligence threat; US official disputes it.
Type: Reported claim · Source chain: S-AXIOS-10
Source references: S-AXIOS-10.
Locator: Inside the room.
Qualification: Conflicting attributed accounts persist. A denial does not erase the allegation; neither account authenticates what occurred.
E78 · The wire reports further energy attacks after the announcement.
Type: Reported claim · Source chain: S-WIRE-INTEL-13, S-WIRE-14-UPDATED
Source references: S-WIRE-INTEL-13, S-WIRE-14-UPDATED.
Locator: Reported Russian energy attacks.
Qualification: Not an independent battle-damage or complete ceasefire-compliance audit.
Used in: Context or a recorded limitation. Comparison tests: D12.
E79 · The wire records his complaint about missing warnings.
Type: Reported claim · Source chain: S-WIRE-INTEL-13
Source references: S-WIRE-INTEL-13.
Locator: Zelenskyy warning complaint.
Qualification: Some missed warnings do not establish that all intelligence sharing stopped or that withholding was deliberate.
Used in: Context or a recorded limitation. Comparison tests: D12.
E80 · The wire records Trump maintaining that sharing continues.
Type: Reported claim · Source chain: S-WIRE-INTEL-13
Source references: S-WIRE-INTEL-13.
Locator: Trump public statement and contrasting Ukrainian statements.
Qualification: Reported statement, not proof of complete/timely delivery. The same story reports continued receipt from Ukrainian officials and an alleged future threat.
Used in: Context or a recorded limitation. Comparison tests: D12.
Evidence 81–100
E81 · Reuters states that refinery-strike drones use other communications.
Type: Reported claim · Source chain: S-REUTERS-14
Source references: S-REUTERS-14.
Locator: Previously captured incident report, political-context section.
Qualification: This is a newsroom assertion, not independently measured technical coverage. It weakens a direct-disabling story without excluding wider coercive leverage.
E82 · The updated wire reports a Ukrainian data-centre strike.
Type: Reported claim · Source chain: S-WIRE-14-UPDATED
Source references: S-WIRE-14-UPDATED.
Locator: Data-centre paragraph.
Qualification: A reported contemporaneous event, not evidence of the satellite decision-maker or retaliation purpose. Precise historical availability remains unknown.
Used in: Context or a recorded limitation. Comparison tests: D12.
E83 · The official release records the 8 October award to Musk.
Type: Analytical inference · Source chain: S-WH-MEDAL
Source references: S-WH-MEDAL.
Locator: Dated release and medalist list.
Qualification: The award is supported; renewed relationship or coordinated intent is a separate interpretation.
Used in: Context or a recorded limitation. Comparison tests: D13.
E84 · The wire attributes a public challenge to Sikorski.
Type: Reported claim · Source chain: S-WIRE-14-UPDATED
Source references: S-WIRE-14-UPDATED.
Locator: Polish reaction paragraphs.
Qualification: Primary post not independently retrieved; a political reaction is not corroboration of his suspected cause.
Used in: Context or a recorded limitation. Comparison tests: D12.
E85 · Official and provider-attributed accounts support Russian interference capability/use.
Type: Reported claim · Source chain: S-USSF-THREATS, S-REUTERS-SHOTWELL
Source references: S-USSF-THREATS, S-REUTERS-SHOTWELL.
Locator: Dated source passages identified in source-observations.json..
Qualification: Independent technical verification of every system affected or a link to October is absent.
E86 · Positioning-related and satellite-data-link failures are distinct possibilities.
Type: Reported claim · Source chain: S-USSF-THREATS, S-PLAN-ALERTS
Source references: S-USSF-THREATS, S-PLAN-ALERTS.
Locator: Dated source passages identified in source-observations.json..
Qualification: Official interference context plus provider location warnings establish plausibility, not actual Russian GPS causation here.
E87 · Official notice reports suspected Russian-linked September ground-infrastructure arson.
Type: Reported claim · Source chain: S-PL-ARSON
Source references: S-PL-ARSON.
Locator: Dated source passages identified in source-observations.json..
Qualification: Official attribution, suspects and arrests; no conviction or October speed-link established.
E88 · Western official account describes concerning Russian orbital activities.
Type: Reported claim · Source chain: S-USSF-THREATS
Source references: S-USSF-THREATS.
Locator: Dated source passages identified in source-observations.json..
Qualification: Official threat assessment, not a demonstrated attack on the affected service.
E89 · No incident-specific Russian interference connection established in the checked source set.
Type: Evidence gap · Source chain: No original source established
E90 · Alternative development and an operating European government-service pool are documented.
Type: Reported claim · Source chain: S-UASAT-JV, S-EU-GOVSATCOM, S-REUTERS-MARCH9
Source references: S-UASAT-JV, S-EU-GOVSATCOM, S-REUTERS-MARCH9.
Locator: Dated source passages identified in source-observations.json..
Qualification: Exact UASAT-NANO operational status and comparative platform suitability are unverified; do not present plans as a ready equivalent.
Used in: Context or a recorded limitation. Comparison tests: D22.
E91 · Reuters attributes White House origin and a message to Pentagon leaders to two US officials and a Western official briefed on the matter.
Type: Reported claim · Source chain: S-WIRE
E92 · A senior Ukrainian official describes calls and says Kyiv was told the decision was from the White House.
Type: Reported claim · Source chain: S-WIRE
E93 · The wire attributes to Musk a statement that speed or usage limits are decided by the US military or the president.
Type: Reported claim · Source chain: S-WIRE
E94 · The wire reports a senior US official denying a request by the president and no White House response about other officials.
Type: Reported claim · Source chain: S-WIRE
E95 · The official release names nine senators requesting an Inspector General investigation.
Type: Reported claim · Source chain: S-SENATE
Source references: S-SENATE.
Locator: Published date, opening list and reproduced request letter.
Qualification: Primary evidence of the public request, not an investigation finding or independent confirmation of incident causes. The letter explicitly leaves cause and connections uncertain.
Used in: Context or a recorded limitation. Comparison tests: D18.
E96 · Beskrestnov describes the affected service as a Pentagon-managed military package with separate terms.
Type: Reported claim · Source chain: N-AP16
E97 · The adviser reports prior high-speed service and a remaining motion cap.
Type: Reported claim · Source chain: N-AP16
E98 · The adviser reports separate transient outages repaired while a cap remained.
Type: Reported claim · Source chain: N-AP16
E99 · He reports negotiations over removing the cap or changing military service package.
Type: Reported claim · Source chain: N-AP16
E100 · A 16 October public-briefing account says service was recovering.
Type: Reported claim · Source chain: N-INTERFAX16
Source references: N-INTERFAX16.
Locator: Dated body, recovering-speed statement.
Qualification: Stronger headline is not proof of full recovery; timing and capability scope matter.
Evidence 101–108
E101 · Zelenskyy said restrictions remained partial on 17 October.
Type: Reported claim · Source chain: N-AXIOS17
E102 · Trump publicly denied responsibility and doubted Musk was responsible.
Type: Reported claim · Source chain: N-AP16, N-AXIOS16
Source references: N-AP16, N-AXIOS16.
Locator: Hanna Arhirova 16 October interview; service-package, outage-repair and negotiation passages; Trump public comments and Ukrainian counterclaim.
Qualification: These repeat the same public comments; denial is evidence to weigh, not proof or independent repetition.
E103 · Zelenskyy alleges Ukraine-specific restrictions and infers planned action.
Type: Reported claim · Source chain: N-AP17
E104 · Beskrestnov says the affected service is not used for refinery strikes inside Russia.
Type: Reported claim · Source chain: N-AP16
E105 · The Telegraph reports four unnamed sources alleging Musk proposed a restriction and Trump agreed.
Type: Reported claim · Source chain: N-TELEGRAPH16
Source references: N-TELEGRAPH16.
Locator: Lead; four-source description; agreement, response and restoration passages.
Qualification: One original reporting chain; source identities, first-hand access and overlap with Reuters are unknown. Underlying discussion/order unauthenticated.
E106 · The report also carries the public and official denials.
Type: Reported claim · Source chain: N-TELEGRAPH16
Source references: N-TELEGRAPH16.
Locator: Lead; four-source description; agreement, response and restoration passages.
Qualification: A denial retained in the same article does not independently resolve the contested account.
E107 · The current Reuters syndication retains White House-origin reporting without identifying the actual decision-maker or implementer.
Type: Reported claim · Source chain: N-REUTERS16
Source references: N-REUTERS16.
Locator: Lead, source descriptions, denial, request for comment and Ukrainian calls.
Qualification: Same audited chain as E91–E94, not an independent new source.
E108 · The later interview article places onset on Thursday, unlike reports first published on Wednesday 14 October.
Type: Conflicting source accounts · Source chain: N-AP16
Source references: N-AP16.
Locator: Hanna Arhirova 16 October interview; service-package, outage-repair and negotiation passages.
Qualification: Preserve the discrepancy. Use first public reporting on 14 October; do not claim an exact start time is settled.
Used in: Context or a recorded limitation. Comparison tests: D26.