# TestFlows Machine Status > The current status of TestFlows Machine: the website, the API, sign-in, and sessions on each class. The website, the API and sessions are checked from a server outside the TestFlows cloud, sign-in from inside it: every 30 seconds for the website and the API, every minute for sign-in, and every 15 minutes for sessions. An operator writes incidents and maintenance. ## Status - [Status in Markdown](https://status.testflows.com/index.md): The status now, open incidents with their updates, and the last 14 days. Rewritten on every change and at least every 60 minutes; an incident an operator writes reaches it within 5 minutes. If the file is older than 75 minutes, treat the status as unknown. ## Machine-readable - [status.json](https://status.testflows.com/status.json): Each component's status, and each stretch it was not operational for 90 days, in Unix seconds. `updated` is when it was written; if it is older than `stale_after` seconds, treat the status as unknown. - [incidents.json](https://status.testflows.com/incidents.json): The incidents and maintenance an operator writes, each with its components and timestamped updates. - [feed.atom](https://status.testflows.com/feed.atom): The incidents as an Atom feed. ## Optional - [TestFlows Machine](https://testflows.com/machine.md): What Machine is. - [The website's index for agents](https://testflows.com/llms.txt): The rest of testflows.com in Markdown.