Skip to content
PulseWatchOUTAGE.INTEL
X logo

Social

Is X down right now?

UnknownOfficial status last polled Sep 7, 2026 15:54 UTCx.comOfficial status page

X social platform availability, including timelines, posting, login, media, notifications, and API access.

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

Is X down right now?

Unknown. X does not have a conclusive current status. A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health. No current vendor status signal: vendor status was last polled on 2026-09-07, more than 7 days ago. The most recent attempt on 2026-09-27 could not be acquired.

Status as of Sep 27, 2026 07:26 UTC

Unknown

X: status unknown

As of Sep 27, 2026 07:26 UTC

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

0

Last incident

May 1, 2026 21:33 UTC

Trend

0/15m

Monitoring

Coverage gap

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 X.

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 X. Hover a day for detail.

Aug 29Sep 3Sep 8Sep 13Sep 18Sep 2301234

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

07:15 AM10:45 AM02:15 PM05:45 PM09:15 PM12:45 AM04:15 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

X outage on May 1 — 19-minute disruption

May 1, 09:13 PM → May 1, 09:33 PM · 19 minutes · high

On May 1, 2026, service X experienced an outage that was detected through user reports. The incident began at 21:13 UTC and was resolved at 21:33 UTC, lasting approximately 19 minutes. During this period, users reported issues with social platform functionality.

Peak reports
8
in 15 min
Total reports
1
during outage
Duration
19 minutes
until recovery

Impact

During the 19-minute outage, users primarily reported issues related to social platform functionality. A total of 8 peak reports were received within a 15-minute window, with one total report during the incident specifically mentioning social platform issues. The majority of these reports originated from users in the United States. This indicates that users in the affected regions experienced disruptions when attempting to use social platform features within service X.

Top reported issues

  • Social platform issues1

Most affected regions

  • United States1

Outage timeline

  1. May 1, 09:13 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 1, 09:15 PM

    Peak of 0 reports in 15 minutes (baseline 1.3)

  3. May 1, 09:33 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 1, 09:13 PM

    X status page acknowledged the incident.

    View official source
  2. May 1, 09:33 PM

    Manually added after outage observation: X is down.

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

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: X is unknown, so there is no incident history to measure and no uptime figure is shown.

Other social 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

X is currently showing social platform outage reports.

5/1/2026, 9:13:41 PM · 19 min

09:13 PM09:33 PM
Detection5/1/2026, 9:13:41 PM · 4mo ago

Detected — high severity

X is currently showing social platform outage reports.

ResolvedLow

Elevated reports for X / Twitter — resolved

4/22/2026, 1:05:20 AM · 34 min

01:05 AM01:39 AM
Detection4/22/2026, 1:05:20 AM · 5mo ago

Detected — low severity

Elevated reports for X / Twitter — resolved

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment X 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
Unknown
Monitoring
A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health. No current vendor status signal: vendor status was last polled on 2026-09-07, more than 7 days ago. The most recent attempt on 2026-09-27 could not be acquired.
Coverage
Reachability and crowd signals only; not independently verifiable
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

x.com