Skip to content

Outage tracker / Target

Is Target down?

Short linkrlup.io/down/target

I'm having a problem

Operationalchecked 35 minutes ago

We reached Target from all 2 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Target (since Aug 20, 2026).

our independent probeslive · checked Sep 3, 2026, 12:54 AM UTC
US-East414 msOperational
US-West119 msOperational

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 independent reading here is ours on the left.

Target response time, by region

US-East
414msp95 · 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-08-20 UTC: p95 900ms2026-08-21 UTC: p95 815ms2026-08-22 UTC: p95 1.0s2026-08-23 UTC: p95 488ms2026-08-24 UTC: p95 452ms2026-08-25 UTC: p95 494ms2026-08-26 UTC: p95 608ms2026-08-27 UTC: p95 630ms2026-08-28 UTC: p95 464ms2026-08-29 UTC: p95 471ms2026-08-30 UTC: p95 581ms2026-08-31 UTC: p95 525ms2026-09-01 UTC: p95 570ms2026-09-02 UTC: p95 501ms2026-09-03 UTC: p95 414ms
Aug 5Aug 19Sep 3
US-West
162msp95 · 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-08-20 UTC: p95 1.0s2026-08-21 UTC: p95 965ms2026-08-22 UTC: p95 1.0s2026-08-23 UTC: p95 461ms2026-08-24 UTC: p95 604ms2026-08-25 UTC: p95 591ms2026-08-26 UTC: p95 442ms2026-08-27 UTC: p95 1.4s2026-08-28 UTC: p95 660ms2026-08-29 UTC: p95 727ms2026-08-30 UTC: p95 646ms2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 603ms2026-09-02 UTC: p95 637ms2026-09-03 UTC: p95 162ms
Aug 5Aug 19Sep 3

Is it Target, or is it you?

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: OperationalUS-West: OperationalEurope: 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: OperationalUS-West: OperationalEurope: 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 we measured, and what people reported

  • US-East
    Operationallatency: 414msstatus code: 401checked: Sep 3, 2026, 12:42 AM 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
    Operationallatency: 119msstatus code: 401checked: Sep 3, 2026, 12:54 AM 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.
  • Europe
    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 regionTarget is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • 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
  • UK
    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
  • South America
    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 outages

No outages on record yet for Target.

measured 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 measurements and Target's own claim at the time, side by side.

Full availability history for Target: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Target, and again when they can reach it again. That is our own measurement from ten regions, not Target's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Target uptime measured by RealUptimeLive, from this page's own readings.
[![Target uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Target's SLA implies, from our measurement

At or above your target

We measured none of downtime for Target over the 337h 29m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, 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/
RealUptime is not affiliated with Target; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Target's online store serves United States shoppers, so we check it from our US regions only. Read the full methodology.

Related services

AirbnbAmazonApple iCloudBest BuyBooking.com