Skip to content
Start a project See the work

Knowing which sites can fail over, before it matters.

Our hosting clients need their sites to survive a server failure, so we built a panel that checks each site every minute, through the CDN and on each server, and only calls it ready when both serve the same page.

FailoverLast check 14:32:05Check nowSites38 ready2 out of sync1 down on BSiteThrough CDNServer AServer BSame pageResponsebayview-grill200200200✓ samecanal-dental200200200✓ sameelmpark-library2002002003 files differhillcrest-fit200200200✓ samenorthgate-venues200200502–timeoutsouthpoint-realty200200200✓ samewestbrook-cafe2002002001 file differslakeside-studio200200200✓ samemaple-clinic200200200✓ sameoakridge-law200200200✓ sameharbor-yoga200200200✓ sameNext stepsnorthgate-venues1Server B answers 502 on /2Restart the PHP service on B3Re-check, then mark it ready

Screen redrawn with sample data. The client is not named.

Customer
Our own hosting clients
The result
We know which client sites can fail over before we need them to.
Runs on
Web
Built with
Node.js
What they wanted

A standby server only helps if it’s in sync, and nobody could say which sites were. Our hosting clients need their sites to stay up if a server goes down.

How we approached it

We made “ready” strict: both servers serve the same page. Anything else goes on the to-do list with the next step written in.

What we delivered
  • A live matrix of sites by server
  • Sync checks with the next step written in
  • A list of server issues
  • No dependencies, so it runs anywhere
Services
Industries

Have something that should work better?

Tell us what is getting in the way. A person reads it and replies within two business days.