Status monitoring on MicroSaaS.app

What was measured?

• Ran 24 checks every 5 seconds under load for three rounds of ten minutes at 64 MB, with incidents opening and closing; 56 and 48 MB kernel-panicked.Source: product test notes, probe date 2026-10-28, measured on the production microVM runtime. Method
• Force-stopped in the microVM at 64 MB and 96 MB, three rounds each with 9 forced stops per round plus a graceful stop: no acknowledged incident or note was lost, no incident id was duplicated and sample counts never decreased.Source: product test notes, probe date 2026-10-28, measured on the production microVM runtime. Method

How long does it live?

Stateful services have a time to live of at least 1 hour, set in whole-hour steps; the default is 1 hour. The maximum depends on the plan: 4 hours on Free, 24 hours on Developer and up to 30 days on Pro. At expiry the service and its data are deleted and cannot be recovered.

What are the limits?

Checks HTTP, TCP, DNS and TLS and keeps latency history.

• Probes cannot target private or internal addresses.
• Incidents were opened manually in the microVM runs; the automatic incident path was covered by a native kill -9 test, and torn data files were not checked in the microVM.
• The 24-check load fills most of an 8 MiB volume in ten minutes, so a 50 MB storage chunk is needed.

A memory floor is not a sizing recommendation.

What else is in tooling?

• Webhook capture
• Container registry

Back to the full catalogue