We’ve enhanced our HTTP Monitor to give you more control over what counts as “up.”

What’s new?

You can now define the exact HTTP status codes that should be considered successful for your uptime checks.

✅ How it works

• If left empty: All 2xx status codes are treated as success (default behavior, unchanged).

• If specified: Only the status codes you list will be accepted as “up.”

💡 Why this matters

Not all healthy endpoints return a 2xx response. Some services intentionally use redirects (3xx) or other specific codes to indicate correct behavior. With this update, you can align monitoring with your application’s real-world logic.

This gives you:

• More accurate uptime reporting

• Fewer false alerts

• Greater flexibility for modern architectures

Learn more in our HTTP Monitor Setup Guide.

Let us know what you think!