Promptwatch Logo

Better Stack

Better Stack is a platform for monitoring and alerting on your applications.
Monitoring

What is Better Stack?

Better Stack checks URLs chosen by its monitoring customers. A request tests whether an application responds as expected and can contribute to an incident when it does not. The monitor already has the URL in its configuration, so this is a probe rather than a crawler following links around the site.

Current monitors send a browser-like user agent beginning Better Stack Better Uptime Bot. Monitors created under the older Better Uptime identity can use a different prefix. A single monitor may run from multiple locations, which explains why the same path can be requested from several addresses.

By default, Better Stack checks from at least four locations and opens an incident only after failures from at least three. The operator recommends firewall rules based on its user agent because monitoring IPs can change. For stricter network controls, it also publishes current addresses in machine-readable formats.

Cloudflare's bot directory says these requests do not follow robots.txt, despite the true flag preserved in this bot. That fits their direct, configured nature. Better Stack is an uptime service with no documented role in AI search or model training.

Not relevant for AI search

Is Better Stack relevant for AI search?

No. Better Stack is not part of AI search or training, so allowing or blocking it does not change your AI visibility.

Better Stack runs synthetic monitoring or uptime checks on a schedule. It is not collecting content for any index or model, so it has no bearing on search rankings or AI answers. You usually see it because your own team or a service you use set up a check.

How to handle Better Stack

Do not add a BetterStack robots.txt group. Better Stack sends requests to configured monitor URLs, and its directory entry records no robots support.

Make the monitored route fast and predictable. When bot protection rejects a legitimate check, allow the documented current and older user-agent forms, or consume Better Stack's published IP list on an automated refresh. A header rule is easier to maintain but can be spoofed; an up-to-date source allowlist is narrower.

Stop or edit an unwanted monitor in Better Stack itself. Blocking its requests while it stays active turns an access-control decision into a failed availability check and may open a false incident. For a monitor your team owns, a private request header can also separate it from other traffic using the public Better Stack identity.

Examples

  • A `/status` monitor succeeds from three locations but times out from one. Under the documented default, that isolated failure does not open an incident.
  • A WAF begins rejecting `Better Stack Better Uptime Bot`. Visitors see no outage, but the monitor fails until the team allows its chosen identification method.

Frequently asked questions about Better Stack

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

A Better Stack customer configured a monitor for that URL. Check the relevant account and monitor settings if the probe is unexpected.

Be the brand AI recommends

Monitor your brand's visibility across ChatGPT, Claude, Perplexity, and Gemini. Get actionable insights and create content that gets cited by AI search engines.

Promptwatch Dashboard