Integration guide

Listing your product on GlobalOutageMap needs no technical work at all. If you want more accurate status detection later, you can optionally expose one tiny public health endpoint.

Option A - No setup required

Default

You do not need to change your website for basic monitoring.

Add your product.
Confirm your email.
We review and approve the listing.
GlobalOutageMap checks your public URL automatically.
Your product gets a public GlobalOutageMap status page.
Visitors can Watch it and get notified when something looks wrong.

This is already useful on its own. Technical integration is entirely optional.

Add your product

Option B - Enhanced monitoring

Optional

Basic monitoring tells us whether your public site is reachable. Sometimes a homepage still returns 200 while your actual app or API is broken.

For better accuracy, expose one small public endpoint:

https://example.com/.well-known/globaloutagemap

It returns a deliberately tiny JSON document:

{
  "status": "operational",
  "message": "All systems operational",
  "updated_at": "2026-09-03T12:00:00Z"
}

Allowed status values: operational, degraded, down, maintenance. The fields message and updated_at are optional. Components, regions, metrics and custom status values are not supported, keep it tiny.

Requirements

publicly reachable, no authentication
returns application/json
responds quickly and is read-only
exposes only high-level public health information

Never expose

API keys or database credentials
environment variables
stack traces
private or internal IP addresses
customer information
internal infrastructure details

Using Lovable, Cursor, Claude Code, Replit or another AI builder?

1 prompt

Copy this prompt into your AI builder and it will create the endpoint for you.

AI builder prompt

Add a public GlobalOutageMap health endpoint to my application.

Create:

/.well-known/globaloutagemap

It must return "application/json" in this format:

{
  "status": "operational",
  "message": "All systems operational",
  "updated_at": "<current ISO timestamp>"
}

Allowed status values:

operational
degraded
down
maintenance

Requirements:

- public endpoint
- no authentication
- read-only
- fast
- do not expose secrets
- do not expose environment variables
- do not expose stack traces
- do not expose private/internal infrastructure
- do not expose customer information

Where possible, derive the status from existing application health logic rather than returning a permanently hardcoded status.

If the project already has a health endpoint, reuse its logic instead of duplicating it.

Test your endpoint

Switching later

You can start with basic monitoring and add a health endpoint whenever you like. Your provider page, watchers, history and incidents stay exactly the same, nothing is reset.

If a health endpoint temporarily breaks or returns invalid JSON, we do not report your product as down. We fall back to the normal public availability check until the endpoint works again.