Back to portfolio
Live infrastructure telemetry

System Status

A daily scheduled job writes one heartbeat row to the portfolio's Postgres database. This page reads that table live, so what you see is the real history, not a mock.

All systems operational
Last database heartbeat recorded yesterday.
Current streak
21 days
Consecutive days with a heartbeat
Days recorded
21
21/21 tracked days in the last 30
Last heartbeat
08:31
16 Oct 2026 · UTC+2
Next scheduled run
~08:00
17 Oct 2026 · UTC+2 (within the hour)

Last 30 days

Days in Europe/Berlin (UTC+2)
  1. 18 Sept 2026: Before monitoring started
  2. 19 Sept 2026: Before monitoring started
  3. 20 Sept 2026: Before monitoring started
  4. 21 Sept 2026: Before monitoring started
  5. 22 Sept 2026: Before monitoring started
  6. 23 Sept 2026: Before monitoring started
  7. 24 Sept 2026: Before monitoring started
  8. 25 Sept 2026: Before monitoring started
  9. 26 Sept 2026: Heartbeat recorded
  10. 27 Sept 2026: Heartbeat recorded
  11. 28 Sept 2026: Heartbeat recorded
  12. 29 Sept 2026: Heartbeat recorded
  13. 30 Sept 2026: Heartbeat recorded
  14. 1 Oct 2026: Heartbeat recorded
  15. 2 Oct 2026: Heartbeat recorded
  16. 3 Oct 2026: Heartbeat recorded
  17. 4 Oct 2026: Heartbeat recorded
  18. 5 Oct 2026: Heartbeat recorded
  19. 6 Oct 2026: Heartbeat recorded
  20. 7 Oct 2026: Heartbeat recorded
  21. 8 Oct 2026: Heartbeat recorded
  22. 9 Oct 2026: Heartbeat recorded
  23. 10 Oct 2026: Heartbeat recorded
  24. 11 Oct 2026: Heartbeat recorded
  25. 12 Oct 2026: Heartbeat recorded
  26. 13 Oct 2026: Heartbeat recorded
  27. 14 Oct 2026: Heartbeat recorded
  28. 15 Oct 2026: Heartbeat recorded
  29. 16 Oct 2026: Heartbeat recorded
  30. 17 Oct 2026: Today's run pending
18 Sept 2026Today
  • Heartbeat recorded
  • No heartbeat
  • Today's run pending
  • Before monitoring started

How it works

  1. 01 · Schedule
    A Vercel Cron job calls a secret-protected API route once a day at 06:00 UTC.
  2. 02 · Write
    The route inserts at most one row per Europe/Berlin day inside a locked transaction, so retries never duplicate. Row-level security keeps the table private.
  3. 03 · Read
    This page reads the table through a 10-minute server cache and refreshes itself every 12 hours while open. Supabase's free tier pauses after 7 idle days; the daily write prevents that.

Data read at 05:56 on 17 Oct 2026 (Europe/Berlin)