Three Weeks of 100% Uptime: Meet the TimeLogic API Status Page
A time API sits underneath a lot of other systems: schedulers, billing cycles, booking flows, log pipelines. When it answers, nobody thinks about it. That is exactly how it should be, and it is also why you should be able to check it yourself instead of taking our word for it.
So we built a public status page: status.timelogicapi.com.
Monitoring started on August 28, 2026. Three weeks later, the page shows 100% uptime. Not a single red day on the bar.
What the status page shows
- Current status for the TimeLogic API monitor, with the latest status and the latest measured latency.
- 90 days of status history as a day-by-day bar, so a bad day can't hide inside an average.
- A latency trend with minimum, average and maximum latency for the selected window.
- Incidents and scheduled maintenance, with history, so you can see what happened and how long it lasted.
The monitor has its own page at status.timelogicapi.com/monitors/timelogic-api.
Get notified instead of refreshing
You shouldn't have to keep a tab open to know whether a dependency is healthy.
- Subscribe on the status page to get incident and maintenance updates by email.
- RSS: incidents and maintenance are published as a feed at
https://status.timelogicapi.com/rss.xml. Point your feed reader, Slack RSS app or on-call tooling at it.
curl -s https://status.timelogicapi.com/rss.xml
Put live status in your README or dashboard
The status page serves SVG badges, so you can show live TimeLogic API status next to your own:
The uptime badge covers the last 90 days by default. Add sinceLast (in seconds) for another window, for example the last 30 days:
https://status.timelogicapi.com/badge/timelogic-api/uptime?sinceLast=2592000
Measure it from your side too
A status page tells you how the API looks from our monitor. Your users experience it from your network. A synthetic check of your own takes one line:
curl -s -o /dev/null -w "%{http_code} %{time_total}s\n" \
"https://api.timelogicapi.com/v1/time/current?tz=UTC" \
-H "Authorization: Bearer $TIMELOGIC_API_KEY"
A healthy call prints 200 and the total request time. Every response also carries an X-Request-Id header. If something ever looks off, log it and send it to us: it lets us find your exact request.
Why we publish it
Reliability claims are cheap. A public history is not. Publishing status, latency and incidents in the open holds us to the same standard you hold your own services to, and it gives you a link to share when someone on your team asks whether the time API is up.
Three weeks of 100% is a good start. We intend to keep it there.
Status: status.timelogicapi.com · Docs: timelogicapi.com/docs