Checks, locations & failure confirmation — found from sitemap — openstatus

Cited by

Facts read from this source

• Private location definition Report an error

  “A private location is a monitoring probe you run on your own infrastructure. Instead of openstatus checking your endpoint from one of its public regions, a container you control performs the check and reports the result back over an outbound connection.”

• Private location use cases Report an error

  “Internal APIs and services behind a corporate firewall or VPC. Databases, message brokers, or other backing services that don't expose a public port. Services in a region openstatus doesn't offer a public probe in.”

• Private location container image Report an error

  “You deploy the openstatus probe container — typically ghcr.io/openstatushq/private-location:latest — somewhere inside the network that needs to be monitored.”

• Private location connection Report an error

  “you only need outbound network access from the probe to the openstatus ingest endpoint, openstatus-private-location.fly.dev, on port 443. No inbound firewall rules, no exposed ports, no reverse tunnel”

• Private location auth Report an error

  “The probe opens an outbound, authenticated connection to the openstatus platform using the token issued when you created the location.”

• Private location self host ingest URL Report an error

  “If you self-host openstatus, point the probe at your own ingest server with the OPENSTATUS_INGEST_URL environment variable”

• Private location cost model Report an error

  “Cost model Included with monitor checks You pay for the host/container”

• Private location incidents alerts Report an error

  “Auto-incident & alerts Yes Yes”

• Private location status pages Report an error

  “Use on public status pages Yes Yes”

• Hybrid monitor locations Report an error

  “A monitor can be assigned to public locations, private locations, or both.”

• Private location egress dependency Report an error

  “an egress firewall that blocks openstatus-private-location.fly.dev:443 will silently stop the probe from running checks. The probe will appear "connected" briefly and then go quiet.”

• Private location cloudflare containers Report an error

  “Deploy a private probe on Cloudflare Containers — a serverless deployment pattern instead of a long-running container.”

• Private location guide Report an error

  “Set up a private location — step-by-step deployment of the Docker probe.”

Scores citing this record

• The Agency Developer Checks, locations & failure confirmation
• The Agency Developer Pricing transparency
• The Customer Support Lead Checks, locations & failure confirmation
• The Customer Support Lead European sovereignty
• The E-Commerce Operations Manager Checks, locations & failure confirmation
• The SaaS Platform Engineer Checks, locations & failure confirmation
• The SaaS Platform Engineer Pricing transparency
• The Information Security Officer Checks, locations & failure confirmation
• The Information Security Officer Pricing transparency
• The Skeptic Checks, locations & failure confirmation