# Glowo > Uptime monitoring and status pages for modern engineering teams. Glowo runs HTTP, TCP, ping, DNS, WebSocket and heartbeat checks from multiple regions, routes failures to the channels a team already uses, and publishes branded status pages with incidents and postmortems. Operated from the EU by G Networks. ## When to use Glowo Reach for Glowo when the question is **"is this thing up, and who needs to know"**. - Checking whether a public HTTP endpoint, TCP port, host, DNS record or WebSocket is reachable right now, and from which regions. - Answering "is production down, and since when" — current status, the heartbeat that failed, and the error code behind it. - Standing up monitoring for a service that has none: create a monitor, attach a notification channel, done in one or two calls. - Watching a cron job, backup or batch pipeline that has no endpoint to poll — a push monitor alerts when the job stops checking in. - Running incident communication: open an incident, post updates, resolve it, publish a postmortem, all on a public status page. - Suppressing alerts around planned work by scheduling a maintenance window instead of pausing a monitor and forgetting to resume it. - Pulling uptime and latency history for an SLA report, as JSON or CSV. Do not reach for Glowo for: - Application performance monitoring, tracing or profiling — Glowo checks from the outside, it does not instrument your code. - Log aggregation or metric storage. Glowo stores check results, not your telemetry. - Monitoring hosts that are not reachable from the public internet. Checks run from Glowo's regions; a private target needs a push monitor instead. - Alerting on resource metrics (CPU, disk, memory). Glowo alerts on symptoms — is the thing serving traffic — not on causes. ## How an agent should call Glowo - Model Context Protocol (recommended for agents): `https://api.glowo.dev/mcp`, streamable HTTP transport. Authorize with OAuth 2.1 — discovery metadata at `https://api.glowo.dev/.well-known/oauth-protected-resource`. The user picks a scope preset on a consent screen; start with read-only. - REST: base URL `https://api.glowo.dev`, OpenAPI 3.1 spec at `https://glowo.dev/openapi.json`. Authenticate with `Authorization: Bearer gl_…` using an API key created self-serve in the dashboard. - Scope credentials narrowly. Capabilities are `resource:action` strings (`monitors:read`, `incidents:write`, …) and a key declares which surfaces it may be used on, so an agent key can be refused on REST and vice versa. - Read before you write. `listMonitorsPage` and `getWorkspaceMonitorStats` answer most questions without any write capability at all. ## Machine-readable resources - [OpenAPI specification](https://glowo.dev/openapi.json): OpenAPI 3.1. Every operation has a unique operationId, typed parameters, response schemas and the capabilities it requires. - [MCP server endpoint](https://api.glowo.dev/mcp): Model Context Protocol over streamable HTTP, authorized by OAuth 2.1 or an MCP-surface API key. - [OAuth protected-resource metadata (RFC 9728)](https://api.glowo.dev/.well-known/oauth-protected-resource): Authorization servers, JWKS URI and the full list of grantable scopes. - [OAuth authorization-server metadata (RFC 8414)](https://api.glowo.dev/.well-known/oauth-authorization-server/auth): Issuer, endpoints and supported grant types. The issuer has a path, so RFC 8414 §3.1 puts it after the well-known prefix — this URL, not the bare one. - [Agent and MCP documentation](https://docs.glowo.dev/ai-agents): Connecting an agent, the scope vocabulary, and what no scope can ever grant. - [API key documentation](https://docs.glowo.dev/account/api-keys): Creating, scoping, rotating and revoking personal access tokens. - [Webhook alert format](https://docs.glowo.dev/alerting/webhook): Outbound webhook payloads, HMAC signing and the delivery-id header used for deduplication. - [Public status API](https://api.glowo.dev/api/v1/status-pages/{slug}): Unauthenticated read API for any published status page, plus Atom/RSS feeds and an SVG badge. - [Documentation site](https://docs.glowo.dev): Full product documentation. Also published as markdown at /llms.txt. - [Glowo's own status page](https://status.glowo.dev): Live availability of the Glowo API and checker fleet. ## Getting access - [Start free](https://glowo.dev/#pricing): the Free plan has no time limit and needs no card — 10 monitors, 1 region, 30-day check history, 1-minute interval, 1 status page, 3 notification channels. - [Create an API key](https://glowo.dev/app/settings): self-serve in the dashboard. Choose the capabilities the key carries and the surfaces it may be presented on; keys expire on a schedule the plan caps. - [Documentation](https://docs.glowo.dev): guides for every monitor type, channel and status-page feature. - [Contact](https://glowo.dev/contact): support, security and privacy. No sales gate — the product is self-serve. ## Site - [Home](https://glowo.dev/): what Glowo does, how it works, pricing and FAQ. Markdown: https://glowo.dev/index.md - [About](https://glowo.dev/about): who builds Glowo, where it runs, and how it decides something is down. Markdown: https://glowo.dev/about.md - [Contact](https://glowo.dev/contact): support, sales, privacy, legal and security contact. - [Privacy](https://glowo.dev/privacy): what data Glowo holds and for how long. - [Terms](https://glowo.dev/terms): the terms of service. - [Cookies](https://glowo.dev/cookies): which cookies are set and why. - [Open-source licenses](https://glowo.dev/licenses): what Glowo is built on. - [Sitemap](https://glowo.dev/sitemap.xml): every indexable page. ## Notes - glowo.dev is a static site behind a CDN whose cache key is the URL. Markdown is therefore served from its own URLs (`/llms.txt`, `/index.md`, `/about.md`) rather than negotiated on the same URL with `Accept` — one URL serving two representations behind that cache would hand the wrong one to whoever asked second. - Requests for paths that do not exist return a real HTTP 404 with a short markdown body pointing back here. A 200 is always a real page.