Skip to content

Tridot API status

All systems operationalUpdated Nov 18, 2026, 3:49 PM UTC · recomputed every 60 s

Services

ServiceStatusError rate 24 hp95 24 hError rate 7 dp95 7 dLast 7 days
Turn-takingOperational Synthetic check0.0%80 ms0.0%80 ms
  1. Nov 12: Operational
  2. Nov 13: Operational
  3. Nov 14: Operational
  4. Nov 15: Operational
  5. Nov 16: Operational
  6. Nov 17: Operational
  7. Nov 18: Operational
ProactivenessOperational Synthetic check0.0%130 ms0.0%130 ms
  1. Nov 12: Operational
  2. Nov 13: Operational
  3. Nov 14: Operational
  4. Nov 15: Operational
  5. Nov 16: Operational
  6. Nov 17: Operational
  7. Nov 18: Operational
Social dynamicsOperational Synthetic check0.0%120 ms0.0%120 ms
  1. Nov 12: Operational
  2. Nov 13: Operational
  3. Nov 14: Operational
  4. Nov 15: Operational
  5. Nov 16: Operational
  6. Nov 17: Operational
  7. Nov 18: Operational
Social memoryOperational Synthetic check0.0%100 ms0.0%100 ms
  1. Nov 12: Operational
  2. Nov 13: Operational
  3. Nov 14: Operational
  4. Nov 15: Operational
  5. Nov 16: Operational
  6. Nov 17: Operational
  7. Nov 18: Operational
Event awarenessOperational Synthetic check0.0%40 ms0.0%50 ms
  1. Nov 12: Operational
  2. Nov 13: Operational
  3. Nov 14: Operational
  4. Nov 15: Operational
  5. Nov 16: Operational
  6. Nov 17: Operational
  7. Nov 18: Operational
Action selectionOperational Synthetic check0.0%40 ms0.0%40 ms
  1. Nov 12: Operational
  2. Nov 13: Operational
  3. Nov 14: Operational
  4. Nov 15: Operational
  5. Nov 16: Operational
  6. Nov 17: Operational
  7. Nov 18: Operational
PersonaOperational Synthetic check0.0%40 ms0.0%40 ms
  1. Nov 12: Operational
  2. Nov 13: Operational
  3. Nov 14: Operational
  4. Nov 15: Operational
  5. Nov 16: Operational
  6. Nov 17: Operational
  7. Nov 18: Operational
Expression & motionOperational Synthetic check0.0%50 ms0.0%50 ms
  1. Nov 12: Operational
  2. Nov 13: Operational
  3. Nov 14: Operational
  4. Nov 15: Operational
  5. Nov 16: Operational
  6. Nov 17: Operational
  7. Nov 18: Operational
Conversation analyticsOperational Synthetic check0.0%70 ms0.0%60 ms
  1. Nov 12: Operational
  2. Nov 13: Operational
  3. Nov 14: Operational
  4. Nov 15: Operational
  5. Nov 16: Operational
  6. Nov 17: Operational
  7. Nov 18: Operational
Character APIOperational Synthetic check0.0%70 ms0.0%60 ms
  1. Nov 12: Operational
  2. Nov 13: Operational
  3. Nov 14: Operational
  4. Nov 15: Operational
  5. Nov 16: Operational
  6. Nov 17: Operational
  7. Nov 18: Operational
GuardrailOperational Synthetic check0.0%70 ms0.0%60 ms
  1. Nov 12: Operational
  2. Nov 13: Operational
  3. Nov 14: Operational
  4. Nov 15: Operational
  5. Nov 16: Operational
  6. Nov 17: Operational
  7. Nov 18: Operational
MCP endpointOperational Synthetic check0.0%60 ms0.0%50 ms
  1. Nov 12: Operational
  2. Nov 13: Operational
  3. Nov 14: Operational
  4. Nov 15: Operational
  5. Nov 16: Operational
  6. Nov 17: Operational
  7. Nov 18: Operational

Last synthetic check Nov 18, 2026, 3:45 PM UTC · every 5 minutes

How this is measured

  • Error rate: the share of REST API, MCP and playground calls that ended in a 5xx. 4xx answers (key, limit or input errors) are not counted.
  • p95: the 95th percentile of the time from receiving a request to answering it, inside Tridot.
  • A window with fewer than 20 calls shows “Not enough traffic” instead of numbers. No per-customer data or call volume is published.
  • Status: a 24-hour error rate of 5% or more shows as degraded, 25% or more as a partial outage. An incident posted by our operators takes precedence.
  • “Synthetic check”: where live traffic is too thin, a service is measured by our synthetic checks every 5 minutes. While all services run in sandbox mode these cover authentication, routing, input validation, rate limiting, the database and response serialization; real-engine latency appears once services are live. 3 failed checks in a row (5xx) show as a partial outage.

Machine-readable: /status.json · Contact: hello@tridot.io