Service status
Everything we check is answering normally.
Checked from our website's server at , at most once a minute. Reload for a newer answer.
API api.taghistorian.com
Operational. Up, and every dependency it checks is healthy.
- Account database (sign-in, API keys, tag definitions): healthy
- Measurement storage: healthy
- Measurement storage capacity: healthy
- Write-ahead log recovery after a restart: healthy
Explorer app.taghistorian.com
Operational. Its pages are being served.
This page shows what our website's server sees at the moment it asks, and keeps no history. It is not an uptime record: the self-service plans carry no uptime SLA, and we do not publish an availability figure until we have measured one worth publishing - see where your data lives.
The API's answer comes from its readiness check, which is healthy only while its database, its measurement storage and its write-ahead log recovery all are. A component with a failing check is normally taken out of service by the platform, so a problem there usually shows up here as the API not answering at all rather than as a list with one line in red. The long-term archive is not part of that check: the API keeps answering without it, and we watch it separately.
The page runs on the same Azure platform in Sweden Central as the service itself. If it does not load at all, the outage is wider than one component. Questions: support@taghistorian.com.