What’s the worst way you found out your website was down?
A website rarely goes down politely.
It waits until you are asleep.
Until the campaign goes live.
Until customers are trying to pay.
Then the first monitoring alert arrives wearing the face of an angry customer.
I’m launching Fajita because I think uptime monitoring has become too complicated, too noisy, and too eager to panic.
Most small teams do not need another command center.
They need three answers:
Is something broken?
Is it a real outage?
Who needs to know?
Fajita monitors websites, APIs, SSL certificates, and cron jobs.
When something fails, it verifies the problem before sounding the alarm, opens an incident, updates the status page, and alerts the team.
But I would rather make this thread useful than turn it into an advertisement.
So I’m curious:
What is the worst way you have discovered your website was down?
What frustrates you most about the monitoring tool you use today?
What would make you trust a new one enough to switch?
Share the horror stories.
I’ll be here answering every reply, and probably taking notes.
Cheers🥂
Replies