Skip to content
PulseWatchOUTAGE.INTEL
Segment logo

Other

Is Segment down right now?

NormalOfficial status last polled Sep 29, 2026 16:25 UTCsegment.comOfficial status page

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

Is Segment down right now?

No. Segment 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 Sep 29, 2026 16:41 UTC

Normal

Segment is operating normally

As of Sep 29, 2026 16:41 UTC

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

Reports 24h

0

Last incident

Sep 16, 2026 22:41 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 Segment.

2

Incident days

28

No recorded incident

4h 48m

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

Aug 31Sep 5Sep 10Sep 15Sep 20Sep 2501234

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

2

Days with incidents

1 incident

Busiest day

4h 48m

Recorded duration

Report volume

0 reports in last 24H

04:30 PM08:00 PM11:30 PM03:00 AM06:30 AM10:00 AM01:30 PM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Segment outage on September 16 — 2h 24m disruption

Sep 16, 08:16 PM → Sep 16, 10:41 PM · 2h 24m · medium

A service disruption affecting Segment was detected via automated monitoring signals. The incident began on September 16, 2026, at 20:16 UTC and was resolved on September 16, 2026, at 22:41 UTC.

Peak reports
0
in 15 min
Total reports
0
during outage
Duration
2h 24m
until recovery

Impact

During the 2-hour and 24-minute incident, Segment experienced a medium-severity disruption. This incident was detected through automated signals, including the vendor's own status page. No user-reported data was collected for this incident, and its impact was assessed solely based on automated monitoring.

Outage timeline

  1. Sep 16, 08:16 PM

    PulseWatch detected the incident from automated vendor and probe signals (medium severity)

  2. Sep 16, 08:16 PM

    Status updated: possible issue

  3. Sep 16, 10:41 PM

    Signals cleared — incident resolved

Official updates

  1. Sep 16, 08:16 PM

    Segment status page acknowledged the incident.

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

Reliability

Detected by PulseWatch

30-day uptime

99.33%

90-day uptime

99.73%

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

Other other 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 →
ResolvedMedium

Segment: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/16/2026, 8:16:54 PM · 2h 24m

08:16 PM10:41 PM
Detection9/16/2026, 8:16:54 PM · 12d ago

Detected — medium severity

Segment: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Segment incident correlated across 1 signal group: official/vendor.

9/3/2026, 6:23:54 PM · 2h 23m

06:23 PM08:47 PM
Detection9/3/2026, 6:23:54 PM · 25d ago

Detected — medium severity

Segment incident correlated across 1 signal group: official/vendor.

ResolvedMedium

Segment incident correlated across 1 signal group: official/vendor.

8/18/2026, 6:04:24 PM · 1h 2m

06:04 PM07:06 PM
Detection8/18/2026, 6:04:24 PM · 1mo ago

Detected — medium severity

Segment incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Segment 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

segment.com