Is Segment down?
Segment status · Developer Tools · checked (1s ago)
Also searched as Twilio Segment.
No — Segment is not down. All Segment systems are reported operational.
According to Segment's official status page, Segment was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Segment's feed reported no outage in 100.00% of our checks.
Is Segment down for you right now?
Everything above is read from Segment's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Segment in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
What Segment is
Segment is a customer data platform: it collects events from your applications through a single API and fans them out to analytics, marketing and warehouse destinations.
What Segment's status feed covers
Segment's status page separates ingestion from delivery to destinations, and that split is the important one. Ingestion rarely fails; delivery to individual destinations degrades regularly, and when it does, events are queued and retried rather than lost. Individual destination problems are frequently the destination's fault rather than Segment's, and are posted per-destination.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
Segment uptime, last 30 days
One bar per day. Each shows the share of that day's checks where Segment's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Segment was down.
- No outage reported (99%+)
- 95–99%
- 80–95%
- Under 80%
- No data
Other services reporting problems right now
9 other services isuptime tracks were also reporting a problem as of the same check, 1s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
CloudflarePartial System Outage
- Razorpay1 of 7 services down: Payments API
- ElasticPartial System Outage
- PlayStation NetworkPlayStation Store affected in Russia
- SalesforceDegraded Performance: 1 active incident
- ScalewayPartially Degraded Service
- SnowflakePartially Degraded Service
- Temporal CloudPartially Degraded Service
Segment response time trend
Each point is one check of Segment's status endpoint.
Segment outage history
Segment has published 41 incidents in the last 12 months, the 20 most recent shown here. Only what Segment posted itself — not every problem users hit.
- Intermittent failures scheduling warehouse jobs and processing Profile Syncs
resolved · Nov 7, 12:46 AM (21h ago)
- Delays to Realtime Audiences and Journeys
resolved · Nov 4, 08:17 PM (3d ago)
- Segment event delivery issues
resolved · Oct 26, 12:30 AM (12d ago)
- Audience & Journey data delivery delay in EU region
resolved · Oct 2, 11:12 PM (35d ago)
- Braze Web Event Delivery is experience event delivery issue
resolved · Oct 1, 03:30 AM (37d ago)
- Actions S3 is currently experience formatting issues with the delivered events
resolved · Sep 16, 07:40 PM (52d ago)
- SSO Login Issues with the Segment App
resolved · Sep 10, 02:28 PM (58d ago)
- Issue with Engage UI
resolved · Sep 3, 05:53 PM (65d ago)
- Segment App UI Issue with Profile Traits with no recent activity
resolved · Sep 3, 01:04 AM (65d ago)
- Intermittent Segment application login errors
resolved · Aug 18, 05:49 PM (81d ago)
- Google ads destination intermittent delivery failure
resolved · Aug 6, 03:19 PM (93d ago)
- Notification and verification email delivery
resolved · Aug 6, 05:50 AM (93d ago)
- Data processing pipeline issue
resolved · Jul 26, 01:43 AM (104d ago)
- Connections Processing Delays
resolved · Jul 25, 10:45 PM (104d ago)
- Elevated Event Delivery Latency
resolved · Jul 15, 04:48 PM (115d ago)
- Criteo Audience destinations are experiencing an outage
resolved · Jul 3, 09:39 AM (127d ago)
- (US West 2) Partial degradation of Linked Audiences, Linked Events, Reverse ETL, and Profile Sync due to external Snowflake Outage
resolved · Jun 22, 10:14 PM (138d ago)
- Facebook Custom Audiences destination is experiencing partial delivery failures for few workspaces
resolved · Jun 5, 08:11 AM (155d ago)
- Reddit Conversions API destination is experiencing delivery failures
resolved · May 8, 01:59 AM (183d ago)
- Destinations Failing to Load in UI
resolved · Apr 29, 02:49 PM (192d ago)
Segment status — frequently asked
- Is Segment down right now?
- No — Segment is not down. All Segment systems are reported operational. Checked (1s ago).
- What is Segment's status right now?
- Segment is reporting “All Systems Operational” on its official status page — Operational — as of . That status feed answered our last check in 540 ms. isuptime reads this from Segment's own published feed and does not test Segment independently.
- When did Segment last go down?
- The most recent incident Segment published was “Intermittent failures scheduling warehouse jobs and processing Profile Syncs”, opened Nov 7, 12:46 AM UTC (21h ago) and marked resolved Nov 7, 03:01 AM UTC. That is the latest entry in Segment's own incident feed, not every problem users experienced.
- What is Segment's uptime?
- isuptime does not measure Segment's uptime directly — it reads Segment's own published status feed. Over the last 30 days, Segment's own status feed reported no outage in 100.00% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
- Is it just me, or is Segment down for everyone?
- Segment reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.
Segment says operational but it is not working for me
Data missing from one destination while others are fine is normally that destination's mapping, filters or credentials. Use the source debugger to confirm events are arriving at Segment at all before looking downstream. Ad blockers block analytics.js in the browser, so client-side events from real users can silently never be sent.