Every 2–3 min
Data sources · Trust center
Public inputs, clear limits.
The tracker uses public catalog data and local assets. It is an investigative and educational tool, not an authoritative sensor network. We show you where each input comes from, how often it updates, how we use it, and where the limits are.
Live source status
Daily ~00:00 UTC
Multiple times daily
As available
As available
Irregular releases
3× daily
Data sources
Usage in SkyLens
Live Earth-orbiting public objects are loaded through the local server and propagated in the browser. Powers orbit propagation, visibility passes, and conjunction screening.
Limitations
⚠ Not navigation-grade.TLE accuracy degrades over time. Not all objects are maneuver-aware.
Usage in SkyLens
Investigation checks use SATCAT metadata for cross-catalog comparison, launch dates, and decay records — object attributes, IDs, classifications, and metadata baselines.
Limitations
⚠ May be delayed.Catalog updates can lag real-world changes; not authoritative.
Usage in SkyLens
Near-Earth asteroid close approaches come from the JPL CNEOS CAD API, with trajectory context from JPL SBDB orbit elements cached by the local server. Used for NEO discovery, close-approach screening, and characteristics.
Limitations
⚠ Model-based.Orbits and physical properties carry uncertainty.
Usage in SkyLens
The Visuals page uses official NASA Eyes iframe app URLs for Solar System, Earth, and Exoplanets. NASA Live and Spot the Station are linked out because their pages block external framing.
Limitations
⚠ Visual reference only.Not for measurement or operational decisions.
Usage in SkyLens
Blog hero imagery is fetched live from images-api.nasa.gov using per-topic queries. Each post is matched to a thematically relevant NASA image (Apollo, Artemis, ISS, Mars, Hubble, Webb, aviation archives) with category-based fallbacks for topics outside NASA's collection.
Limitations
⚠ Illustrative only.Image time/location may not match event timelines.
Usage in SkyLens
The UAP Files page links to official public sources such as the PURSUE release portal, AARO imagery, National Archives UAP records, NASA UAP study material, and ODNI/DoD public reports. It does not host classified or leaked material. Provides context for historical reports and trend exploration.
Limitations
⚠ Unverified.Reports are not validated by SkyLens; subject to observer and reporting bias.
Usage in SkyLens
538 editorial blog posts including 535 UAP-tagged analyses across 25 sub-topics — PURSUE Release 01/02/03/04 case deep-dives, FBI 62-HQ-83894 files, international historical cases, researcher profiles, AARO/UAPTF institutional analysis, nuclear-facility incursions, and contemporary news. All hedged for evidentiary care, source-attributed, and accessible at /blog.html. Feeds daily assessments, explainers, and event summaries.
Limitations
⚠ Not a primary data source.Editorial content reflects analysis and opinion.
Pipeline & local assets
Earth, planet textures, country GeoJSON, and visual reference layers are bundled locally for reliable rendering.
The public daily brief combines CelesTrak Earth-orbit records with NASA/JPL near-Earth-object context and explains candidate signals with explicit source limits.
Daily space-news posts are auto-generated by the SkyLens editorial automation 3× per day (07:00 / 13:00 / 23:00 CET) drawing on live CelesTrak satellite catalog, NASA/JPL asteroid feed, and Spaceflight News API trending stories. The schedule survives restarts via persistent state in .cache/blog-schedule.json.
Known limitations
- TLE-derived positions are estimates and become less reliable as epochs age.
- Visual satellite dots are screen-scaled and do not represent physical object size.
- Asteroid trajectory arcs are compressed visualizations from public osculating elements; use JPL SBDB or Horizons for precision ephemerides.
- Public catalog anomalies are leads only and require independent validation.
Attribution: CelesTrak (celestrak.org), NASA/JPL (nasa.gov, jpl.nasa.gov), and other public data providers. See each provider's terms for reuse.