Status

Working

Last check: 10/20/2026, 3:46:19 PM. Typical response in the last day: 103 ms.

Last 30 days

100% of checks passed (131 of 131; 0 failed, 0 did not run).

  1. 2026-09-21: no data
  2. 2026-09-22: no data
  3. 2026-09-23: no data
  4. 2026-09-24: no data
  5. 2026-09-25: no data
  6. 2026-09-26: no data
  7. 2026-09-27: no data
  8. 2026-09-28: no data
  9. 2026-09-29: no data
  10. 2026-09-30: no data
  11. 2026-10-01: no data
  12. 2026-10-02: no data
  13. 2026-10-03: no data
  14. 2026-10-04: no data
  15. 2026-10-05: no data
  16. 2026-10-06: no data
  17. 2026-10-07: no data
  18. 2026-10-08: no data
  19. 2026-10-09: no data
  20. 2026-10-10: no data
  21. 2026-10-11: no data
  22. 2026-10-12: no data
  23. 2026-10-13: no data
  24. 2026-10-14: no data
  25. 2026-10-15: no data
  26. 2026-10-16: no data
  27. 2026-10-17: no data
  28. 2026-10-18: no data
  29. 2026-10-19: 100%, all passed
  30. 2026-10-20: 100%, all passed
  • All checks passed
  • Some checks did not run
  • A check failed
  • No data yet

What this measures

Every 15 minutes the app checks that it can read its own database, and records the answer. This page counts those answers, starting 10/19/2026, 7:15:59 AM.

A check that did not run is counted as not confirmed working, never as working. The check runs inside our hosting platform, so it cannot see every problem a person might meet, such as a slow phone network.

We do not offer an uptime promise (SLA). See also Security and the roadmap and known limits.