Component status
Current health, regional availability, active notices, and maintenance information.
Public service network
Availability and resources, without unnecessary friction.
Public availability information and versioned resources.
Live summary
Checking service state
The public interface is loading current component information.
What is published
A small service with useful public interfaces
The browser pages and read-only API provide the same operational picture.
Versioned resources
Public files include versions, media types, sizes, and SHA-256 values for independent verification.
Read-only API
Stable JSON responses and an OpenAPI description support lightweight integrations.
Current components
Service overview
Component data is supplied by the same interface used by the status page.
Loading components…
Field notes
How the public service works
Short, practical explanations of static publishing, status information, and resource integrity.
Why static pages age well
How a small static publishing surface stays understandable and dependable over time.
Read articleReading service status without guesswork
A simple way to distinguish overall health, incidents, maintenance, and regional summaries.
Read articleVerifying public resources
Why versions, sizes, media types, and SHA-256 values make published files easier to check.
Read articleResource integrity
Metadata that can be checked
Every published resource can expose a stable identifier, version, size, media type, and SHA-256 digest.
Open the resource catalogService behavior
Useful even during partial outages
Static pages remain available independently. Cached public metadata can remain readable while the application process recovers.
How the service is operated