Bu yazının Türkçesi için tıklayın.

A month ago I introduced imsu.io. Since then it has grown from a website checker into something that watches your sites, your services and your background jobs. Here’s what’s new.

Smarter HTTP checks

A 200 isn’t always enough. You can now set the status code you expect, look for a keyword in the response, choose between GET and HEAD requests, and decide how redirects are handled. With a keyword check, a /health endpoint that returns 200 with an error message inside no longer passes as healthy.

Heartbeat monitors

Some of the most important jobs are the ones nobody sees: nightly backups, cron jobs, scheduled imports. With a heartbeat monitor, your job pings imsu.io when it runs, and you get alerted when the ping doesn’t arrive. You can also report progress and explicit failures, set a grace period, and get warned when a job takes too long to finish.

TCP port monitors

Not everything speaks HTTP. A TCP port monitor checks whether a public service such as a mail server accepts connections. It shows the connection time and tells you whether a failure was a refused connection, a timeout or a DNS error.

Negative TCP checks

Some doors should stay closed. A negative TCP check alerts you when a port that should be closed starts accepting connections, so you hear about it right away if a database or admin panel becomes reachable from the internet.

More control over history

You can now compare uptime over the last 24 hours, 7, 30 or 90 days, look through response-time charts and detailed check results, and pause or resume a monitor whenever you need to.

It’s still free to start and still doesn’t need a credit card. If you’ve been using imsu.io, thank you. If you haven’t tried it yet, now is a good time. As always, I’d love to hear what you think. You can reach me by email.