Skip to content

Outage tracker / Target

Is Target down?

I'm having a problem

Checks passingchecked 3 minutes ago

Our checks of Target pass from all 2 regions we check.

As of Oct 23, 2026, 3:57 PM UTC, RealUptime's checks of Target passed in all 2 regions that returned a reading.

Front-door and live API checks

Our checks of Target did not fail from two or more distant regions in the 64 days we have checked it (since Aug 20, 2026). This does not show Target works for users.

This reading is from our two US regions.

Email me when our checks of Target fail from two or more distant regions

One email when our checks of Target 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 Target's official status.

our check readinglive · checked Oct 23, 2026, 3:57 PM UTC
US-East1417 msChecks passing
US-West1308 msChecks passing

Target's online store serves United States shoppers, so we check it from our US regions only.

their status pagetheir claim, not our reading

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

Target response time, by region

US-East
1.3sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 428ms2026-09-25 UTC: p95 413ms2026-09-26 UTC: p95 433ms2026-09-27 UTC: p95 506ms2026-09-28 UTC: p95 410ms2026-09-29 UTC: p95 418ms2026-09-30 UTC: p95 542ms2026-10-01 UTC: p95 695ms2026-10-02 UTC: p95 516ms2026-10-03 UTC: p95 709ms2026-10-04 UTC: p95 637ms2026-10-05 UTC: p95 667ms2026-10-06 UTC: p95 671ms2026-10-07 UTC: p95 683ms2026-10-08 UTC: p95 708ms2026-10-09 UTC: p95 627ms2026-10-10 UTC: p95 623ms2026-10-11 UTC: p95 748ms2026-10-12 UTC: p95 722ms2026-10-13 UTC: p95 725ms2026-10-14 UTC: p95 786ms2026-10-15 UTC: p95 808ms2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.3s
Sep 24Oct 8Oct 23
US-West
1.7sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 504ms2026-09-25 UTC: p95 461ms2026-09-26 UTC: p95 446ms2026-09-27 UTC: p95 376ms2026-09-28 UTC: p95 466ms2026-09-29 UTC: p95 448ms2026-09-30 UTC: p95 524ms2026-10-01 UTC: p95 557ms2026-10-02 UTC: p95 509ms2026-10-03 UTC: p95 568ms2026-10-04 UTC: p95 580ms2026-10-05 UTC: p95 716ms2026-10-06 UTC: p95 768ms2026-10-07 UTC: p95 684ms2026-10-08 UTC: p95 522ms2026-10-09 UTC: p95 538ms2026-10-10 UTC: p95 769ms2026-10-11 UTC: p95 744ms2026-10-12 UTC: p95 718ms2026-10-13 UTC: p95 616ms2026-10-14 UTC: p95 678ms2026-10-15 UTC: p95 946ms2026-10-16 UTC: p95 784ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.7s
Sep 24Oct 8Oct 23

Check your own site while you wait on Target

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 Target. It cannot diagnose Target's own systems.

What we measured, function by function

Target 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: Not monitored from this regionAsia-Pacific: Not monitored from this regionUS-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: Not monitored from this regionAsia-Pacific: Not monitored from this regionUS-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: 1417msstatus code: 401checked: Oct 23, 2026, 3:52 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Target normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1308msstatus code: 401checked: Oct 23, 2026, 3:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Target 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 regionTarget is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionTarget is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionTarget 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
      Not monitored from this regionTarget is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • UK
      Not monitored from this regionTarget 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
      Not monitored from this regionTarget is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Southeast Asia
      Not monitored from this regionTarget is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionTarget 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 Target, 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 Target yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Target.

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

We have been measuring Target since August 20, 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 Target covering any window you pick, with our check readings and Target's own claim at the time, side by side.

Full check history for Target: 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

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

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Target's stated SLA

At or above your target

Our checks of Target failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 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 Target'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://redsky.target.com/redsky_aggregations/v1/web/pdp_client_v1
secondary
https://www.target.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: redsky.target.com

RealUptime is not affiliated with Target; the name identifies what we checked, and nothing here speaks for Target's own team. We send a single web request to Target from 2 regions on our own schedule and time the response. We do not see inside Target's systems, do not use an account or real transaction, and are not the same signal Target's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Target 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. Target's online store serves United States shoppers, so we check it from our US regions only. Read the full methodology.