# Website Uptime Check

> Check whether any site or API is responding, in seconds.

Is it up? tells you whether a website or API is responding right now by sending a real request from a Postman server and reporting whether anything came back, and how long it took.

Also: is it up, is my site down, website down checker, uptime checker, api status check, is this website down, website up or down, ping a url.

## What it does

When a site looks broken the first question is whether it is actually down. This answers that in one request, sent from a Postman server: Up means the origin responded, Down means nothing came back. It is a single sample right now — monitoring on a schedule is what catches an outage you are not awake for.

## When to use it

- A site is not loading and you need to confirm whether the origin is actually down right now.
- You deployed something and want to confirm the origin is answering.
- An API integration started failing and you want to rule out a total outage before debugging.
- You want a quick reachability check without installing anything.

## What you give it

| Input | Meaning |
| --- | --- |
| URL | Any public http or https address. The scheme is added automatically if you leave it off, and www. is trimmed for display. |

## What you get back

| Output | Meaning |
| --- | --- |
| Up or Down | Up when the site responded to the browser at all; Down when nothing came back. |
| Response time | Round-trip milliseconds when the site responded. |

## How it works

- One request is sent from a Postman server to the URL and the round trip is timed.
- Up means the site responded. Down means it did not respond at all.
- The tool reports only whether the site is up and how fast; the exact HTTP status is shown by the API health check and the full Postman client.

## Key terms

- **Reachability** — whether a server answers at all, as distinct from whether it answers correctly. A site returning 500 errors is reachable but broken.
- **Synthetic check** — a request made from a server — here, a Postman server — rather than from your own machine. It answers whether the origin is up consistently, but cannot tell you whether the site is reachable specifically from your own network.
- **Monitoring versus checking** — a check is one sample right now. Monitoring is repeated checks on a schedule with alerting, which is the only way to catch an outage you are not awake for.

## Questions

### Why does it not show the HTTP status code?

By design it reports only Up or Down and the response time. If you need the exact status code and body, the API health check reads them for you.

### Does a site returning errors show as Up?

Yes. Up means the server responded. A site serving 503 errors on every request is still responding, and will report as Up here.

### It says Down but the site loads in my other tab. Why?

The check runs from a Postman server, so a site that blocks or rate-limits automated traffic can read as Down even though it loads in your browser. Treat Down as a strong signal rather than proof, and confirm with a direct visit.

### Can it check a site on my local network?

No — the check runs from a Postman server, so it can only reach publicly-accessible URLs, not localhost or an address on your private network.

### Can it watch a site continuously?

No. This is a single manual check. Scheduled checks with alerting are what Postman monitors are for.


## Privacy

The URL you enter is sent to Postman so the request can be made from a server. It is not stored, and no account is needed.

## Links

- [Use the tool](https://www.postman.com/tools/website-uptime-check) — the interactive version of this page.
- [Postman Tools](https://www.postman.com/tools) — every free tool in this set.
- [Monitors docs](https://learning.postman.com/docs/monitoring-your-api/intro-monitors/) — Postman documentation.