Record entry · other coverage

Starlink V3

What is happening now

Cannot measure: the record's node for this name could not be read, so its claims are not known here.

How well we know this

Cannot measure: No entity labelled "starlink-v3" in the record at 2026-11-14T23:28:43.035217+00:00. Try search_entities, or GET /api/signals..

Added 30 Sept 2026Mentions 42Sources 14Days of coverage 14

Why this name is on the record

Starlink V3 was added automatically on 30 Sept 2026 after 42 mentions across 14 sources over 14 days. 52% of that coverage came from a single subject area.

Reported alongside Starlink V3

The neighbourhood is not yet read for this page.

For developers

GET https://api.signalbureau.ai/api/registry?slug=starlink-v3

{
  "slug": "starlink-v3",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "starlink v3",
    "promotedAt": "2026-09-30",
    "category": "auto",
    "evidence": {
      "mentions": 42,
      "sources": 14,
      "days": 14,
      "concentration": 0.524,
      "standAloneShare": 0.952
    },
    "previouslyRetiredAt": "2026-10-29"
  }
}

The record behind this page, as data. The live response also carries the registry date and version.

Walk the record from Starlink V3

This name is not in the walkable record yet: the entity graph does not carry it at this cutoff.

The coverage behind it

Ask about Starlink V3Watch Starlink V3

No trend and no market price are shown because neither has been measured for Starlink V3 yet. Informational only, not advice. As of 14 Nov 2026.