Skip to content

Is Glassdoor down?

Glassdoor publishes no status we can read

Right now

Unknown. No machine-readable official status; see their status page.

No official machine-readable status

For agents

proceed

Proceed.

GET upbutler.com/status/glassdoor/status.agent.json

MCP: upstream_status {"service":"glassdoor"}

Company reviews and salaries. Glassdoor publishes no status page and no public API, and its site answers automated requests with a bot check.

What Glassdoor says

Glassdoor publishes no status page.

Their site: glassdoor.com

What UpButler measured

There is no keyless endpoint of Glassdoor that says anything useful, so UpButler does not probe it. To check your own Glassdoor account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Glassdoor incidents, last 90 days

Without a machine-readable source there is no incident history to show. Glassdoor keeps its own at glassdoor.com.

Get alerted when Glassdoor goes down

Glassdoor publishes no incidents we can read, so there is nothing to send an alert about. If you depend on it, monitor your own use of it: add a monitor with your key or URL.

Status badge

Show Glassdoor's current status in a README or an internal wiki. It updates by itself.

Glassdoor status badge

[![Glassdoor status](https://upbutler.com/status/glassdoor/badge.svg)](https://upbutler.com/status/glassdoor)

Tell your outage from Glassdoor's

Declare that your project depends on Glassdoor. When one of your monitors fails while Glassdoor has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

upbutler.yaml
# upbutler.yaml
dependencies:
  - glassdoor
Ask before you retry
curl -s https://upbutler.com/status/glassdoor/status.agent.json
status.agent.json (live)
{
  "schema": "upbutler.upstream-status/v1",
  "service": "glassdoor",
  "verdict": "proceed",
  "status": "unknown",
  "reason": "No machine-readable official status; see their status page",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Glassdoor down right now?
We cannot tell. Glassdoor publishes no status page. Their own status page is at https://glassdoor.com.
Where does this status come from?
Glassdoor publishes no status page.
How can my agent or app check Glassdoor status?
Fetch https://upbutler.com/status/glassdoor/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"glassdoor"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Glassdoor's?
Add "glassdoor" to the dependencies of your UpButler workspace. When one of your monitors fails while Glassdoor has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with Glassdoor. Status and incident text belong to Glassdoor and are read from their public status source; the probe result is UpButler's own measurement.