This page is /status, and it is the only page on this estate that says whether anything is working. / is the way IN — names, purposes and links, and not one claim about health, because a fact with two owners is how this estate keeps being wrong. Machines poll /health, which answers this page as JSON with a status code that means something. The dot on a card at / is this page's verdict rendered again — the same snapshot, the same function — so it is the only claim that page makes and it cannot be a second opinion.
sampledevery 60s, in the background
this observation46s old
history since10m ago
samples stored121
survived0 restart(s)
This history starts here. Nothing was found in the store when this container started, so every window below begins at that moment. If this keeps happening after a merge, the volume in health/compose.yaml is not attached and the memory of this page is one deploy long — docs/health-page.md says how to check.
down · 5ok · 6
Needs attention. These are ours:
TAG Harness — The read operation timed out
Sign-in (TAG's login app) — The read operation timed out
Accounts (Ory Kratos, public) — The read operation timed out
TrueForge — Personal — [Errno -2] Name or service not known
TrueForge — Northwind Traders (synthetic, org-a) — [Errno -2] Name or service not known
Web surfaces
down · 3ok · 1
What a person opens in a browser, probed through the edge at its own address, so a pass also proves the route and the certificate.
TAG Harnessdown
harness.preview.tag.company
04:00Z1 of 24 hours observednow
state
downfor 1m · since 03:50Z
24 hours
not observed that long· 0.0% of 11 so far
7 days
not observed that long· 0.0% of 11 so far
30 days
not observed that long· 0.0% of 11 so far
all time
0.0%11 samples· 10 down, 1 degraded· observed 10m
response
4,099 msnowp50 4,058 ms p95 4,117 ms · 11 samples, 24h
changed
2time(s) in 24h — a service that flaps is a different problem from one that is down
last failure
0s ago· down — The read operation timed out
probe
http · the address is not published on this page expects HTTP 200 through the edge
The read operation timed out · through the edge · 4099 ms
Sign-in (TAG's login app)down
login.preview.tag.company
04:00Z1 of 24 hours observednow
state
downfor 10m · since 03:42Z
24 hours
not observed that long· 0.0% of 11 so far
7 days
not observed that long· 0.0% of 11 so far
30 days
not observed that long· 0.0% of 11 so far
all time
0.0%11 samples· 11 down· observed 10m
response
4,099 msnowp50 4,077 ms p95 4,099 ms · 11 samples, 24h
last failure
0s ago· down — The read operation timed out
probe
http · the address is not published on this page expects HTTP 200 through the edge
The read operation timed out · through the edge · 4099 ms
Accounts (Ory Kratos, public)down
The allowlisted public paths on the sign-in host
04:00Z1 of 24 hours observednow
state
downfor 10m · since 03:42Z
24 hours
not observed that long· 0.0% of 11 so far
7 days
not observed that long· 0.0% of 11 so far
30 days
not observed that long· 0.0% of 11 so far
all time
0.0%11 samples· 11 down· observed 10m
response
4,097 msnowp50 4,065 ms p95 4,102 ms · 11 samples, 24h
last failure
0s ago· down — The read operation timed out
probe
http · the address is not published on this page expects HTTP 401 through the edge
The read operation timed out · through the edge · 4097 ms
OIDC issuer (Ory Hydra, public)ok
auth.preview.tag.company
04:00Z1 of 24 hours observednow
state
okfor 8m · since 03:43Z
24 hours
not observed that long· 90.9% of 11 so far
7 days
not observed that long· 90.9% of 11 so far
30 days
not observed that long· 90.9% of 11 so far
all time
90.9%11 samples· 1 down· observed 10m
response
122 msnowp50 86 ms p95 122 ms · 11 samples, 24h
changed
1time(s) in 24h — a service that flaps is a different problem from one that is down