Catch outages before your users do.
Flowtag Uptime monitors your sites, APIs, and servers — with incident tracking and public status pages.
12 detector types
Automatic incidents
Status pages
Plenty of outages return a valid status code. The page loads but renders an error. The API answers with the wrong payload. Flowtag checks what actually matters, so "up" means genuinely working.
Match a regex against a response header or body, verify a specific status code, or reach past HTTP entirely to a TCP port, a WebSocket, or your SMTP, IMAP, and DNS servers. A basic up/down ping calls all of those healthy.
Detectors
Different services fail in different ways. Choose the detector that matches how your endpoint actually breaks, then set the status codes, headers, or patterns that count as a pass.
HTTP endpoints
Alert when a URL goes unreachable, returns a status code outside your healthy list, or when a response header or body stops matching a regex you define.
Network ports
Reach a host by ICMP or TCP ping, or open a connection to a specific TCP or UDP port to confirm the service behind it is still accepting traffic.
Protocol servers
Check that a WebSocket, SMTP, POP3, IMAP, or DNS server answers — mail and realtime services a plain HTTP check would never notice failing.
Monitoring that sees what your users see.
Checked from outside your network, on a schedule, with the response time behind every check recorded.
Checked from the outside in
Every monitor hits your endpoint on a schedule from our side of the network — you see what your users would see, not what your server logs claim.
Incidents open themselves
The first failed check starts an incident automatically. No manual acknowledgement, no waiting for a customer to tell you something is down.
More than a ping
Twelve detector types check HTTP status, response headers and body, TCP and UDP ports, WebSocket, and SMTP, POP3, IMAP, and DNS servers.
Response time, recorded
Every check stores how long the endpoint took to answer, so a slow slide toward failure shows on the chart long before it goes hard down.
Status pages on your domain
Publish a public status page for your monitors, connect your own domain, and match it to your brand with a logo, theme, and color scheme.
Checks as tight as two minutes
Pick a cadence per monitor — from every two minutes up to hourly — and tune the timeout so slow-but-alive endpoints aren't flagged as down.
Downtime, tracked from the first failed check.
You don't file incidents — Flowtag does. The moment a check fails, an incident opens and the clock starts. When checks pass again, it resolves on its own.
Up and down duration
See how long a monitor has been up, or exactly how long it's been down during an active incident.
Full incident history
Every incident is kept with its timeline, so you can look back at how often and how long a service has failed.
Response-time trend
A chart of check latency over time turns a creeping slowdown into something you can catch before it becomes an outage.
Pause when you need to
Pause a monitor during known work and resume it later without losing its configuration or history.
One public page for "is it just me?"
Give customers somewhere to check before they open a ticket. Publish your monitors, put the page on your own domain, and make it look like part of your product.
Your own domain
Connect a custom domain and publish the page there, so customers see status.yourcompany.com instead of a shared URL.
Grouped monitors
Organize monitors into folders so a long list reads as clear sections — API, web, email — rather than one flat wall of dots.
Maintenance windows
Schedule planned work ahead of time so expected downtime shows as maintenance, not as a surprise incident.
Status reports
Post updates during an incident and keep a history of what happened, with automation to keep the page current as monitors recover.
On-brand look
Upload a logo and pick a theme and color scheme so the page fits your product instead of looking bolted on.
Always current
The page reflects live monitor state — when a check fails, visitors see it without you touching anything.
From endpoint to status page in minutes.
Add a monitor
Pick a detector, paste your URL or hostname, and choose how often to check. Response-pattern, port, WebSocket, and mail detectors are on the Pro plan.
From every 2 minWe watch it for you
Every interval, the endpoint is checked from the outside. Response times are recorded and an incident opens the moment a check fails.
Nothing to installShare the status
Add the monitor to a status page, connect your domain, and give customers a single place to see whether things are healthy.
Your own domainMove fast when something breaks.
Free plan included. No credit card, no agent to install, nothing to run on your own servers.
Free forever plan
No credit card, no trial countdown, no setup call.
Nothing to install
Checks run from our network — no agent on your servers.
Incidents open themselves
The first failed check starts the clock, with no acknowledgement needed.