Uptime monitoring
HTTP health checks every minute with instant alerts.
Keep an eye on your websites (and your clients') with HTTP health checks that run every minute and alert you the moment something goes down.
- /uptime → New monitor
- Enter a URL (can be any public endpoint)
- Pick a check interval (1 min / 5 min / 15 min / 1 hour)
- Name it (e.g. "Client site — Acme Corp")
- Click Create monitor
First check runs within 10 seconds.
- HTTP status code — expects 200 by default (configurable per-monitor)
- Response time — measured in milliseconds
- SSL certificate validity — expires in ≤ 30 days triggers a warning
- Content check (optional) — expects a specific string on the response body
When a monitor fails 2 consecutive checks (to avoid false positives), we fire alerts via:
- In-app notification — bell icon in the topbar
- Email — to the user who created the monitor (if notifications enabled in profile)
- Slack webhook — configure in Settings → Integrations
- Telegram — configure with bot token + chat ID
- Outbound user webhook — POSTs to your endpoint with the monitor payload
When the site comes back up, a recovery alert fires.
Each monitor shows:
- Last 24 hours uptime percentage
- Last 7 days uptime
- Last 30 days uptime
- Last 90 days uptime + a bar chart (1 bar per day)
- Average response time
- Last failure details (status code, error message)
The 90-day bar is the standard "status page" format used by StatusCake, UptimeRobot, Better Stack, and Statuspage.io.
Enable the public status page at Settings → Workspace → Status page and your monitors appear at flowmaticx.com/status/[your-slug] for the whole internet to see. Great for reassuring customers during incidents.
- Monitor key pages, not just the homepage — login flow, checkout, API health endpoint
- Set a content check for the page's expected text — catches cases where the server returns 200 but the content is broken
- Use the 1-minute interval sparingly — for business-critical pages only. 5-min is fine for everything else and stays well under rate limits.
- Name monitors by client + page — "Acme Corp — homepage" is better than "Monitor 23" when alerts fire
FlowMaticX checks SSL certificate expiry on every monitor. Alerts fire at:
- 30 days before expiry (info)
- 14 days (warning)
- 7 days (urgent)
- 1 day (critical)
Never miss a cert renewal again.