Status API response latency
Some status API responses were slower than the publication target. The public website and records archive remained available.
Read incident record →The public record of system availability.
Current service state, maintenance notices, and resolved incidents — published in plain language and kept available after the moment passes.
All monitored services operational
Published
Current operational status
View all services →| Service | Endpoint | Status | Last published |
|---|---|---|---|
| Public website | / | Operational | Jul 10, 16:00 UTC |
| Status page | /status/ | Operational | Jul 10, 16:00 UTC |
| Status API | /status.json | Operational | Jul 10, 16:00 UTC |
| Records archive | /resources/ | Operational | Jul 10, 16:00 UTC |
| Contact page | /contact/ | Operational | Jul 10, 16:00 UTC |
30-day availability
Read methodology →Public website
30 daily readings
100%Status page
30 daily readings
100%Status API
30 daily readings
99.90%Records archive
30 daily readings
100%Contact page
30 daily readings
100%Latest incident and maintenance
View incident history →No maintenance scheduled
There is no published maintenance window. Planned work will appear here before its stated start time and will remain in the archive after completion.
How maintenance is published →Public record archive
Search all records →| Date (UTC) | Type | Service | Summary | State |
|---|---|---|---|---|
| Jul 10, 16:00 | Status | Public website | Published snapshot refreshed. | Published |
| Jul 08, 09:30 | Notice | Records archive | Monthly archive index published. | Published |
| Jun 22, 10:02 | Incident | Status API | Response latency returned to normal. | Resolved |
| Jun 12, 16:10 | Maintenance | Status page | Accessibility update completed. | Completed |
Status signal definitions
Open signal guide →Operational
The service is performing normally for visitors.
Degraded
The service works, but some requests may be slower or incomplete.
Disruption
The service is partially or fully unavailable.
Maintenance
Planned work is in progress and expected impact is stated.
No data
No reliable published reading exists for that interval.
Publication standard
Read the full method →Timestamp
Every record uses UTC with minute precision.
Affected surface
The public page or endpoint is named directly.
Public impact
The record says what a visitor may have experienced.
Resolution
Closed records state what restored normal operation.
Follow-up
Preventive work is included when it adds useful context.
Machine-readable endpoints
Open data notes →/status.jsonPublished overall status and service states.JSON/healthLightweight availability response for simple checks.text/plain/sitemap.xmlIndex of public journal pages.XML