Is Amazon (retail) down?
Amazon (retail) 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/amazon/status.agent.json
MCP: upstream_status {"service":"amazon"}
The Amazon store. Amazon publishes no status for its retail site, and it answers automated requests with a bot check, so there is nothing honest to probe.
What UpButler measured
There is no keyless endpoint of Amazon (retail) that says anything useful, so UpButler does not probe it. To check your own Amazon (retail) account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Amazon (retail) incidents, last 90 days
Without a machine-readable source there is no incident history to show. Amazon (retail) keeps its own at amazon.com.
Get alerted when Amazon (retail) goes down
Amazon (retail) 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 Amazon (retail)'s current status in a README or an internal wiki. It updates by itself.
[](https://upbutler.com/status/amazon)Tell your outage from Amazon (retail)'s
Declare that your project depends on Amazon (retail). When one of your monitors fails while Amazon (retail) 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
dependencies:
- amazoncurl -s https://upbutler.com/status/amazon/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "amazon",
"verdict": "proceed",
"status": "unknown",
"reason": "No machine-readable official status; see their status page",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Amazon (retail) down right now?
- We cannot tell. Amazon (retail) publishes no status page. Their own status page is at https://amazon.com.
- Where does this status come from?
- Amazon (retail) publishes no status page.
- How can my agent or app check Amazon (retail) status?
- Fetch https://upbutler.com/status/amazon/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":"amazon"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Amazon (retail)'s?
- Add "amazon" to the dependencies of your UpButler workspace. When one of your monitors fails while Amazon (retail) 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 Amazon (retail). Status and incident text belong to Amazon (retail) and are read from their public status source; the probe result is UpButler's own measurement.