How does RealUptime check Target?

RealUptime checks Target with scheduled HTTP requests to its public, unauthenticated functional endpoints, run from named regions on a fixed cadence, plus an extra check whenever a signal suggests a problem. A passing check shows that the functional endpoints we check answered our request, not that every feature of Target works for users.

What does "degraded" mean for Target?

Degraded means Target answered our check but at several times its own seven-day median response time. Degraded only ever applies to a reading that answered: a surface that fails our check, or one that refused it, is shown as a failed check or as awaiting data instead, never softened into "degraded".

What is Target's current response time?

RealUptime's most recent response time for Target, by region: US-East: 1409 ms. This is the latest single check reading per region, not an average.

When did RealUptime last check Target?

RealUptime's checks last ran against Target at 2026-11-05T15:40:01.390Z.

Is Target down?

Q: Is Target down right now?

Awaiting data. Our checks of Target pass from 1 of the 2 regions we check, and have no usable reading from the rest. A missing reading is an absence of data, not an all-clear and not an outage.

Short linkrlup.io/down/target

I'm having a problem

Awaiting datachecked 3 minutes ago

Our checks of Target pass from 1 of the 2 regions we check, and have no usable reading from the rest. A missing reading is an absence of data, not an all-clear and not an outage.

As of Nov 5, 2026, 3:40 PM UTC, RealUptime's check of Target passed in US-East, the only region with a reading for it. RealUptime could not obtain a reading from US-West, which is a fact about our own check there and is not evidence about Target.

Front-door and live API checks

Our checks of Target did not fail from two or more distant regions in the 77 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.

our check readinglive · checked Nov 5, 2026, 3:40 PM UTC

US-East1409 msChecks passing

US-West1018 msCheck failed

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.8sp95 · latest

2.5s1.3s0ms

Oct 7Oct 21Nov 5

US-West

1.3sp95 · latest

2.5s1.3s0ms

Oct 7Oct 21Nov 5

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 our checks show, and what people reported

North America
Awaiting dataUS-East, US-West, US-Central, Canada
- US-East
  Checks passinglatency: 1409msstatus code: 401checked: Nov 5, 2026, 3:29 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
  Awaiting datalatency: no responsestatus code: nonechecked: no data yet
  0 people in the last 5 minutesNot enough reports to sayWe hold no current probe reading for Target from US-West, and not enough reports from there to say anything on their own.
- 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

Live, 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>

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 Target down?", https://realuptime.io/outages/target. The readings change with every check, so give the date you read them.

How our checks compare with Target's stated SLA

Window

What you pay per month

Uptime target in your contract

Include events only one region saw (none)

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/

secondary

https://www.target.com/s?searchTerm=milk

secondary

https://www.target.com/store-locator/find-stores

secondary

https://www.target.com/l/target-circle/-/N-pzno9

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.

Related services

ANA (All Nippon Airways)AOL Mail AT&T Accor Aeroméxico

Is Target down?

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

Target response time, by region

Check your own site while you wait on Target

What we measured, function by function

What our checks show, and what people reported

Recent probe events

Put this badge in your README

How our checks compare with Target's stated SLA

What we check

What our check can and cannot see

Related services