lovelyweb
Updating every 4s
Live · not cached
You are being served by
ip-10-10-18-91.ec2.internal
us-east-1b · us-east-1 · generated in 295.9 ms
the heart beats faster as CPU rises
Proof of life
Watch the load balancer
hand you around.
Each row is a real request this page just made. When the Availability Zone changes, a different server answered — that is high availability, happening in front of you.
Disaster recovery
Two regions.
One of them is serving you.
Route 53 watches the primary and decides which region answers. Data travels the other way — continuously, so the standby is never cold. The badges below are not decoration: they are read from whichever region actually rendered this page.
us-east-1
Serving all traffic
- Auto Scaling group across 2 Availability Zones
- Aurora writer · EFS primary
- WAF at the CloudFront edge
eu-central-1
Ready to take over
- 1 × EC2 running · scales out on promotion
- Aurora Global replica · EFS replica
- WAF on its own regional Web ACL
Health checks
Something is always
checking on us.
Two independent watchdogs probe this server around the clock. They are ordinary HTTP requests with their own signatures, so we can count them as they land — these are the real ones, not a simulation.
Firewall
Inspected before it
ever reaches us.
AWS WAF guards both paths — at the CloudFront edge for the primary, and on a regional Web ACL for the standby. You don’t have to take that on trust either.
Each button sends a real request carrying that attack. The firewall should refuse it before it ever reaches WordPress.
Caching
This page is deliberately
never cached.
The home page is served from the CloudFront edge for speed. This one bypasses it entirely, so every number above comes straight from the server that answered you.
This page — Live Status
Reading the response headers…
age at the edge: —
Home page
Cached at the edge by CloudFront’s cache policy — the origin sends no Cache-Control of its own.
age at the edge: —