[ { "slug": "amazon-leo-d2d", "name": "Amazon Leo Direct-to-Device", "family": "amazon-leo", "aka": "Amazon Leo D2D; Kuiper direct-to-device", "operator": "Kuiper Systems LLC", "parent": "Amazon.com, Inc.", "country": "US", "jurisdiction": "US", "system_class": "direct-to-device", "status": "filed", "status_detail": "Application filed with the FCC on 24 July 2026 for up to 5,105 satellites, using the L- and S-band spectrum held by Globalstar, whose acquisition by Amazon was announced in April 2026 and is expected to close in 2027. No grant. Service stated as no earlier than 2028.", "services": "direct-to-device; voice; messaging; broadband; iot", "orbit_regimes": "LEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "SAT-LOA-20260601-00224", "filing_call_sign": "S00917", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": null, "filed": 5105, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "L; S", "isl": "unknown", "first_launch": "", "service_start": "", "target_completion": "", "target_completion_kind": "operator-target", "launch_providers": "", "n_regulatory": 1, "n_itu": 0, "n_sources": 4, "has_primary": "yes", "n_discrepancies": 0, "supersedes": "", "superseded_by": "", "notes": "Contributed by Dan York on 29 July 2026, having been filed after his IETF 126 survey was presented. The first entry in the registry to come from the community rather than the initial sweep, and the first whose provenance was upgraded by a contributor: Dan supplied the ICFS file number on 3 August 2026, and the count, the band edges and the lifetime now come from Schedule S instead of trade press. Provenance gap: the orbital geometry is in an attachment, \"Amazon Leo D2D Application - Orbital Parameters Attachment.zip\", which has not been opened, and the public version of Exhibit C (technical attachment and ODAR) has not been read. A confidential version of Exhibit C is withheld, so some technical detail will not become public. This record and globalstar-c3 will need reconciling if the Amazon acquisition of Globalstar completes: two systems, one spectrum position, one eventual owner. Whether the D2D constellation supersedes the C-3 plan or runs alongside it is not yet stated anywhere this registry has found.", "added": "2026-07", "verified": "2026-08-03", "verified_age_months": 0, "stale": "no" }, { "slug": "amazon-leo-gen1", "name": "Amazon Leo Gen1", "family": "amazon-leo", "aka": "Project Kuiper; Kuiper Gen1", "operator": "Kuiper Systems LLC", "parent": "Amazon.com, Inc.", "country": "US", "jurisdiction": "US", "system_class": "broadband", "status": "deploying", "status_detail": "Production satellites launching since April 2025 and enterprise beta service from 2025, but far short of the interim deployment milestone, which the FCC waived in part with conditions in June 2026.", "services": "broadband; backhaul", "orbit_regimes": "LEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "SAT-LOA-20190704-00057", "filing_call_sign": "S3051", "filing_absent": "", "launched": 398, "in_orbit": null, "licensed": 3232, "filed": 3236, "announced": null, "n_shells": 3, "constellation_code": "", "constellation_code_status": "", "spectrum": "Ku; Ka; V", "isl": "optical", "first_launch": "2023-10-06", "service_start": "2025", "target_completion": "2029-07-30", "target_completion_kind": "regulatory-milestone", "launch_providers": "United Launch Alliance; Arianespace; Blue Origin; SpaceX", "n_regulatory": 3, "n_itu": 0, "n_sources": 3, "has_primary": "yes", "n_discrepancies": 2, "supersedes": "", "superseded_by": "", "notes": "Amazon renamed Project Kuiper to Amazon Leo in 2026 and the FCC order adopts the new name for both constellation and licensee, while the licensee of record remains Kuiper Systems LLC. Provenance gap: FCC 20-102 is cited through the fcc.report mirror of the grant attachment rather than a docs.fcc.gov permanent URL, and the 2024 orbital parameters modification (39 FCC Rcd 2180) has not been read. The shells recorded here are the 2020 configuration, so the current authorised geometry may differ. This is why each shell carries its own src.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "amazon-leo-gen2", "name": "Amazon Leo Gen2 and Polar", "family": "amazon-leo", "aka": "Kuiper Gen2; Amazon Leo Polar system; Amazon 2026 V-band Grant", "operator": "Kuiper Systems LLC", "parent": "Amazon.com, Inc.", "country": "US", "jurisdiction": "US", "system_class": "broadband", "status": "licensed", "status_detail": "Authorised 10 February 2026 in the 2021 V-band processing round. Nothing launched under this authorisation; the first milestone is six years out.", "services": "broadband; backhaul", "orbit_regimes": "LEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "SAT-LOA-20211104-00145", "filing_call_sign": "S3105", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": 4504, "filed": null, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "V", "isl": "", "first_launch": "", "service_start": "", "target_completion": "2035-02-10", "target_completion_kind": "regulatory-milestone", "launch_providers": "", "n_regulatory": 2, "n_itu": 0, "n_sources": 2, "has_primary": "yes", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: this record is built entirely from the description of the 10 February 2026 grant contained in a *later* order (DA 26-553). The grant stamp itself, under ICFS SAT-LOA-20211104-00145 and SAT-AMD-20250311-00068, has not been read. Reading it would supply the orbital parameters for both the Gen2 and Polar systems, which are the main gap in this record. Note the source grading subtlety: DA 26-553 is a primary source, and it is a primary source *for what it says*, which is the counts and the milestone dates. It is not a source for the shell geometry, which it does not discuss. A source's grade does not extend beyond its contents.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "ast-spacemobile", "name": "AST SpaceMobile", "family": "ast-spacemobile", "aka": "SpaceMobile; BlueBird; BlueWalker; FM-1 / FM-2", "operator": "AST & Science, LLC", "parent": "AST SpaceMobile, Inc.", "country": "US", "jurisdiction": "US", "system_class": "direct-to-device", "status": "deploying", "status_detail": "Fully authorised for 248 satellites as of April 2026, including supplemental coverage from space and direct-to-cell operations, with spectrum leases from AT&T, Verizon and FirstNet granted the same day. A small number of satellites are in orbit.", "services": "direct-to-device; broadband", "orbit_regimes": "LEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "SAT-LOA-20200413-00034", "filing_call_sign": "S3065", "filing_absent": "", "launched": 9, "in_orbit": null, "licensed": 248, "filed": 248, "announced": null, "n_shells": 5, "constellation_code": "", "constellation_code_status": "", "spectrum": "V; S; L", "isl": "unknown", "first_launch": "2022-09-10", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "SpaceX; Blue Origin", "n_regulatory": 1, "n_itu": 0, "n_sources": 3, "has_primary": "yes", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "This record is the registry's worked example of orbital geometry that the constellation code cannot express for a reason unrelated to phasing: every authorised shell here is elliptical, with apogee and perigee stated separately and a station-keeping tolerance attached. The code assumes a single circular altitude. Four of the five shells also fail the code's divisibility or plane-count assumptions independently. AST's satellites are physically very large, which is why the constellation size is small relative to its coverage ambition. Recording sat_mass_kg for this system would be valuable and has not been done.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "blue-origin-sunrise", "name": "Blue Origin Project Sunrise", "family": "blue-origin", "aka": "Project Sunrise; Blue Origin Orbital Data Center System", "operator": "Blue Origin, LLC", "parent": "Blue Origin, LLC", "country": "US", "jurisdiction": "US", "system_class": "orbital-compute", "status": "filed", "status_detail": "Application filed 19 March 2026; no grant. NASA filed an objection in May 2026. Nothing launched.", "services": "orbital-compute", "orbit_regimes": "LEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "", "filing_call_sign": "", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": null, "filed": 51600, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "Ka; optical", "isl": "external", "first_launch": "", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "", "n_regulatory": 2, "n_itu": 0, "n_sources": 3, "has_primary": "no", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: no primary source, and the ICFS file number has not been retrieved. Reading the application would give the shell structure, the satellite design and the basis for the 51,600 figure, and reading NASA's objection would give the first documented instance in this registry of a federal science agency contesting a constellation filing on operational grounds. Both are worth doing.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "blue-origin-terawave", "name": "Blue Origin TeraWave", "family": "blue-origin", "aka": "Tera Wave", "operator": "Blue Origin, LLC", "parent": "Blue Origin, LLC", "country": "US", "jurisdiction": "US", "system_class": "broadband", "status": "announced", "status_detail": "Announced January 2026, with deployment stated to begin Q4 2027. No FCC file number has been retrieved for TeraWave itself, though it is referred to in the Project Sunrise filing as the optical backbone that system depends on.", "services": "broadband; backhaul", "orbit_regimes": "LEO; MEO", "dual_use": "civil", "filing_authority": "", "filing_number": "", "filing_call_sign": "", "filing_absent": "No filing reference retrieved. TeraWave is described in trade press as an announced constellation and is referenced in Blue Origin's Project Sunrise FCC application as the communications network Sunrise will relay through, but no application or grant for TeraWave itself has been located in this pass. It may well exist; this is a gap in our work, not a statement that none exists.", "launched": null, "in_orbit": null, "licensed": null, "filed": null, "announced": 5408, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "optical", "first_launch": "", "service_start": "", "target_completion": "2027", "target_completion_kind": "operator-target", "launch_providers": "Blue Origin", "n_regulatory": 0, "n_itu": 0, "n_sources": 2, "has_primary": "no", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: no primary source and no filing reference. Everything here is trade press and a conference slide, and the headline count is disputed three ways. Locating a TeraWave application in ICFS would fix all of it. Recorded despite that because Project Sunrise, which does have a filing, depends on TeraWave for its ground path. A registry that carried Sunrise but not TeraWave would hide the dependency.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "china-mobile-l1", "name": "China Mobile L1 and M1", "family": "china-mobile", "aka": "CHINAMOBILE-L1; CHINAMOBILE-M1", "operator": "China Mobile", "parent": "China Mobile Communications Group, state-owned", "country": "CN", "jurisdiction": "CN", "system_class": "broadband", "status": "filed", "status_detail": "Advance publication information received by the ITU on 30 December 2025 and published 14 April 2026, one day after the CTC-1 and CTC-2 filings and part of the same wave. API/A only: no coordination request, no national authorisation identified, nothing launched.", "services": "broadband; direct-to-device", "orbit_regimes": "VLEO; LEO; MEO", "dual_use": "unknown", "filing_authority": "other", "filing_number": "API/A 14312 (notice ID 125545461)", "filing_call_sign": "", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": null, "filed": 2664, "announced": null, "n_shells": 5, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "unknown", "first_launch": "", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "", "n_regulatory": 0, "n_itu": 2, "n_sources": 2, "has_primary": "yes", "n_discrepancies": 0, "supersedes": "", "superseded_by": "", "notes": "Found by scanning the non-GSO tables of the downloaded BR IFICs for Chinese networks with large plane counts, while looking for something else. It appears in no secondary source consulted for this registry and was not in the IETF 126 survey. A 2,664-satellite filing by the largest mobile operator in the world is not a marginal entry, and the fact that it surfaced only by reading the ITU publication directly is the clearest argument this registry has for doing so routinely. The 251 km shell is worth attention on its own: 960 satellites in 960 separate planes at an altitude where drag is severe. Whether that is a serious deployment plan or a spectrum placeholder is exactly the question the API/A stage cannot answer.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "cowboy-space-stampede", "name": "Cowboy Space Stampede", "family": "cowboy-space", "aka": "Stampede", "operator": "Cowboy Space", "parent": "Cowboy Space (San Carlos, California)", "country": "US", "jurisdiction": "US", "system_class": "orbital-compute", "status": "filed", "status_detail": "Application filed 14 May 2026. The company states the satellite design is unfinished and that a licence modification will be needed before service, which is unusually explicit about how provisional the filing is.", "services": "orbital-compute", "orbit_regimes": "LEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "", "filing_call_sign": "", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": null, "filed": 20000, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "unknown", "first_launch": "2028", "service_start": "", "target_completion": "", "target_completion_kind": "operator-target", "launch_providers": "", "n_regulatory": 1, "n_itu": 0, "n_sources": 2, "has_primary": "no", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: no primary source and no file number. This record is worth keeping in view for a reason beyond its size. The company told the regulator that the satellite design is unfinished and that a modification will be needed before service. That is a filing made to hold a place in a processing round, stated as such, by the applicant. It is the cleanest documented instance in this registry of the mechanism Dan York and Nitinder Mohan discussed at IETF 126: filings as spectrum positioning rather than deployment commitments. Recording it as `filed` and never as `licensed` is exactly the distinction the registry exists to preserve.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "ctc-1", "name": "CTC-1", "family": "ctc", "aka": "China Radio Spectrum next-generation constellation 1", "operator": "Institute of Radio Spectrum Utilization and Technological Innovation", "parent": "Chinese state research institute", "country": "CN", "jurisdiction": "CN", "system_class": "other", "status": "filed", "status_detail": "Advance publication information received by the ITU on 29 December 2025 and published on 17 March 2026. API/A is the earliest and weakest stage of the ITU process: it precedes the coordination request and confers no coordination priority. Nothing launched and no deployment programme identified.", "services": "other", "orbit_regimes": "LEO", "dual_use": "unknown", "filing_authority": "other", "filing_number": "API/A 14285 (notice ID 125545446)", "filing_call_sign": "", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": null, "filed": 96714, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "unknown", "first_launch": "", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "", "n_regulatory": 0, "n_itu": 1, "n_sources": 4, "has_primary": "yes", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Upgraded from secondary to primary on 2026-07-29 by querying the ITU Space Network List for the filing identity and then reading the declared orbit data out of BR IFIC 3067 directly. See scripts/itu_query.sh, which reproduces both steps. CTC-1 and CTC-2 together account for about 193,000 of the roughly 200,000 satellites in the December 2025 Chinese filing wave, and therefore for a large share of any global aggregate. A reader deciding how much weight to put on a 2.3 million total should know that roughly 8 per cent of it comes from two filings by a single research institute, with a stated purpose that nobody has confirmed. Making that visible is the point of keeping the record.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "ctc-2", "name": "CTC-2", "family": "ctc", "aka": "China Radio Spectrum next-generation constellation 2", "operator": "Institute of Radio Spectrum Utilization and Technological Innovation", "parent": "Chinese state research institute", "country": "CN", "jurisdiction": "CN", "system_class": "other", "status": "filed", "status_detail": "Advance publication information received by the ITU on 29 December 2025 and published on 17 March 2026. API/A is the earliest and weakest stage of the ITU process: it precedes the coordination request and confers no coordination priority. Nothing launched and no deployment programme identified.", "services": "other", "orbit_regimes": "LEO", "dual_use": "unknown", "filing_authority": "other", "filing_number": "API/A 14288 (notice ID 125545445)", "filing_call_sign": "", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": null, "filed": 96714, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "unknown", "first_launch": "", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "", "n_regulatory": 0, "n_itu": 1, "n_sources": 4, "has_primary": "yes", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Upgraded from secondary to primary on 2026-07-29 by querying the ITU Space Network List for the filing identity and then reading the declared orbit data out of BR IFIC 3067 directly. See scripts/itu_query.sh, which reproduces both steps. CTC-1 and CTC-2 together account for about 193,000 of the roughly 200,000 satellites in the December 2025 Chinese filing wave, and therefore for a large share of any global aggregate. A reader deciding how much weight to put on a 2.3 million total should know that roughly 8 per cent of it comes from two filings by a single research institute, with a stated purpose that nobody has confirmed. Making that visible is the point of keeping the record.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "eutelsat-oneweb", "name": "Eutelsat OneWeb", "family": "oneweb", "aka": "OneWeb; WorldVu; OneWeb Ku/Ka NGSO FSS system", "operator": "WorldVu Satellites Limited", "parent": "Eutelsat Group (merged with OneWeb 2023)", "country": "GB", "jurisdiction": "GB; US", "system_class": "broadband", "status": "operational", "status_detail": "First-generation constellation complete and in wholesale service. Authorised by the United Kingdom; US market access granted by the FCC and modified in 2023 from 720 to 716 satellites. A requested expansion to 6,372 satellites was deferred, not granted.", "services": "broadband; backhaul", "orbit_regimes": "LEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "SAT-MPL-20200526-00062", "filing_call_sign": "S2963", "filing_absent": "", "launched": 660, "in_orbit": null, "licensed": 716, "filed": 6372, "announced": null, "n_shells": 3, "constellation_code": "", "constellation_code_status": "", "spectrum": "Ku; Ka", "isl": "none", "first_launch": "2019-02-27", "service_start": "2023", "target_completion": "", "target_completion_kind": "", "launch_providers": "Arianespace; SpaceX; ISRO", "n_regulatory": 2, "n_itu": 0, "n_sources": 3, "has_primary": "yes", "n_discrepancies": 2, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: the UK authorisation held by WorldVu Satellites Limited has not been retrieved, so the licensed figure recorded here is strictly the number for which US market access is granted. Eutelsat Next, the announced successor constellation, is not recorded and needs its own record once a filing or a firm figure can be traced.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "globalstar-c3", "name": "Globalstar C-3", "family": "globalstar", "aka": "Globalstar-C3 MSS System; Globalstar third generation; AST-NG-C-3", "operator": "Globalstar France SAS", "parent": "Globalstar, Inc. (acquisition by Amazon.com, Inc. filed with the FCC 26 May 2026; pleading cycle open as of June 2026)", "country": "US", "jurisdiction": "FR", "system_class": "direct-to-device", "status": "filed", "status_detail": "Licensed by France and notified to the ITU. US market access is sought through a pending petition for declaratory ruling, not a US licence, so the system has no FCC authorisation. Nothing launched.", "services": "voice; messaging; direct-to-device; iot", "orbit_regimes": "LEO; MEO", "dual_use": "civil", "filing_authority": "other", "filing_number": "SAT-PDR-20250214-00047", "filing_call_sign": "S3233", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": 48, "filed": 6221, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "unknown", "first_launch": "", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "", "n_regulatory": 3, "n_itu": 1, "n_sources": 5, "has_primary": "yes", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Globalstar's operational second-generation service is a separate system and has its own record, globalstar-hibleo. The deck's \"97 launched\" and \"~85 planned\" belong there, not here. This record is also the registry's worked example of the flag-of-convenience pattern: a US operator's constellation licensed by a European administration and reaching the US market through a declaratory ruling rather than a licence. It is why `country` and `jurisdiction` are separate fields. Provenance gap: the French authorisation has not been retrieved, so the 48-satellite figure rests on the FCC's description of it rather than on the French decision itself.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "globalstar-hibleo", "name": "Globalstar second generation", "family": "globalstar", "aka": "HIBLEO-4; HIBLEO-X; Globalstar 2nd generation", "operator": "Globalstar Licensee LLC; GUSA Licensee LLC", "parent": "Globalstar, Inc. (acquisition by Amazon.com, Inc. filed 26 May 2026; pleading cycle open)", "country": "US", "jurisdiction": "US; FR", "system_class": "direct-to-device", "status": "operational", "status_detail": "In commercial service, and the backbone of Apple's Emergency SOS. Operates as one system across a US-licensed component (HIBLEO-4) and a France-licensed component (HIBLEO-X) reached through a US market access grant.", "services": "voice; messaging; iot; direct-to-device", "orbit_regimes": "LEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "", "filing_call_sign": "", "filing_absent": "", "launched": 97, "in_orbit": null, "licensed": null, "filed": null, "announced": 85, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "none", "first_launch": "", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "", "n_regulatory": 3, "n_itu": 0, "n_sources": 2, "has_primary": "yes", "n_discrepancies": 0, "supersedes": "", "superseded_by": "", "notes": "Split from globalstar-c3 so that the operational system and the planned next-generation system are not conflated: they have different satellite counts, different licensing administrations and different regulatory states. The deck's \"~85 planned / 97 launched\" belongs here and its \"1,946 (C-3) / 0\" belongs on globalstar-c3. Provenance gap: no file numbers for either the HIBLEO-4 licence or the HIBLEO-X market access grant, and no orbital parameters. Exhibit A to the Amazon transfer application lists every Globalstar authorisation and would close most of this in one read. If the Amazon transaction completes, this system and Amazon Leo come under one owner, alongside Amazon's stated intention to file for a global direct-to-device system. Worth tracking as a concentration question rather than only a technical one.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "guowang-gw-2", "name": "Guowang GW-2", "family": "guowang", "aka": "GW-2; Guowang high shell; Xingwang; SatNet", "operator": "China Satellite Network Group Co., Ltd. (China SatNet)", "parent": "State-owned, established April 2021", "country": "CN", "jurisdiction": "CN", "system_class": "broadband", "status": "deploying", "status_detail": "The higher of Guowang's two ITU networks, and the one being deployed. A notification (Part I-S) received 7 November 2025 declares 1,728 satellites, roughly a quarter of the figure in the earlier coordination request.", "services": "broadband; government-secure", "orbit_regimes": "LEO", "dual_use": "unknown", "filing_authority": "other", "filing_number": "Part I-S (notice ID 125500219); CR/C 5486; API/A 12664", "filing_call_sign": "", "filing_absent": "", "launched": 216, "in_orbit": null, "licensed": 1728, "filed": 6912, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "unknown", "first_launch": "2024-12", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "China Aerospace Science and Technology Corporation (CASC)", "n_regulatory": 0, "n_itu": 1, "n_sources": 4, "has_primary": "yes", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance upgraded 2026-07-29 from trade press to the ITU filing and publication. See scripts/itu_query.sh. Provenance gap: the CR/C figure of 6,912 could not be confirmed. Its publication, BR IFIC 2996 of May 2023, is outside the roughly eighteen-month window in which BR IFICs are downloadable without a subscription. Closing it needs the BR IFIC DVD-ROM or a TIES account.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "guowang-gw-a59", "name": "Guowang GW-A59", "family": "guowang", "aka": "GW-A59; Guowang low shell; 国网", "operator": "China Satellite Network Group Co., Ltd. (China SatNet)", "parent": "State-owned, established April 2021", "country": "CN", "jurisdiction": "CN", "system_class": "broadband", "status": "filed", "status_detail": "The lower of Guowang's two ITU networks. Coordination request on file and modified three times, most recently published in BR IFIC 3055 in September 2025. No notification (Part I-S) has been filed for this network, so nothing under it has been brought into use in the ITU sense.", "services": "broadband; government-secure", "orbit_regimes": "VLEO; LEO", "dual_use": "unknown", "filing_authority": "other", "filing_number": "CR/C 5448 (notice ID 120520170); API/A 12666", "filing_call_sign": "", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": null, "filed": 6080, "announced": null, "n_shells": 3, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "unknown", "first_launch": "", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "", "n_regulatory": 0, "n_itu": 1, "n_sources": 4, "has_primary": "yes", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance upgraded 2026-07-29 from trade press to the ITU filing and publication. See scripts/itu_query.sh. Launch reporting does not split Guowang launches between the two networks, so counts.launched is recorded on guowang-gw-2 as a family-level figure rather than duplicated here.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "honghu-3", "name": "Honghu-3", "family": "honghu", "aka": "Honghu; 鸿鹄-3", "operator": "Shanghai Lanjian Hongqing Technology Company (Hongqing Technology)", "parent": "LandSpace holds 48 per cent", "country": "CN", "jurisdiction": "CN", "system_class": "broadband", "status": "filed", "status_detail": "Advance publication information received by the ITU on 8 September 2023 and published 31 October 2023, with comments (API/B) published April 2024. No coordination request has been filed. Nothing launched. The third Chinese constellation of more than 10,000 satellites to be filed, after Guowang and Qianfan.", "services": "broadband", "orbit_regimes": "LEO", "dual_use": "unknown", "filing_authority": "other", "filing_number": "API/A 13448 (notice ID 123545296)", "filing_call_sign": "", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": null, "filed": 10000, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "unknown", "first_launch": "", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "LandSpace", "n_regulatory": 0, "n_itu": 1, "n_sources": 4, "has_primary": "yes", "n_discrepancies": 2, "supersedes": "", "superseded_by": "", "notes": "Provenance partially upgraded 2026-07-29: the ITU filing identity, stage and dates now come from the Space Network List. The declared satellite count does not, because it lives in BR IFIC 3008 (October 2023), which is outside the roughly eighteen-month window in which BR IFICs can be downloaded without a subscription. Closing that needs the BR IFIC DVD-ROM or a TIES account. This is the clearest instance in the registry of the retention window blocking an otherwise easy provenance upgrade.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "iridium-next", "name": "Iridium NEXT", "family": "iridium", "aka": "Iridium Certus; Iridium second generation", "operator": "Iridium Constellation LLC", "parent": "Iridium Communications Inc. (acquisition by Rocket Lab Corporation announced 29 June 2026, ~USD 8.0bn, subject to FCC licence transfer consent; expected to close mid-2027)", "country": "US", "jurisdiction": "US", "system_class": "direct-to-device", "status": "operational", "status_detail": "Replacement constellation complete since 2019 and in commercial service. One of the two original 1990s LEO operators still flying.", "services": "voice; messaging; iot; direct-to-device", "orbit_regimes": "LEO", "dual_use": "dual", "filing_authority": "FCC", "filing_number": "SAT-MOD-20131227-00148", "filing_call_sign": "S2110", "filing_absent": "", "launched": 75, "in_orbit": null, "licensed": 81, "filed": 81, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "L; Ka", "isl": "rf", "first_launch": "", "service_start": "1998", "target_completion": "", "target_completion_kind": "", "launch_providers": "SpaceX", "n_regulatory": 1, "n_itu": 0, "n_sources": 3, "has_primary": "yes", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: the shell geometry on this record is sourced entirely to the constellation-code draft, not to the filing. The Iridium NEXT engineering statement is public and would give the authorised altitude, inclination and plane structure directly; reading it would move three code_assumptions from assumed to exact. This is the clearest single provenance upgrade available in the registry right now. Project Stardust, Iridium's announced direct-to-device layer, has no authorisation identified and no satellite count and is therefore not recorded. The deck notes it as \"plus unknown number\".", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "iris2", "name": "IRIS2", "family": "iris2", "aka": "IRIS²; Infrastructure for Resilience, Interconnectivity and Security by Satellite; EU Secure Connectivity Programme", "operator": "SpaceRISE consortium (SES, Eutelsat, Hispasat)", "parent": "European Commission (concession holder)", "country": "EU", "jurisdiction": "EU", "system_class": "government-military", "status": "licensed", "status_detail": "A 12-year concession contract was signed with the European Commission on 16 December 2024, implemented with ESA support. Critical design review planned for early 2028 and launches for 2029-2030. Nothing launched.", "services": "government-secure; broadband", "orbit_regimes": "LEO; MEO", "dual_use": "dual", "filing_authority": "EUSPA", "filing_number": "", "filing_call_sign": "", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": null, "filed": null, "announced": 290, "n_shells": 3, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "optical-planned", "first_launch": "", "service_start": "", "target_completion": "2030", "target_completion_kind": "operator-target", "launch_providers": "", "n_regulatory": 1, "n_itu": 0, "n_sources": 2, "has_primary": "no", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: no primary source. The concession contract itself, the Commission's programme documentation and the member state ITU filings that will carry the spectrum have none of them been consulted. IRIS2 is the registry's worked example of a system that does not fit the filing-centred model: it is a publicly procured programme whose defining instrument is a concession contract, whose spectrum will come through member state administrations, and whose satellite count is a design target rather than an authorised ceiling. Worth discussing whether the schema should carry a distinct instrument type for procured systems.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "logos-space", "name": "Logos Space", "family": "logos-space", "aka": "Logos Space Services, Inc.", "operator": "Logos Space Services, Inc.", "parent": "Logos Space Services, Inc.", "country": "US", "jurisdiction": "US", "system_class": "broadband", "status": "licensed", "status_detail": "Granted by the FCC on 30 January 2026 for 4,178 satellites in S-, Ka-, V- and E-band, together with a waiver of the processing round rules for a list of higher bands, conditioned on participating in a future processing round. Nothing launched.", "services": "broadband; government-secure; relay", "orbit_regimes": "LEO", "dual_use": "dual", "filing_authority": "FCC", "filing_number": "SAT-LOA-20241030-00243 and SAT-AMD-20250328-00084", "filing_call_sign": "", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": 4178, "filed": 4178, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "S; Ka; V; E", "isl": "rf-planned", "first_launch": "", "service_start": "", "target_completion": "2035", "target_completion_kind": "regulatory-milestone", "launch_providers": "", "n_regulatory": 2, "n_itu": 0, "n_sources": 4, "has_primary": "yes", "n_discrepancies": 2, "supersedes": "", "superseded_by": "", "notes": "Provenance upgraded 2026-07-29. The grant stamp itself is not a published document with a DA number, but the Space Bureau restates its terms in DA 26-552, which is citable and is used here. Provenance gap: the orbital shells are still unknown. The grant stamp and the underlying application would give them.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "lynk-global", "name": "Lynk Global", "family": "lynk-global", "aka": "Lynk Towers; Lynk the Everywhere Network", "operator": "Lynk Global, Inc.", "parent": "Lynk Global Holdings; SES investment and MEO-relay partnership reported", "country": "US", "jurisdiction": "US", "system_class": "direct-to-device", "status": "deploying", "status_detail": "Licensed for ten satellites under the FCC's streamlined small space station process and operating commercially in partner markets. The 2,000-satellite figure in circulation has no authorisation behind it.", "services": "direct-to-device; messaging", "orbit_regimes": "LEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "SAT-LOA-20210511-00064", "filing_call_sign": "S3087", "filing_absent": "", "launched": 12, "in_orbit": null, "licensed": 10, "filed": 10, "announced": 2000, "n_shells": 0, "constellation_code": "", "constellation_code_status": "", "spectrum": "L; S; Ka", "isl": "none", "first_launch": "2022", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "SpaceX", "n_regulatory": 2, "n_itu": 0, "n_sources": 3, "has_primary": "yes", "n_discrepancies": 2, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: the April 2025 modification is recorded from trade press; the grant itself has not been retrieved, so it has no file number here. Provenance gap: the 12-launched figure exceeds the 10 authorised and the discrepancy has not been resolved against ELS records. Note for the group: DA 22-969 resolves a petition to deny from Iridium and comments from Kuiper and the NRAO. The direct-to-device band is contested by incumbents and radio astronomy, which is a spectrum-governance thread worth following in its own right.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "orbital-compute", "name": "Orbital Compute", "family": "orbital-compute", "aka": "Orbital; Orbital Compute, Inc.", "operator": "Orbital Compute, Inc.", "parent": "Orbital Compute, Inc.", "country": "US", "jurisdiction": "US", "system_class": "orbital-compute", "status": "filed", "status_detail": "Application filed with the FCC in 2026 for up to 100,000 satellites totalling 10 GW of compute. No grant, nothing launched, and the company is at pre-seed funding scale.", "services": "orbital-compute", "orbit_regimes": "LEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "", "filing_call_sign": "", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": null, "filed": 100000, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "external", "first_launch": "", "service_start": "", "target_completion": "2028", "target_completion_kind": "operator-target", "launch_providers": "", "n_regulatory": 1, "n_itu": 0, "n_sources": 2, "has_primary": "no", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: no primary source, no file number, no precise filing date. Reading the application is the whole task on this record.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "project-suncatcher", "name": "Project Suncatcher", "family": "project-suncatcher", "aka": "Google Project Suncatcher", "operator": "Google LLC", "parent": "Alphabet Inc.", "country": "US", "jurisdiction": "US", "system_class": "orbital-compute", "status": "announced", "status_detail": "A research programme, announced November 2025, to put Google TPUs in orbit. Two prototype satellites are to be built and operated by Planet Labs for an in-orbit demonstration in early 2027. No constellation size has been stated and no filing has been identified.", "services": "orbital-compute", "orbit_regimes": "LEO", "dual_use": "civil", "filing_authority": "", "filing_number": "", "filing_call_sign": "", "filing_absent": "No filing identified. The programme is presented as research with a two-satellite demonstration, and the demonstration satellites are to be built and operated by Planet Labs, so any near-term spectrum authority would most likely sit under Planet's existing licences rather than a new Google filing. There is nothing yet to file for: no constellation size has been announced.", "launched": null, "in_orbit": null, "licensed": null, "filed": null, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "optical", "first_launch": "2027", "service_start": "", "target_completion": "", "target_completion_kind": "operator-target", "launch_providers": "Planet Labs", "n_regulatory": 0, "n_itu": 0, "n_sources": 3, "has_primary": "no", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Included with an empty `counts` block on purpose. An announced programme from an operator of this size, with no stated constellation size, is a real category and the honest representation of it is absence. Writing a speculative number here would corrupt exactly the aggregate the registry is meant to make trustworthy. Provenance gap: the Google Research post describing the system design has been cited but not read in detail; it would give the cluster geometry and the power and thermal assumptions.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "qianfan", "name": "Qianfan", "family": "qianfan", "aka": "Thousand Sails; G60 Starlink; Spacesail; 千帆", "operator": "Shanghai Spacecom Satellite Technology (SSST) / Spacesail", "parent": "Backed by the Shanghai Municipal People's Government; Chinese Academy of Sciences involvement reported", "country": "CN", "jurisdiction": "CN", "system_class": "broadband", "status": "deploying", "status_detail": "Launching production satellites since August 2024; regional service targeted for around 2026 and global service around 2030. Well short of the announced phase targets.", "services": "broadband", "orbit_regimes": "LEO", "dual_use": "unknown", "filing_authority": "", "filing_number": "", "filing_call_sign": "", "filing_absent": "No filing reference established, and not for want of looking. The ITU Space Network List was queried on 2026-07-29 for QIANFAN, SSST, SPACESAIL, STARNET, THOUSANDSAILS, G60-STARLINK, CHINA-LEO, CHINASAT-LEO, SSST-GW, QIANFAN-1 and QF-1, all returning nothing; the SNL name search is exact, not substring, so a name we have not guessed will not surface. Scanning the non-GSO tables of six downloaded BR IFICs for Chinese networks turned up 100 or so names, none obviously this system. A filing almost certainly exists under a designation we do not know. China's national authorisations are separately not published in any docket comparable to the FCC's ICFS.", "launched": 239, "in_orbit": null, "licensed": null, "filed": null, "announced": 15000, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "unknown", "first_launch": "2024-08-06", "service_start": "", "target_completion": "2030", "target_completion_kind": "operator-target", "launch_providers": "China Aerospace Science and Technology Corporation (CASC)", "n_regulatory": 0, "n_itu": 1, "n_sources": 3, "has_primary": "no", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: this record still has no primary source, and after a systematic ITU search it is now the only major system in the registry in that position. See filing_absent for what was tried. The most likely routes in are: a Chinese-language source that gives the ITU designation directly; a full SNL export filtered by administration, which the ITU server currently returns a 500 for on date-range queries; or somebody in the group with access to the BR IFIC DVD-ROM, which would allow scanning publications outside the eighteen-month download window when the filing was most likely made. ASK THE LIST. This is a good first question to put to space@irtf.org once the registry is announced: a working constellation of 239 satellites whose ITU identity we cannot find is exactly the kind of gap a group is better at closing than an individual. This record is the registry's worked example of the non-US jurisdiction problem: for FCC-licensed systems the filing, the geometry, the milestones and the spectrum are all in a public docket, and for most others they are not. Any aggregate satellite count that treats a Chinese or Russian figure as equivalent evidence to an FCC grant is comparing unlike things, and the registry should make that visible rather than smooth it over.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "rassvet", "name": "Rassvet", "family": "rassvet", "aka": "Dawn; Bureau 1440 Rassvet; RASSVET-1", "operator": "Bureau 1440", "parent": "X Holding / IKS Holding", "country": "RU", "jurisdiction": "RU", "system_class": "broadband", "status": "deploying", "status_detail": "First 16 production satellites launched 23 March 2026 after an experimental phase from 2023. Of the three ITU networks filed in 2022-2023, two were suppressed at the operator's own administration's request in December 2025; only RASSVET-1 remains on file.", "services": "broadband; direct-to-device", "orbit_regimes": "LEO", "dual_use": "unknown", "filing_authority": "other", "filing_number": "CR/C 5975 (notice ID 123520004); API/A 13240", "filing_call_sign": "", "filing_absent": "", "launched": 22, "in_orbit": null, "licensed": null, "filed": 1350, "announced": 383, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "unknown", "first_launch": "2023", "service_start": "", "target_completion": "2030", "target_completion_kind": "operator-target", "launch_providers": "Roscosmos", "n_regulatory": 0, "n_itu": 3, "n_sources": 6, "has_primary": "yes", "n_discrepancies": 2, "supersedes": "", "superseded_by": "", "notes": "Provenance upgraded 2026-07-29 from encyclopaedia and press to the ITU filings and publication. See scripts/itu_query.sh. Reporting on this system is heavily coloured by the war in Ukraine and by its dual-use potential, in both directions. The ITU record is the one part of the picture that is neutral and checkable, which is most of why this round of work was worth doing.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "reliance-jio", "name": "Reliance Jio LEO constellation", "family": "reliance-jio", "aka": "Jio sovereign LEO constellation; Jio Space", "operator": "Jio Platforms Limited", "parent": "Reliance Industries Limited", "country": "IN", "jurisdiction": "IN", "system_class": "broadband", "status": "licensed", "status_detail": "IN-SPACe approved the proposal on 17 July 2026, four days before the IETF 126 session, judging it technically sound. The approval enables the Government of India to support the ITU filings and orbital rights the system needs; those filings are not yet made. Nothing launched.", "services": "broadband; direct-to-device", "orbit_regimes": "LEO", "dual_use": "dual", "filing_authority": "IN-SPACe", "filing_number": "", "filing_call_sign": "", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": 1600, "filed": 1600, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "unknown", "first_launch": "", "service_start": "", "target_completion": "2029", "target_completion_kind": "operator-target", "launch_providers": "Not disclosed", "n_regulatory": 1, "n_itu": 0, "n_sources": 3, "has_primary": "no", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: no primary source and no citable docket. IN-SPACe authorisations are not published in a form comparable to FCC ICFS. Carlos Martinez-Cagnazzo asked at IETF 126 who the proper authority is when a company files, and Dan York used exactly this system as the example: the Indian space agency approves, then the filing goes to the ITU. This record captures that chain at the moment the first step completed and the second had not yet begun, which makes it a useful teaching case for the draft.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "spacex-orbital-data-center", "name": "SpaceX Orbital Data Center System", "family": "spacex-orbital-compute", "aka": "AI1; Starmind", "operator": "Space Exploration Holdings, LLC", "parent": "Space Exploration Technologies Corp. (SpaceX)", "country": "US", "jurisdiction": "US", "system_class": "orbital-compute", "status": "filed", "status_detail": "Application filed 30 January 2026, accepted for filing 4 February 2026. No grant. This single application is the largest contributor by far to every circulating aggregate of planned satellites.", "services": "orbital-compute", "orbit_regimes": "LEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "SAT-LOA-20260108-00016", "filing_call_sign": "S00798", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": null, "filed": 1000000, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "optical", "isl": "optical", "first_launch": "", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "", "n_regulatory": 2, "n_itu": 0, "n_sources": 3, "has_primary": "yes", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Reported in the press as connected to the SpaceX/xAI merger. The application itself is for a communications authorisation; the compute payload is not what the FCC is licensing, which is worth remembering when reading the filing as evidence about data-centre capacity. Provenance gap: the application narrative and technical attachment (Attachment A) are cited in DA 26-113 but have not been read directly. They would give the shell structure, the satellite versions and the TT&C bands.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "spinlaunch-meridian", "name": "SpinLaunch Meridian Space", "family": "spinlaunch", "aka": "Meridian Space", "operator": "SpinLaunch, Inc.", "parent": "SpinLaunch, Inc.", "country": "US", "jurisdiction": "US", "system_class": "broadband", "status": "filed", "status_detail": "FCC application for roughly 1,200 satellites in Ka-, Ku- and V-band. 280 satellites contracted from Kongsberg NanoAvionics in April 2025. Nothing launched.", "services": "broadband; backhaul; government-secure", "orbit_regimes": "LEO", "dual_use": "dual", "filing_authority": "FCC", "filing_number": "", "filing_call_sign": "", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": null, "filed": 1200, "announced": 280, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "Ku; Ka; V", "isl": "unknown", "first_launch": "", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "SpinLaunch", "n_regulatory": 1, "n_itu": 0, "n_sources": 2, "has_primary": "no", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: no primary source, no file number, no filing date. Worth noting for anyone modelling this system: repeating ground tracks are unusual among the constellations in this registry and change the contact pattern seen by a fixed ground station substantially. It is a good test case for the ground-station elements added in draft-piraux-space-constellation-code-02.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "starcloud", "name": "Starcloud", "family": "starcloud", "aka": "Lumen Orbit", "operator": "Starcloud, Inc.", "parent": "Starcloud, Inc. (independent; Series A March 2026)", "country": "US", "jurisdiction": "US", "system_class": "orbital-compute", "status": "filed", "status_detail": "One demonstrator on orbit (Starcloud-1, November 2025). The 88,000-satellite system is an FCC application accepted for filing in March 2026; no grant.", "services": "orbital-compute", "orbit_regimes": "LEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "SAT-LOA-20260202-00073", "filing_call_sign": "", "filing_absent": "", "launched": 1, "in_orbit": null, "licensed": null, "filed": 88000, "announced": null, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "Ka; optical", "isl": "optical", "first_launch": "2025-11-02", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "", "n_regulatory": 1, "n_itu": 0, "n_sources": 2, "has_primary": "no", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: this record has no primary source. Everything except the demonstrator launch rests on one trade-press report of the FCC application. The application itself (ICFS SAT-LOA-20260202-00073) is public and should be read; the accepted-for-filing public notice would also be a primary source for the date. Until then every number here is secondary and the record should be read as such. Kept in the registry despite the weak provenance because orbital data centre filings are a large and fast-growing share of the aggregate satellite count, and because this system as filed depends entirely on other operators' optical crosslinks - which is exactly the kind of coupling the group should be able to see.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "starlink-gen1", "name": "Starlink Gen1", "family": "starlink", "aka": "SpaceX NGSO Satellite System (first generation); Starlink Ku/Ka", "operator": "Space Exploration Holdings, LLC", "parent": "Space Exploration Technologies Corp. (SpaceX)", "country": "US", "jurisdiction": "US", "system_class": "broadband", "status": "operational", "status_detail": "Fully deployed and in commercial service. The shells recorded here are the authorised configuration after the April 2021 third modification.", "services": "broadband", "orbit_regimes": "LEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "SAT-MOD-20200417-00037", "filing_call_sign": "S2983", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": 4408, "filed": 4409, "announced": null, "n_shells": 5, "constellation_code": "", "constellation_code_status": "", "spectrum": "Ku; Ka", "isl": "optical", "first_launch": "2019-05-24", "service_start": "2020-10", "target_completion": "", "target_completion_kind": "", "launch_providers": "SpaceX", "n_regulatory": 4, "n_itu": 3, "n_sources": 5, "has_primary": "yes", "n_discrepancies": 0, "supersedes": "", "superseded_by": "", "notes": "The ITU networks behind Starlink are notified by Norway, not the United States. SpaceX holds a US licence from the FCC and the international filings that carry its spectrum are made by the Norwegian administration under the names STEAM-1, STEAM-2 and STEAM-2B. Nothing improper about that, and it is common practice, but it means a reader looking for Starlink under \"USA\" in ITU records will not find it, and any jurisdiction-by-jurisdiction tally built from ITU data will attribute the largest constellation in orbit to Norway. This is the single most consequential thing found in the ITU pass. Provenance gap: two later modifications (SAT-MOD-20230215-00036, granted 2024-08-16, and SAT-MOD-20241104-00251, granted 2025-03-17) are recorded from a citation in DA 26-113 but have not been read. The authorised geometry may have changed since FCC 21-48, so the shells here are the 2021 configuration and are marked as such by their src. counts.launched is deliberately empty on this record: launch reporting does not distinguish Gen1 from Gen2 spacecraft, so a per-authorisation launched figure cannot be sourced. The family-level figure is on starlink-gen2.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "starlink-gen2", "name": "Starlink Gen2", "family": "starlink", "aka": "SpaceX Gen2 NGSO Satellite System; Starlink V2 / V3", "operator": "Space Exploration Holdings, LLC", "parent": "Space Exploration Technologies Corp. (SpaceX)", "country": "US", "jurisdiction": "US", "system_class": "broadband", "status": "deploying", "status_detail": "Deploying under a partial grant. Authorised for 15,000 of the 29,988 satellites requested; the Commission has expressly deferred action on the remainder. Carries the direct-to-cell (supplemental coverage from space) service.", "services": "broadband; direct-to-device", "orbit_regimes": "VLEO; LEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "SAT-LOA-20200526-00055", "filing_call_sign": "S2992/3069", "filing_absent": "", "launched": 12612, "in_orbit": null, "licensed": 15000, "filed": 29988, "announced": null, "n_shells": 4, "constellation_code": "", "constellation_code_status": "", "spectrum": "Ku; Ka; V; W", "isl": "optical", "first_launch": "", "service_start": "", "target_completion": "2031-12-01", "target_completion_kind": "regulatory-milestone", "launch_providers": "SpaceX", "n_regulatory": 3, "n_itu": 0, "n_sources": 3, "has_primary": "yes", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "The ITU networks behind Starlink (STEAM-1, STEAM-2, STEAM-2B) are notified by Norway, not the United States; the shells declared in the most recent STEAM-2 notification match the Gen1 authorisation rather than this one, so the ITU detail is recorded on starlink-gen1. No ITU network has yet been identified that corresponds specifically to the Gen2 authorisation, which is itself worth resolving. This record is the registry's worked example of an envelope authorisation. Three of its four shell entries are geometry_kind envelope or unknown and emit no constellation code, because DA 26-36 bounds the geometry rather than fixing it and lets SpaceX redistribute satellites between shells. Any simulator that wants a concrete Gen2 topology must choose one point in that feasible set, and should say which.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "starlink-gen3", "name": "Starlink Gen3", "family": "starlink", "aka": "SpaceX third-generation Starlink system", "operator": "Space Exploration Holdings, LLC", "parent": "Space Exploration Technologies Corp. (SpaceX)", "country": "US", "jurisdiction": "US", "system_class": "broadband", "status": "filed", "status_detail": "Application filed 6 July 2026; no grant. Nothing launched under this authorisation. Deployment is predicated on Starship reaching operational cadence at roughly 2,000 kg per satellite.", "services": "broadband", "orbit_regimes": "VLEO", "dual_use": "civil", "filing_authority": "FCC", "filing_number": "SAT-LOA-20260630-00264", "filing_call_sign": "", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": null, "filed": 100000, "announced": null, "n_shells": 2, "constellation_code": "", "constellation_code_status": "", "spectrum": "Ku; Ka; V; E; W; D", "isl": "", "first_launch": "", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "SpaceX", "n_regulatory": 1, "n_itu": 0, "n_sources": 2, "has_primary": "no", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: this record has no primary source. The file number, satellite count, altitude bands and spectrum all come from trade press. The application is public in ICFS and should be read; doing so would also settle whether the request is for a genuinely new system or an amendment of the Gen2 authorisation, which changes how the 100,000 should be aggregated.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "starshield", "name": "Starshield", "family": "starshield", "aka": "NRO proliferated architecture (SpaceX-built element)", "operator": "Space Exploration Technologies Corp. (SpaceX)", "parent": "Space Exploration Technologies Corp. (SpaceX)", "country": "US", "jurisdiction": "US", "system_class": "government-military", "status": "deploying", "status_detail": "Satellites are launching regularly on dedicated NRO missions, but the system has no public authorisation, no published constellation size and no published geometry. Status is inferred from launch reporting alone.", "services": "government-secure; military; relay", "orbit_regimes": "LEO", "dual_use": "military", "filing_authority": "", "filing_number": "", "filing_call_sign": "", "filing_absent": "No public FCC or ITU filing identifies this system. It is procured and operated under US government contracts, principally for the National Reconnaissance Office's proliferated architecture, and US federal government spectrum use is coordinated through NTIA rather than licensed by the FCC, so no ICFS docket exists to point at. Everything in this record therefore rests on launch reporting and catalogue observation. This is a structural provenance limit, not an oversight, and it applies to classified systems in every jurisdiction.", "launched": 245, "in_orbit": null, "licensed": null, "filed": null, "announced": 1600, "n_shells": 0, "constellation_code": "", "constellation_code_status": "", "spectrum": "", "isl": "optical", "first_launch": "", "service_start": "", "target_completion": "", "target_completion_kind": "", "launch_providers": "", "n_regulatory": 0, "n_itu": 0, "n_sources": 1, "has_primary": "no", "n_discrepancies": 0, "supersedes": "", "superseded_by": "", "notes": "Kept in the registry with almost every field empty on purpose. A government constellation of this size is a real consumer of orbital shells and spectrum and a real contributor to conjunction and coordination load, and omitting it because it is undocumented would understate the picture in exactly the direction that is hardest to notice. What the record contributes is the fact, stated in filing_absent, that no public filing exists. Possible future primary sources: the UN Register of Objects Launched into Outer Space (treaty-registry) gives launch-by-launch registrations with orbital parameters, and NTIA spectrum certification records are partially public. Neither has been checked.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" }, { "slug": "telesat-lightspeed", "name": "Telesat Lightspeed", "family": "telesat-lightspeed", "aka": "Telesat LEO", "operator": "Telesat Canada", "parent": "Telesat Corporation", "country": "CA", "jurisdiction": "CA; US", "system_class": "broadband", "status": "licensed", "status_detail": "Authorised by ISED in Canada, with US market access granted separately by the FCC. 198 satellites contracted from MDA in August 2023, down from an earlier 298. Telesat has stated it will not meet the current ISED milestones and intends to seek an amendment. Nothing launched.", "services": "broadband; backhaul; government-secure", "orbit_regimes": "LEO", "dual_use": "dual", "filing_authority": "ISED", "filing_number": "", "filing_call_sign": "", "filing_absent": "", "launched": null, "in_orbit": null, "licensed": null, "filed": null, "announced": 198, "n_shells": 1, "constellation_code": "", "constellation_code_status": "", "spectrum": "Ka; V", "isl": "optical", "first_launch": "", "service_start": "", "target_completion": "2028", "target_completion_kind": "operator-target", "launch_providers": "", "n_regulatory": 2, "n_itu": 0, "n_sources": 4, "has_primary": "yes", "n_discrepancies": 1, "supersedes": "", "superseded_by": "", "notes": "Provenance gap: this record has no usable primary source for its counts. The FCC market access grant is cited by landing page rather than by document number and has not been read, and the ISED authorisation has not been located at all. This record is the registry's worked example of the non-US-but-Western jurisdiction problem, which sits between the FCC case and the Chinese case: the authorisation certainly exists and is not secret, but it is not published in a form that can be cited, so the best available evidence is the operator's own reporting. Any contributor with ISED experience could close this quickly.", "added": "2026-07", "verified": "2026-07-29", "verified_age_months": 1, "stale": "no" } ]