Know when your site is down — set up in a minute, read in a second
Paste a URL, pick how often, and choose where alerts go. Checks run from multiple regions, and one clean screen shows what is up, what is slow, and where.
No credit card. Free forever for 10 checks.
One screen for status, speed, and regions
Status, response time, and the last run sit together. Switch the time range, hide a region, and the answer to “is it us or is it the network?” is usually already on the screen.
Spike at 14:05 from Frankfurt only. The other regions stayed flat.
Understand your website's status
Every monitor shows its state and recent history as a single bar. Green is fine. Amber is slow. Red needs you.
Compare performance across regions
Hide a region to see whether a spike is local routing or the whole service. A one-city spike rarely means an outage.
See what happened during each check
Status code, response time, headers, host IP, and DNS resolve time on each check. The detail is one click away, never in your face.
Track performance over time
The last 2 hours, day, week, or month. Enough to spot a slow drift before it turns into an outage.
Start monitoring in three steps
Most uptime tools open with a wall of options. We start with the three things only you can answer, and give everything else a sensible default you can change later.
A website, landing page, or API health endpoint. Healthy status codes start at 200–299, so most sites need nothing more. APIs can use GET or POST when you need them.
Every 1, 5, 10, or 30 minutes. One-minute checks start on the $5 Solo plan; the free plan checks every 10 minutes.
Email, Slack, Microsoft Teams, desktop notifications, or a webhook. Send a test alert and you are done.
Status codes, timeouts, and response-time limits start on defaults. Tighten them whenever you like.
Simple to start. Sharp when you need it
Every option has a default that suits most sites. Open the settings only when a check needs to be stricter.
Healthy status codes
Add 301 or 302 when a redirect is expected. Anything outside the list, or a timeout, is a failed check.
Look for words on the page
A 200 can still be the wrong page. Require a string to be present, or fail when an error message appears.
Response-time limit
Set a limit in milliseconds. A region that crosses it fails that run, so slow counts as broken when it matters.
APIs, not just pages
Point a check at an API URL the same way you point it at a site, with the same status, latency, and string match.
Consecutive failures
Decide how many failed checks in a row it takes before each channel is alerted. Slack can hear first; the pager can wait.
Your interval
Fast checks for checkout and login, slower ones for the blog. Change it at any time without rebuilding the monitor.
Alerts that mean something
A single dropped packet should not wake anyone. Set how many consecutive failures count before an alert, and send each channel its own rule — Slack for a heads-up, your pager for the real ones.
- Different rules per channel: Slack after two failures, a webhook into the pager after five.
- Every alert names the region, so a blip in one city reads differently from a real outage.
- Send a test alert from the channel settings so you know it reaches the right place.
3 checks in a row over the 1,000 ms limit from Frankfurt. London and Singapore are normal.
Uptime is old news. Using it should not feel old
Every monitoring tool can ping a URL. The difference is how quickly you get set up, and how quickly you understand what you are looking at.
Lots of settings to fill in before the first check runs.
URL, interval, alert channel. Defaults cover the rest, and the first check runs straight away.
Results can end up spread across logs and separate reports.
Status, response time by region, and the last run on one screen.
Alerts for every blip can pile up until people mute the channel.
Alerts after the consecutive failures you choose, set per channel.
Often a second product when you need browser journeys or cron checks.
Synthetic, API, heartbeat, SSL, WHOIS, and status pages in the same app.
Go beyond basic uptime
Uptime is the start. Watch certificates, domains, cron jobs, and real browser journeys from the same place.
SSL and domain expiry
Get alerts before a certificate or domain expires. Included in every plan’s check allowance.
Status pages
Public or private pages that update from your monitors. Custom domains from the Solo plan.
Heartbeat and cron
Scheduled tasks like backups, billing, and syncs check in when they finish. If they go quiet, something failed.
Synthetic journeys
A real browser walks login or checkout and keeps the proof when it breaks.
Trusted by clients that rely on reliable monitoring
“They played a crucial role in helping us quickly onboard several hundred sites for both uptime and synthetic monitoring, providing invaluable support every step of the way.”
“The company I work for needed to transition to a new monitoring system for the many ecommerce sites we support, and Acumen has stepped in and filled the void in a terrific way.”
“Love the support we got from Acumen Logs! Highly recommended.”
Start free. Go to one-minute checks for $5
Checks share one allowance with uptime, SSL, WHOIS, and heartbeat — mix them as you need. No credit card to start, and you can cancel any time.
Free
- 10 uptime, SSL, and WHOIS checks
- Checks every 10 minutes
- Email alerts
- 1 status page
- 3 days of history
Solo
- 100 uptime, SSL, and WHOIS checks
- Checks every minute
- Slack, Teams, desktop, and webhook alerts
- 10 status pages with custom domains
- 10 days of history, with export
Need more checks, longer history, or synthetic video? Essentials and Pro are on the pricing page.
See every plan →Frequently Asked Questions
How long does setup take?
About a minute. Paste the URL, choose an interval, and pick an alert channel. Status codes and other settings start on defaults, so the first check can run straight away.
How often can a site be checked?
Every 1, 5, 10, or 30 minutes. The free plan checks every 10 minutes. One-minute checks start on the Solo plan at $5 a month.
Can it monitor APIs as well as websites?
Yes. Point a check at an API URL over GET or POST and you get the same status, latency, headers, and string match. Chained requests, auth tokens, and JSON assertions belong to API monitoring, a separate test.
How do I stop false alarms?
Set how many consecutive failures each channel waits for, and check the region on the alert. A spike in one region usually points at routing or a CDN; a spike everywhere points at the service.
Show all questions Show fewer questions
Where do alerts go?
Email on every plan. Slack, Microsoft Teams, desktop notifications, and webhooks from the Solo plan.
What happens when I need more than uptime?
Stay in the same app. SSL and WHOIS expiry, heartbeat checks, status pages, and synthetic browser journeys all sit beside your uptime monitors.
Explore Acumen Logs Monitoring Tools
Free website testing tools, monitoring products, and practical engineering guides.
Free website testing tools
Key products
Create complete synthetic journeys from a simple prompt.
Explore builder →Keep your website running. Start monitoring for free.
Monitor your site and response times, and get alerts when something goes wrong. 10 free checks, no credit card.