Skip to content

Outage tracker / JD.com

Is JD.com down?

Short linkrlup.io/down/jd-com

I'm having a problem

Checks passingchecked 1 minute ago

Our checks of JD.com pass from all 4 regions we check.

As of Nov 5, 2026, 2:08 PM UTC, RealUptime's checks of JD.com passed in all 4 regions that returned a reading.

Front-door and live API checks

Our checks of JD.com did not fail from two or more distant regions in the 3 days we have checked it (since Nov 2, 2026). This does not show JD.com works for users.

Email me when our checks of JD.com fail from two or more distant regions

One email when our checks of JD.com fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not JD.com's official status.

our check readinglive · checked Nov 5, 2026, 2:08 PM UTC
US-East2413 msChecks passing
US-West2818 msChecks passing
Europe2166 msChecks passing
Asia-Pacific2016 msCheck failed
their status pagetheir claim, not our reading

JD.com publishes no status feed we can read, so the only reading here is our check reading on the left.

JD.com response time, by region

US-East
3.2sp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 4.3s2026-11-03 UTC: p95 3.0s2026-11-04 UTC: p95 3.0s2026-11-05 UTC: p95 3.2s
Oct 7Oct 21Nov 5
US-West
3.2sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 3.1s2026-11-03 UTC: p95 3.3s2026-11-04 UTC: p95 3.1s2026-11-05 UTC: p95 3.2s
Oct 7Oct 21Nov 5
Europe
3.2sp95 · latest
5s2.5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 3.0s2026-11-03 UTC: p95 3.2s2026-11-04 UTC: p95 2.7s2026-11-05 UTC: p95 3.2s
Oct 7Oct 21Nov 5
Asia-Pacific
2.9sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 5.1s2026-11-03 UTC: p95 3.2s2026-11-04 UTC: p95 3.0s2026-11-05 UTC: p95 2.9s
Oct 7Oct 21Nov 5

Check your own site while you wait on JD.com

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not JD.com. It cannot diagnose JD.com's own systems.

What we measured, function by function

JD.com answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Awaiting dataUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 2413msstatus code: 200checked: Nov 5, 2026, 2:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach JD.com normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 2818msstatus code: 200checked: Nov 5, 2026, 2:07 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach JD.com normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionJD.com is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionJD.com is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionJD.com is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 2166msstatus code: 200checked: Nov 5, 2026, 1:56 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach JD.com normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionJD.com is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2016msstatus code: 200checked: Nov 5, 2026, 1:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach JD.com normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionJD.com is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionJD.com is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using JD.com, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for JD.com yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for JD.com.

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring JD.com since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for JD.com covering any window you pick, with our check readings and JD.com's own claim at the time, side by side.

Full check history for JD.com: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

JD.com uptime by RealUptime's checksLive, from this page's own readings.
[![JD.com uptime by RealUptime's checks](https://realuptime.io/outages/jd-com/badge.svg?days=30)](https://realuptime.io/outages/jd-com)
<a href="https://realuptime.io/outages/jd-com"><img src="https://realuptime.io/outages/jd-com/badge.svg?days=30" alt="JD.com uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is JD.com down?", https://realuptime.io/outages/jd-com. The readings change with every check, so give the date you read them.

How our checks compare with JD.com's stated SLA

At or above your target

Our checks of JD.com failed for none over the 71h 54m since we started checking it on 2026-11-02, which is 100% uptime by our checks. A 99.9% target allows 4 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from JD.com's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.jd.com/routerjson
secondary
https://www.jd.com/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: api.jd.com

RealUptime is not affiliated with JD.com; the name identifies what we checked, and nothing here speaks for JD.com's own team. We send a single web request to JD.com from 4 regions on our own schedule and time the response. We do not see inside JD.com's systems, do not use an account or real transaction, and are not the same signal JD.com's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for JD.com is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. JD.com operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 2444 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

ANA (All Nippon Airways)AOL MailAT&TAccorAeroméxico