We configure an uptime and monitoring service to watch your site and alert you the moment it goes down or responds unusually slowly — through your own account with the monitoring provider, since the ongoing subscription and who receives alerts long-term is something you manage directly, not something we hold on your behalf.
Uptime & monitoring service configuration
Uptime monitoring configured and alert-tested — watching it long-term stays your team's job.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- An account with your chosen uptime monitoring service, or confirmation you’d like a recommendation
- Confirmation of what should trigger an alert (downtime, slow response time, both)
- Confirmation of who should actually receive alerts, and through which channel (email, SMS, Slack)
This or something else?
| You want an uptime or monitoring service configured to watch your site and alert appropriately | This fix covers it |
| You want error tracking for application-level errors, not uptime specifically | Error tracking (Sentry) integration, a different, complementary kind of monitoring |
| You want notifications routed to Slack or Teams specifically as the alert destination | Slack / Teams notification routing setup, worth pairing with this if that’s your preferred alert channel |
| Your site is actually down right now and you need it fixed, not monitored | Site Down & Critical Errors category fixes — an urgent, different need than monitoring setup |
What we do
- Confirm your chosen monitoring service and alert preferences
- Configure the service to check your site at an appropriate interval
- Set up alerting to the correct recipients and channels
- Test the alerting by simulating a check failure where the service allows
- Verify normal, healthy checks don’t produce false alerts
- Document the configuration for future reference
What is included
- Uptime or performance monitoring configured for your site
- Alerting set up to your specified recipients and channels
- Tested confirmation of alert delivery
- A written note on the configuration
Not included
- Paying for or managing the monitoring service’s subscription itself, which remains yours directly with the provider
- Application-level error tracking, a separate, complementary kind of monitoring
- Actually fixing an issue the monitoring detects — a separate, related fix when needed
- Ongoing review of monitoring data as a standing service
Questions about this fix
Who receives the alerts long-term — you, or us?
Whoever you specify — typically you or your team, since the ongoing responsibility for responding to alerts is something you manage directly; we set up the routing but don't take on watching for and responding to every alert ourselves as part of this fix.
What happens if my monitoring service's free tier limit is reached?
We'd flag this if your check frequency or site count approaches a free tier's limit — upgrading to a paid tier is a decision between you and the monitoring provider.
Will this catch every kind of problem with my site?
Uptime and response-time monitoring catches whether your site is reachable and reasonably fast, though it won't catch every kind of issue (like a specific broken feature that doesn't affect overall site availability) — application-level error tracking is a complementary, different kind of coverage.
Can alerts go to multiple people or channels at once?
Yes, if you specify more than one recipient or channel, we can configure alerts to reach all of them simultaneously.
Is a false alert something to worry about?
We test to minimise false alerts during setup, though occasional false positives can happen with any monitoring service due to factors like a momentary network blip — worth expecting the rare false alarm rather than treating every alert as certainly a real outage.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.