Run a check

The website down checker is a one-shot ping. You do not sign in. Nothing is stored after you leave the page.

It answers: is this URL up from many cities, or only some? That is different from a Check, which keeps samples and a 24-hour bar.

Run a check

1. Open the homepage and scroll to Is it down right now? (or go to /#checker).
2. Type a hostname or URL. Placeholder: example.com. Fine print: A URL is the address of a website, like https://scaledpapers.com.
3. Click Check. The button reads Checking… while probes run. The loading line says checking from 16 locations…

If you omit http:// or https://, https:// is added. Only http and https URLs with a real hostname are accepted. Invalid input stays on the form with an error (no results panel). The form is rate-limited if you check the same address too often.

What you see

Before the first check, the side panel is a Global status preview (Example result across 16 locations).

After Check:

• Overall badge: Online, Degraded, or Down
• URL (linked) and Date checked (your local time)
• Cities grouped by continent. Each card: {city} ({aws region}), Online / Offline, latency in ms, and a status line such as 200 OK or 408 TIMEOUT
• Per-region rows: median latency, X/Y online, worst HTTP status or no response
• Verdict:
  • All up: This URL is up and reachable from all {N} locations.
  • Partial: This URL is failing from {offline} of {total} locations.

A location is Online when the HTTP status is below 500 (same idea as Website checks in the console). Footer: Want continuous checks with incident history? links to the console and the ScaledPapers status page.

The 16 cities

These are not the five Americas regions used by console Checks. São Paulo, Europe, Asia, and Sydney exist only on this one-shot tool today.

Checker vs Checks

For a public customer page that stays current, add a Check if you want automated samples, link it to a component if you want incidents to follow the probe, or post incidents yourself.