CheckUpstream measured Segment at 100.000% availability across 2836 independent checks (global · api). 14 incidents were recorded in the past 12 months; the most recent resolved 13 days ago after 4 hours. Status signals are polled from Segment's official Atlassian Statuspage status page, alongside independent probes and community reports.
90 days measured availability how this is computed
100.000%
global · api · n=2836 · p95 398ms (30d)
Share of our own checks against Segment endpoints that returned Segment's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 8 incidents · 59 of 90 days with none posted · 8d 17h of declared impact
Fewer incidents in the last 30 days than 25% of 232 tracked services.
Share of each window with no impact declared by Segment
7d
100.000%
30d
98.959%
90d
90.299%
180d
94.948%
1y
97.509%
Downtime like this can be refundable
If you're a paying Segment customer, outages in these windows may count against Segment's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Segment entitlement →Does Segment actually matter to you?
A Segment outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 8 incidents Segment published and resolved in the last 90 days, measured between their own start and resolution times. It describes how long Segment takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 18, 17:49 UTC · resolved in 4h 20m · Resolved
Aug 6, 15:19 UTC · resolved in 14h 51m · Resolved
Jul 26, 01:43 UTC · resolved in 2h 37m · Resolved
Live Segment status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/segment)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Segment is currently Operational. CheckUpstream tracks Segment in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Segment's last resolved incident started 13 days ago and lasted 4h 20m (a partial outage).
Looking for the live "is Segment down" view? See the Segment Live status page.
Jul 25, 22:45 UTC · resolved in 6h 4m · Resolved
Apr 13, 19:02 UTC · resolved in 22m · Resolved
Apr 9, 16:40 UTC · resolved in 3h 20m · Resolved
Apr 7, 17:07 UTC · resolved in 1h 23m · Resolved
Segment's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Segment endpoints. It is the share of checks that returned the expected response, not a figure taken from Segment's status page.
Sign up to CheckUpstream and add Segment to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Segment's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.