Uptime
Login Flow Monitoring

Check that people can still sign in

A login form posting to a broken session store still leaves the homepage returning 200. A flow monitor signs in, reads the token back, and calls the endpoint it authorises, so the sign-in itself is what gets checked.

Sign-in checked each runJWT signature and expiryFailure names the step
Screenshot of the Uptime dashboard: a sidebar listing HTTP, DNS, and TCP monitors, cron jobs, alerts, maintenance, and status pages; summary cards for monthly ping usage, overall uptime percentage, and the slowest endpoint; per-type counts of monitors up and down; and a table of HTTP monitors with latency trend sparklines and status badges
Auth

First-class

JWT

Verified

15m

Minimum interval

90d

Result history

Deep Dive

Everything you need

A closer look at what you get, from the first check to the alert that reaches you.

Sign in the way your app does

A form post to a token endpoint, bearer or basic credentials, or a cookie header — whichever your login actually uses.

Verify the token, not just the response

The returned JWT is checked against your live JWKS: ES256 signature and expiry, past whether a string came back at all.

Then use it

Call the endpoint the token authorises and assert on what comes back. A 200 on the login page says nothing about the session behind it.

A named failure, not a status code

The failing test's title and line number, expected against observed, shown on your own spec with that line marked.

Get started

How it works

Three steps from an empty dashboard to checks that run on their own.

Verify your domain

A flow drives a sequence against your host, so the team verifies it first.

Write the sign-in

Post the fixture account's credentials, assert on the token, then call something it authorises.

Get alerted on the failing step

A broken sign-in alerts through your existing channels, naming the assertion that failed.

FAQ

Frequently asked questions

The questions people ask most before they start monitoring.

What credentials should a flow use?

A fixed fixture account. A flow replays the same spec every run and generates no data, so it can't invent a fresh signup address each time.

How quickly will I know the login broke?

A flow runs every 15 minutes at the fastest, hourly by default. Pair it with a 1-minute HTTP monitor on the endpoint the login depends on when you need faster detection.

Does this test the login page in a browser?

No — a flow makes HTTP requests and verifies tokens; nothing renders the page or runs client-side code. A login that breaks only in the browser needs a different tool.

Start monitoring your services

Create your first monitor in under 2 minutes. No credit card required to start.