Skip to content

Ecosystem: Public status page + incident communication #818

Description

@joelpeace48-cell

Context

For a platform serving thousands of users and partners, there is no public status page communicating
uptime, incidents, and maintenance windows.

Scope

  • Status page fed by health/SLO checks (API, RPC, indexer, contracts).
  • Incident lifecycle (investigating → identified → resolved) + subscribe for updates.
  • Scheduled-maintenance notices.

Acceptance criteria

  • Real-time component status is public; incidents and maintenance are communicated to subscribers.

Verification

  • A simulated dependency outage flips the relevant component to degraded on the status page.

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programarea: devopsDevOps, CI/CD, deploymentdifficulty: easySmall scopegrowthDrives user acquisition, retention, or viralityobservabilityLogs, metrics, tracing

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions