# echorune status
checked every minute from the server itself against the public URL
https://echorune.net/tokyo/en -- success means curl exit 0 AND http 200
AND a body over 400 bytes AND under the wall in force at that moment.
A 14.9s http-200 is a failure here, not a slow success. Raw seconds stay
in the CSV, so any window can be recomputed under a different threshold.

wall history -- each sample is judged by the ruler of its own era:
  before 2026-07-31 13:26 UTC: 3s
  from 2026-07-31 13:26 UTC: 10s

now:        UP   (http 200, 1.47s, 2903 bytes, 0min ago)
last hour  100.00%  n=60    fail=0    median 1.25s  worst 6.91s
last 24h   100.00%  n=1440  fail=0    median 1.20s  worst 7.59s
last 7d    100.00%  n=10080 fail=0    median 1.09s  worst 9.97s

last 24h, one glyph per 30min  (blank = no sample yet)
████████████████████████████████████████████████
full=100%  ▓=>=99%  ▒=>=90%  ░=below

recent failures (UTC):
  2026-07-31 06:27:11  http=200  curl=0   10.35s 1922B
  2026-07-31 06:38:16  http=200  curl=0   14.72s 469B
  2026-07-31 06:44:12  http=200  curl=0   10.41s 1970B
  2026-07-31 06:48:04  http=200  curl=0   3.34s 1910B
  2026-07-31 08:06:04  http=200  curl=0   3.35s 2082B
  2026-08-13 09:31:35  http=200  curl=0   11.35s 3195B
  2026-08-18 05:17:11  http=000  curl=6   9.78s 0B
  2026-08-21 14:38:03  http=502  curl=0   0.81s 166B

generated 2026-09-07 14:35:02 UTC. This page is a static file
written by a cron job, not by the service it measures -- so it can still
tell you the service is down.