Oddlynew Status
All systems operational
MCP
Operational-
MCP for agents
OperationalThe agent endpoint answers a request without sign-in as expected.
90d uptime 99.99%24h probe latency (mean) 394 ms
-
MCP request admission
OperationalA test checks the gate that keeps agent connections responsive under load; trouble here can make requests wait or be refused.
90d uptime 99.65%24h probe latency (mean) 467 ms
-
MCP capacity headroom
OperationalA dedicated test checks that capacity can be reserved for agent work and released again.
90d uptime 99.54%24h probe latency (mean) 537 ms
-
Stuck request detector
OperationalChecks for reported agent requests whose capacity remains held for too long.
90d uptime 99.94%24h probe latency (mean) 468 ms
API
Operational-
API reads
OperationalThe public API answers a request for its API description.
90d uptime 99.99%24h probe latency (mean) 295 ms
-
API capacity gate
OperationalA test request checks that the API's capacity gate answers promptly, whether it admits or refuses.
90d uptime 97.00%24h probe latency (mean) 372 ms
Web app
Operational-
Web app
OperationalThe application answers and can reach its database.
90d uptime 99.98%24h probe latency (mean) 366 ms
Knowledge write cycle
Operational-
Knowledge write cycle: search visibility for the previous cycle's document
OperationalA test organization creates, edits, publishes, reads and deletes documents every five minutes in production; search visibility is checked only in production. This row measures search visibility for the previous cycle's document.
90d uptime 94.76%24h probe latency (mean) 1524 ms
-
Knowledge write cycle: create
OperationalA test organization creates, edits, publishes, reads and deletes documents every five minutes in production; search visibility is checked only in production. This row measures create.
90d uptime 99.93%24h probe latency (mean) 2803 ms
-
Knowledge write cycle: edit
OperationalA test organization creates, edits, publishes, reads and deletes documents every five minutes in production; search visibility is checked only in production. This row measures edit.
90d uptime 99.93%24h probe latency (mean) 1815 ms
-
Knowledge write cycle: publish
OperationalA test organization creates, edits, publishes, reads and deletes documents every five minutes in production; search visibility is checked only in production. This row measures publish.
90d uptime 98.94%24h probe latency (mean) 3385 ms
-
Knowledge write cycle: read published
OperationalA test organization creates, edits, publishes, reads and deletes documents every five minutes in production; search visibility is checked only in production. This row measures read published.
90d uptime 98.92%24h probe latency (mean) 1358 ms
-
Knowledge write cycle: read published again from cache
OperationalA test organization creates, edits, publishes, reads and deletes documents every five minutes in production; search visibility is checked only in production. This row measures read published again from cache.
90d uptime 98.93%24h probe latency (mean) 251 ms
-
Knowledge write cycle: read draft
OperationalA test organization creates, edits, publishes, reads and deletes documents every five minutes in production; search visibility is checked only in production. This row measures read draft.
90d uptime 98.90%24h probe latency (mean) 666 ms
-
Knowledge write cycle: delete
OperationalA test organization creates, edits, publishes, reads and deletes documents every five minutes in production; search visibility is checked only in production. This row measures delete.
90d uptime 99.93%24h probe latency (mean) 2253 ms
-
Knowledge write cycle: create a document over HTTP
OperationalA test organization creates, edits, publishes, reads and deletes documents every five minutes in production; search visibility is checked only in production. This row measures create a document over HTTP.
90d uptime 99.83%24h probe latency (mean) 2756 ms
Background processing
Operational-
Background processing
OperationalChecks for delayed or failed background processing of document updates.
90d uptime 88.61%24h probe latency (mean) -
Production endpoint checks run every minute. Customer operations run every five minutes in production and every fifteen minutes in staging. Last check 2026-10-27T13:35:27.605Z. Incident history. Machine-readable at /status.json.