Status
Is BayStacker up?
Two answers, from two places. Your browser asks the API directly, so you see what your own connection sees. Everything below that is the record an outside probe keeps: it checks the API and this site every five minutes and writes down what it found, failures included.
Right now
Reading https://locomotion.is/api/health from your browser…
The record
Reading the probe history…
How this is measured
- What is checked
- The API’s health endpoint at https://locomotion.is/api/health, and this site at https://baystacker.com. Each check follows redirects and records the status code, the response time, and, when nothing answered, what curl said.
- From where
- Our operations server — a different host from the API, on purpose. A check made inside the platform would never touch DNS, TLS, the proxy or the CDN, and could not report its own downtime.
- How often
- Every five minutes, both targets, one row each. A check that does not answer is recorded as a failure rather than retried into a success.
- What counts as a failure
- Any answer of 400 or above, and no answer at all. A run of failed checks is one incident, and it ends at the first check that answers again — which is why the list above says how long each one lasted instead of how many checks failed.
- What is kept
- Every check is kept for 180 days; this page reads the most recent 90. The window shown is stated with every figure, so a percentage here is never a claim about a period with nothing recorded in it.
Something not working that this page says is? Tell us — the record above is a good place to start.