# 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.06s, 1845 bytes, 0min ago)
last hour  100.00%  n=60    fail=0    median 0.69s  worst 6.70s
last 24h   100.00%  n=1439  fail=0    median 0.67s  worst 7.80s
last 7d     99.24%  n=10069 fail=77   median 0.55s  worst 7.80s

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

recent failures (UTC):
  2026-07-31 06:14:05  http=200  curl=0   3.09s 1926B
  2026-07-31 06:20:06  http=200  curl=0   4.75s 1916B
  2026-07-31 06:26:16  http=200  curl=0   14.73s 469B
  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

generated 2026-08-06 14:02:01 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.