How to Set Up Website Downtime Alerts in Under 5 Minutes
Finding out your website is down from a customer complaint or a dip in analytics is never a good experience. The fix is simple: set up automated downtime alerts so you know the moment something goes wrong. With the right tool, the entire setup takes less than five minutes.
This guide walks you through setting up website monitoring and downtime alerts using Sitewake, from creating your account to receiving your first alert.
Why Downtime Alerts Matter
The average website experiences around 3 to 5 hours of downtime per year. For some sites, especially those on shared hosting or with complex application stacks, it can be much more. The issue is rarely that downtime happens. It is that it goes unnoticed.
Without monitoring, downtime often gets discovered through:
- Customer complaints via email or social media
- A drop in sales or conversions that shows up hours later in analytics
- A team member who happens to visit the site
None of these are acceptable detection methods for a production website. Automated alerts ensure you find out within minutes, not hours, giving you the best chance to resolve the issue before it impacts your business.
Step 1: Create Your Sitewake Account
Head to sitewake.net and sign up. You can register with your email or use Google or GitHub authentication. The free plan includes three monitors, which is enough to get started with your most important sites.
No credit card is required for the free plan.
Step 2: Add Your First Monitor
Once you are logged in, navigate to the dashboard and click the button to create a new monitor. You will need to provide:
- URL: The full URL of the website you want to monitor (e.g.,
https://yoursite.com). Use the exact URL your visitors use. - Check interval: How often Sitewake should check your site. Shorter intervals mean faster detection but use more of your check quota. A 3-minute interval is a good starting point for most sites.
That is it for the basic configuration. Sitewake will begin sending HTTP requests to your URL at the interval you specified and recording whether the site responds correctly.
Step 3: Set Up Notification Channels
A monitor without alerts is just a dashboard you have to remember to check. To get notified when your site goes down, you need to configure at least one notification channel.
Sitewake supports two types of notification channels:
Email Alerts
Email is the simplest option and a good default for most use cases. Navigate to the notification channels section, add a new email channel, and enter the email address where you want to receive alerts. You will receive a verification email to confirm the address.
Email alerts work well for:
- General awareness of downtime events
- Non-critical sites where a few minutes of delay is acceptable
- Teams that monitor a shared inbox
SMS Alerts
For critical websites where every minute counts, SMS alerts ensure you get notified even when you are not at your desk. Add an SMS channel with your phone number, verify it, and assign it to your most important monitors.
SMS alerts are ideal for:
- Production e-commerce sites
- SaaS applications with uptime SLAs
- Sites where downtime directly impacts revenue
- On-call scenarios where you need immediate notification
You can set up multiple channels and assign different ones to different monitors. For example, you might want email alerts for your blog but email and SMS for your main application.
Step 4: Assign Channels to Your Monitor
After creating your notification channels, go back to your monitor configuration and assign the channels you want to use. When Sitewake detects that your site is down, it will send alerts through every channel assigned to that monitor.
You will also receive a recovery notification when the site comes back online, so you know the issue has been resolved.
Step 5: Verify Everything Works
Once your monitor is active and your channels are assigned, give it a minute to run its first check. You should see the monitor status on your dashboard showing either "up" or the current response time.
To confirm your alerts are working, you can temporarily point the monitor at a URL you know will fail, or simply wait for the next real incident. Either way, you now have automated monitoring in place and can stop worrying about silent downtime.
Tips for Effective Alert Configuration
Start with your most critical sites. If you are on the free plan with three monitors, use them for the sites where downtime has the biggest impact.
Use SMS sparingly. Reserve SMS alerts for truly critical monitors. If every minor issue triggers a text message, you will start ignoring them, which defeats the purpose.
Monitor the right URL. If your site has a health check endpoint (like /api/health), consider monitoring that in addition to the homepage. It can give you more specific information about application health.
Check your spam folder. If you are not receiving email alerts, make sure they are not being caught by your spam filter. Add the Sitewake sender address to your contacts to prevent this.
What Happens When Your Site Goes Down
When Sitewake detects that a check has failed, it confirms the failure with additional checks to avoid false positives from transient network issues. Once downtime is confirmed, it immediately sends notifications through your configured channels.
The alert includes key details: which monitor triggered it, when the downtime was detected, and the type of failure. This gives you enough context to start investigating immediately.
When the site recovers, you receive a follow-up notification with the total downtime duration, which is useful for incident tracking and reporting.
Wrapping Up
Setting up downtime alerts is one of the highest-value, lowest-effort things you can do for any website you are responsible for. Five minutes of configuration gives you 24/7 automated monitoring and instant notifications when things go wrong.
If you have not set up monitoring yet, there is no reason to wait. Create a free account on Sitewake, add your first monitor, configure your alert channels, and you will be covered before your next cup of coffee is finished.