Skip to content

Outage tracker / Segment

Is Segment down?

Short linkrlup.io/down/segment

I'm having a problem

Vendor reports no incidentWhat Segment reports

Segment reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:24 UTC.

Segment's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of Segment pass from all 4 regions we check.

As of Nov 5, 2026, 2:35 PM UTC, RealUptime's checks of Segment passed in all 4 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:35 PM UTC
US-East1041 msChecks passing
US-West624 msChecks passing
Europe905 msChecks passing
Asia-Pacific1444 msChecks passing
their status pagetheir claim, not our reading

Segment reports: All systems operational (“All Systems Operational”)

from Segment's own status page, checked Nov 5, 2026, 1:57 PM UTC
Segment's own status page shows no incident, and our checks of Segment pass right now.

Segment's own component breakdown, as they publish it

  • Analytics.js CDN (US)Operational
  • Blobstore Destinations (US)Operational
  • Cloud Sources (US)Operational
  • Data Deletions (US)Operational
  • Data Ingestion (Tracking) API (US)Operational
  • Data Lakes (US)Operational
  • Data Processing Pipeline (US)Operational
  • Engage (US)Operational
  • Libraries (US)Operational
  • Linked Audiences (US)Operational
  • Linked Events (EU)Operational
  • Public API (US)Operational
  • Reverse ETL (EU)Operational
  • Streaming Destinations (US)Operational
  • Warehouse Destinations (US)Operational
  • Web Interface (US)Operational
  • Analytics.js CDN (EU)Operational
  • Blobstore Destinations (EU)Operational
  • Cloud Sources (EU)Operational
  • Data Deletions (EU)Operational
  • Data Ingestion (Tracking) API (EU)Operational
  • Data Processing Pipeline (EU)Operational
  • Engage (EU)Operational
  • Libraries (EU)Operational
  • Linked Audiences (EU)Operational
  • Linked Events (US)Operational
  • Public API (EU)Operational
  • Reverse ETL (US)Operational
  • Streaming Destinations (EU)Operational
  • Warehouse Destinations (EU)Operational
  • Web Interface (EU)Operational
  • Profiles SyncOperational
  • Journeys (US)Operational
  • Journeys (EU)Operational

These are Segment's components, named and scored by Segment. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Segment's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Segment response time, by region

US-East
1.4sp95 · 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-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
US-West
1.7sp95 · 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-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
Europe
1.4sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Asia-Pacific
2.4sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 3.7s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5

Check your own site while you wait on Segment

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 Segment. It cannot diagnose Segment's own systems.

What we measured, function by function

Segment 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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-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

Email me when Segment reports an incident on its status page, and again when it reports it resolved.

Get an email when Segment reports an incident

Email me when Segment reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Segment's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1041msstatus code: 400checked: Nov 5, 2026, 2:34 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Segment normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 624msstatus code: 400checked: Nov 5, 2026, 2:35 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Segment normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionSegment is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionSegment is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionSegment is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 905msstatus code: 400checked: Nov 5, 2026, 2:31 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Segment normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionSegment is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1444msstatus code: 400checked: Nov 5, 2026, 2:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Segment normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionSegment is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionSegment 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 Segment, 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 Segment yet, which is not evidence that nothing is wrong.

Recent probe events

Delays to Realtime Audiences and Journeys, 2h 8mdeclared on their status page2026-11-04
Segment event delivery issues, 16h 20mdeclared on their status page2026-10-26
Audience & Journey data delivery delay in EU region, 1h 16mdeclared on their status page2026-10-02
Braze Web Event Delivery is experience event delivery issue, 8h 33mdeclared on their status page2026-10-01
Actions S3 is currently experience formatting issues with the delivered events, 2h 10mdeclared on their status page2026-09-16
SSO Login Issues with the Segment App, 1h 11mdeclared on their status page2026-09-10
Issue with Engage UI, 4h 11mdeclared on their status page2026-09-03
Segment App UI Issue with Profile Traits with no recent activity, 21h 38mdeclared on their status page2026-09-03

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Segment since November 2, 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 Segment covering any window you pick, with our check readings and Segment's own claim at the time, side by side.

Full check history for Segment: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Segment uptime by RealUptime's checksLive, from this page's own readings.
[![Segment uptime by RealUptime's checks](https://realuptime.io/outages/segment/badge.svg?days=30)](https://realuptime.io/outages/segment)
<a href="https://realuptime.io/outages/segment"><img src="https://realuptime.io/outages/segment/badge.svg?days=30" alt="Segment uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Segment down?", https://realuptime.io/outages/segment. The readings change with every check, so give the date you read them.

What we check

secondary
https://segment.com/
secondary
https://status.segment.com/
primaryfunctional: live API
https://api.segment.io/v1/track

What our check can and cannot see

A pass means the service's servers answered our request with the error they give a request that carries no account or valid input. It does not show that sign-in works or that any real request succeeds.

Host checked: api.segment.io

RealUptime is not affiliated with Segment; the name identifies what we checked, and nothing here speaks for Segment's own team. We send a single web request to Segment from 4 regions on our own schedule and time the response. We do not see inside Segment's systems, do not use an account or real transaction, and are not the same signal Segment's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Segment is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Segment operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 3693 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

1PasswordAWS (Amazon Web Services)AblyAcuity SchedulingAdobe Fonts