Run a free check now. Early access adds scheduled checks, evidence-backed alerts and an off-site maintenance page.
https://example.com/
Where the time went, for this one request
Example result, for illustration. Run a real check to replace it with live evidence.
Example shown. Your result replaces it, from a real request. How checks work
Visitors meet timeouts long before your server stops answering. FourWay watches the whole slide, and only raises an alarm when the evidence agrees.
Checks pass. First byte in 220 ms.
One check takes 4.1 s. No alert yet: one slow check is not an outage.
Slow for five minutes in a row. You get a warning with the checks attached.
Three failed checks in a row. An incident opens and lists the check IDs.
Two passing checks plus a stability window before we say recovered.
Example Example timeline. Thresholds are starting points we tune with early-access sites.
A launch, a sale, a registration day. One script tag lets in as many people as your site can serve and gives everyone else a calm, fair place in line.
Trust is earned in the details. These are true right now, not on a roadmap.
Paste a domain and our server makes one request to it. You see the status, timing and certificate it actually got.
One GET, a 5 second timeout, a 64 KB read cap and rate limits. It can never be used as a load test.
Missing data shows as a gap. One slow check is not called an outage, and no check is not called healthy.
See who builds FourWay and every shipped change in the changelog.
Small sites now carry load they never planned for, and apps built fast can break quietly. Three numbers, with sources.
39,000+
requests per minute in a single burst from AI fetchers, as seen by Fastly. To a small origin that looks like an attack.
73 TB
downloaded by one AI crawler from Read the Docs in a single month, costing over $5,000 in bandwidth.
46%
of developers distrust the accuracy of AI tools they use. A page can return 200 OK and still be broken, so checks should look at content too.
Enter a domain and the page to watch. We normalise it and refuse unsafe targets.
Add one DNS TXT record or one small file. Until then, nothing is scheduled.
Every 5 minutes on Discover, every 60 seconds on paid plans. Each check is stored with its evidence.
Alerts name the checks, times and errors that caused them. Recovery is confirmed the same way.
Step 2 looks like this. One record, then click Verify.
; Proves you control the domain _fourway-verify TXT "fourway-verification=8f3c1a…"
Or serve the same token at /.well-known/fourway-verification.txt. Tokens expire after 24 hours and are stored hashed.
Verifying example.com does not authorise other hostnames. Each one is verified on its own.
Everything here ships with monitoring in early access. The visuals below are labelled examples.
Response time Example
Missing checks show as a gap, never as success. Each figure states how many checks it is based on.
Certificates
Plus hostname mismatches and chain errors, the moment a check sees them.
Incidents Example
Alerts
Down needs three failed checks in a row. Recovered needs two passes and a quiet window.
[Down] shop.example.com, 3 checks, 10:20 UTC
Park
The same Go, Yield, Park and Stop rules will coordinate AI work, scheduled jobs and email. Web comes first; each of the others has a waitlist.
Health checks with evidence, a fair waiting room for traffic spikes, bot pause during a rush, and a maintenance page that stays up.
Scheduled HTTP jobs with concurrency limits, idempotency keys, retries and verification.
Quota-aware sending through your own provider, with delivery windows and honest status.
Free tool
Use your own numbers: revenue per hour, people left waiting, recovery work. See the formula, a low and high range, and nothing hidden.
Early-access prices. Nothing is charged today, and we will give notice before any change.
Free
One site you care about.
$19 per month
Small teams with production sites.
$99 per month
Agencies running many client sites.
Early-access pricing, subject to change. Monitoring is not live yet, so nobody is billed. Commercial use is allowed on every plan. Prices in US dollars.
Not yet. Today you can run a free one-off check and join early access. Scheduled checks, alerts and the maintenance page preview open to early-access sites first, and the changelog will say the day they do.
You add one script tag. When more people arrive than your site can serve, new visitors wait in a calm line in arrival order, and your server only sees the people it can handle. If FourWay cannot be reached, everyone goes straight in.
From a rush, yes: the waiting room script holds new visitors in a fair line before your server is overwhelmed. From an outage, no: a script only runs once a page has loaded, so a page that never loads needs a gate in front of your server, which is our planned Edge Guard.
No. Search engines are always let through. Only AI crawlers, SEO tools and scripts are asked to come back later, and only while your site is busy.
The time, status code, timing, redirect count, certificate dates and any error for each check. We do not keep page content after a check, and we never ask for passwords.
A maintenance page tells visitors the site is down while you work on it. A waiting room lets visitors in at a safe pace when demand is high. You can build a maintenance page today, and the waiting room is in early access.
Run a free check in five seconds, then see how the waiting room holds a rush.