Skip to content
PulseWatchOUTAGE.INTEL
Target logo

E-commerce

Is Target down right now?

NormalOfficial status last polled Oct 12, 2026 19:13 UTCtarget.comOfficial status page

Target.com online retail

Are you on the Target team and see something inaccurate? Report it to us. We respond within one business day.

Is Target down right now?

No. Target has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 12, 2026 20:15 UTC

Normal

Target is operating normally

As of Oct 12, 2026 20:15 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Apr 29, 2026 03:33 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Target.

0

Incident days

30

No recorded incident

0 min

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Target. Hover a day for detail.

Sep 13Sep 18Sep 23Sep 28Oct 3Oct 801234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

0

Days with incidents

0 incidents

Busiest day

0 min

Recorded duration

Report volume

0 reports in last 24H

08:15 PM11:45 PM03:15 AM06:45 AM10:15 AM01:45 PM05:15 PM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Target outage on April 29 — 24 minutes disruption

Apr 29, 03:08 AM → Apr 29, 03:33 AM · 24 minutes · high

On April 29, 2026, we experienced a service outage affecting Target that lasted for 24 minutes. The incident began at 03:08 UTC and was resolved by 03:33 UTC. During this time, user reports indicated issues categorizing primarily as security related.

Peak reports
3
in 15 min
Total reports
3
during the incident
Duration
24 minutes
tracked by PulseWatch

Impact

Users reported a total of three incidents during the outage, all classified as security issues. No specific regions were noted as being more affected than others, indicating a broad but unidentified impact. While reports peaked at three in a 15-minute period, the issue led to concern regarding security features of the service. All reported issues were addressed promptly.

Top reported issues

  • Security issue3

Incident timeline

  1. Apr 29, 03:08 AM

    PulseWatch detected elevated report volume (high severity)

  2. Apr 29, 03:15 AM

    Peak of 0 reports in 15 minutes (baseline 1.3)

  3. Apr 29, 03:33 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. Apr 29, 03:33 AM

    Security issue clustered from 1 source across 3 signals. Suppressed 2 redundant alerts.

Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals and the sources listed above.

Reliability

Detected by PulseWatch

30-day uptime

99.99%

90-day uptime

99.99%

Calculated from Target's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other e-commerce services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedHigh

69eb5b079e89bcef11c838d1: grouped 3 related Security issue alerts into one incident to reduce noise.

4/29/2026, 3:08:24 AM · 24 min

03:08 AM03:33 AM
Detection4/29/2026, 3:08:24 AM · 5mo ago

Detected — high severity

69eb5b079e89bcef11c838d1: grouped 3 related Security issue alerts into one incident to reduce noise.

ResolvedHigh

69eb5b079e89bcef11c838d1: grouped 3 related Security issue alerts into one incident to reduce noise.

4/29/2026, 3:08:24 AM · 4 min

03:08 AM03:13 AM
Detection4/29/2026, 3:08:24 AM · 5mo ago

Detected — high severity

69eb5b079e89bcef11c838d1: grouped 3 related Security issue alerts into one incident to reduce noise.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Target enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

target.com