Status
System status
A live status page with automated incident history is scheduled work. Until it exists, this page tells you exactly how to check for yourself.
Components
What makes up the platform
| Component | Endpoint | Purpose |
|---|---|---|
| Panchang API | /v1/panchang | Core calendar surface |
| Festival API | /v1/festivals | Rule evaluation and explainability |
| Health probe | /v1/health | Liveness endpoint |
| Documentation | docs.tathaastuapi.com | API reference |
Check liveness yourself
GET https://api.tathaastuapi.com/v1/health is public and unauthenticated. It returns 200 whenever the API is serving, so you can wire it into your own monitoring rather than waiting on ours.Latency
Measured on production
Measured production observations (10 warmed samples per endpoint through the public API on 2026-08-20), not guarantees. Latency varies with cache state, load and request parameters. These are the same figures published on the Accuracy page — we do not keep two sets of numbers.
| Endpoint | Median | p95 |
|---|---|---|
| /v1/panchang | ~35 ms | ~42 ms |
| /v1/festivals | ~95 ms | ~122 ms |
| /v1/festivals/explain | ~118 ms | ~238 ms |
Cold cache — /v1/festivals/year
The first request for an uncached (year, location) on /v1/festivals/year can take up to ~20 seconds while the full year is derived. Subsequent cached requests return in well under a second. Pre-warming commonly requested year/location combinations is planned.
No uptime percentage published
We do not yet run the continuous external monitoring required to state an uptime figure honestly, so we do not state one. Pro carries a 99.9% target and Enterprise is contractual — those are commitments, not measurements. Conflating the two would be exactly the kind of claim this platform exists to avoid.