Is Temu down right now?

We cannot tell. Temu publishes no status page. Their own status page is at https://temu.com.

How can my agent or app check Temu status?

Fetch https://upbutler.com/status/temu/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":"temu"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Temu's?

Add "temu" to the dependencies of your UpButler workspace. When one of your monitors fails while Temu 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.

Is Temu down?

Temu 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/temu/status.agent.json

MCP: upstream_status {"service":"temu"}

Temu listings. Temu publishes no status page and has no public API to probe.

What Temu says

Temu publishes no status page.

Their site: temu.com

What UpButler measured

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

Temu incidents, last 90 days

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

Get alerted when Temu goes down

Temu 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 Temu's current status in a README or an internal wiki. It updates by itself.

[![Temu status](https://upbutler.com/status/temu/badge.svg)](https://upbutler.com/status/temu)

Tell your outage from Temu's

Declare that your project depends on Temu. When one of your monitors fails while Temu 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.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - temu

Ask before you retry

curl -s https://upbutler.com/status/temu/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "temu",
  "verdict": "proceed",
  "status": "unknown",
  "reason": "No machine-readable official status; see their status page",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Temu down right now?: We cannot tell. Temu publishes no status page. Their own status page is at https://temu.com.
Where does this status come from?: Temu publishes no status page.
How can my agent or app check Temu status?: Fetch https://upbutler.com/status/temu/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":"temu"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Temu's?: Add "temu" to the dependencies of your UpButler workspace. When one of your monitors fails while Temu 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 Temu. Status and incident text belong to Temu and are read from their public status source; the probe result is UpButler's own measurement.