Skip to content

Status

Service status

What Trace would report about its own availability, and how it would report it.

This page is illustrative. It is not connected to real monitoring.

Nothing below is measured. No uptime probe, health check, or alerting system feeds this page, and the component states are placeholders showing the structure the page would take. Do not use it to determine whether the service is currently available. A live status page, backed by external monitoring, is planned.

Components

What would be reported.

Each component would be probed independently, because a working application in front of a failing measurement queue is a different situation from a full outage.

Component states

Placeholder values. No component is currently being monitored.

  • Application

    The authenticated workspace, dashboards, and reports.

    Not monitored

  • API

    Programmatic access to portfolios, measurements, and exports.

    Not monitored

  • Ingestion

    Identifier resolution, metadata retrieval, and document processing.

    Not monitored

  • Measurement runs

    Scheduled and on-demand retrieval, citation, and fidelity measurement.

    Not monitored

  • Simulation

    Synthetic stakeholder panels, running sandboxed with no external egress.

    Not monitored

  • Exports

    CSV, JSON, and report generation.

    Not monitored

Definitions

What each state would mean.

Operational
Responding normally, within the stated latency budget.
Degraded
Available but slower or partially impaired — for example, one bibliographic provider failing while others answer.
Outage
Unavailable. An incident entry is opened with a timestamp and updated until it is resolved.
Maintenance
Planned work, announced in advance with a start and expected end time.

History

Incident history.

No incident history

No incidents are recorded, because no monitoring exists to record them. An empty history here means the instrument is absent, not that the service has been flawless — and those two things should never look the same.

If something is wrong

Report it directly.

Because this page reports nothing, the reliable route is email. hello@trace.science for availability problems, and security@trace.science for anything with a security dimension. Disclosure expectations are set out on the security page.