Acceptable use

To be unambiguous, none of the following is a problem, and you never need to ask us first:

• Running hundreds or thousands of monitors on a Max plan.
• Running every one of them at the fastest interval your plan allows.
• Monitoring the same endpoint from several monitors for different reasons.
• Large bursts when you onboard a new fleet or migrate in from another tool.
• Agency and reseller use — monitoring your clients’ infrastructure on their behalf.

If your usage grows to the point where it affects how we run the service, that’s our capacity problem to solve, not yours. We’ll come to you to talk about it before it ever becomes a limit.

A check is a real request to a real server. You may point Moonitor at infrastructure you own or operate, or that you have permission to monitor on someone else’s behalf. You may not use it against third-party systems you have no relationship with.

These are the cases the policy is for. They’re about intent and effect, not volume:

• Using checks as traffic. Pointing many monitors at a target to generate load, degrade it, or contribute to a denial-of-service — whether or not you own it.
• Monitoring without permission. Checks against systems you neither operate nor have been asked to watch.
• Using the checker as a general-purpose fetcher. Moonitor is an uptime monitor, not a scraping backend, a proxy, or a way to route arbitrary requests through our infrastructure or our verification region.
• Manufacturing activity. Checks intended to inflate traffic, ad impressions, analytics or uptime figures rather than to observe them.
• Waste with no monitoring purpose. For example many thousands of duplicate 30-second monitors against one endpoint that a single monitor already covers — it tells you nothing extra and consumes capacity other customers are paying for.
• Anything illegal, or use that breaches the terms of the systems being checked.

We contact you first. If something in your account looks like one of the cases above, we’ll email you, explain what we’re seeing, and give you a reasonable chance to adjust it — in most cases it turns out to be a misconfiguration rather than intent.

We only suspend or limit an account without that conversation where usage is actively harming a third party or the service itself, or where we can’t reach you. We won’t silently slow your checks down as a substitute for talking to you.

Your interval is the target we schedule against, and the minimum your plan allows — every 30 seconds on Team and Max, every 60 seconds on Solo. Real check times can vary by a few seconds either side depending on how long a target takes to respond. Scheduling is fair across accounts, so a large fleet on one account doesn’t push another account’s checks late.