Is Segment down?

Last checked 10m ago
Current status
Segment is having a partial outage

Active incident: Destinations Failing to Load in UI

Get alerts when Segment breaks →

Free · no credit card

Official status page: https://status.segment.com · Polled every 5 minutes · 34 components tracked

Real-time Segment status, recent outages, and incident history — pulled directly from Segment's official status page at https://status.segment.com every 5 minutes. Pingoru tracks 34 Segment services and has captured 33 incidents in the last 90 days (98.63% uptime). Get email, Slack, Discord, or webhook alerts the moment Segment reports a new incident — free for 5 monitors, no credit card.

Users who monitor Segment also follow these Analytics services: New Relic Grafana Fivetran Amplitude Mixpanel Hudl Qualtrics Hotjar Branch FullStory View all 6,000+ providers
Segment uptime 98.63% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Audience Preview Failures
    Resolved —
    Started Apr 29, 2026, 05:14 PM UTC · Resolved Apr 27, 2026, 05:00 PM UTC
    1 update · show timeline
    • resolved · Apr 29, 2026, 05:14 PM UTC

      Summary: From 10:20 AM to 3:00 PM PDT on April 27th, a global Databricks Compute outage resulted in failed audience preview queries across external workspaces. Details: The disruption was caused by an upstream infrastructure failure at Databricks, which prevented some preview queries from executing successfully. This issue was localized to the dashboard preview tool; real-time event delivery and audience activations were not impacted. Resolution: The underlying compute issue has been resolved by the vendor. We have confirmed that preview functionality is fully restored and operating normally.

    Latest: Summary: From 10:20 AM to 3:00 PM PDT on April 27th, a global Databricks Compute outage resulted in failed audience preview queries across external workspaces. Details: The disrupt…

  2. Destinations Failing to Load in UI
    Ongoing ● 2h 44m
    Started Apr 29, 2026, 03:53 PM UTC
    Web Interface (EU)
    3 updates · show timeline
    • investigating · Apr 29, 2026, 02:49 PM UTC

      We are currently investigating an issue affecting the Destinations page in the Segment application UI. For some customers, the Destinations are failing to load.

    • identified · Apr 29, 2026, 03:53 PM UTC

      We’ve identified the root cause and are currently implementing a fix. The issue is isolated to a subset of workspaces with connected RETL destinations.

    • monitoring · Apr 29, 2026, 04:58 PM UTC

      The issue is now mitigated. We’ve deployed a fix, and the Destinations page is loading as expected for all workspaces that were previously impacted. We are monitoring the results.

    Latest: The issue is now mitigated. We’ve deployed a fix, and the Destinations page is loading as expected for all workspaces that were previously impacted. We are monitoring the results.

  3. Unable to add Activation to Event Triggered Journey
    Resolved —
    Started Apr 27, 2026, 10:33 PM UTC · Resolved Apr 27, 2026, 10:00 PM UTC
    1 update · show timeline
    • resolved · Apr 27, 2026, 10:33 PM UTC

      An issue impacting the Event Triggered Journey user interface in the application has been resolved. Prior to resolution, customers may have experienced an error in the user interface impacting their ability to configure Activations for Event Triggered Journeys.

    Latest: An issue impacting the Event Triggered Journey user interface in the application has been resolved. Prior to resolution, customers may have experienced an error in the user interfa…

  4. 🛑 api.tresl.co is down
    Resolved 25m
    Started Apr 23, 2026, 05:42 PM UTC · Resolved Apr 23, 2026, 06:08 PM UTC
    Segments Analyticsapi-tresl-co
    1 update · show timeline
    • resolved · Apr 23, 2026, 05:42 PM UTC

      In [`502fd57`](https://github.com/tresl-co/uptime/commit/502fd57b5850107540a994ac0589422cd91b2c1a ), api.tresl.co (https://api.tresl.co/health) was **down**: - HTTP code: 0 - Response time: 0 ms

    Latest: In [`502fd57`](https://github.com/tresl-co/uptime/commit/502fd57b5850107540a994ac0589422cd91b2c1a ), api.tresl.co (https://api.tresl.co/health) was **down**: - HTTP code: 0 - Respo…

  5. 🛑 api.tresl.co is down
    Resolved 27m
    Started Apr 23, 2026, 04:37 PM UTC · Resolved Apr 23, 2026, 05:04 PM UTC
    Segments Analyticsapi-tresl-co
    1 update · show timeline
    • resolved · Apr 23, 2026, 04:37 PM UTC

      In [`3874fc1`](https://github.com/tresl-co/uptime/commit/3874fc1e4e1b289645b7a7c75c9babba4a18bee2 ), api.tresl.co (https://api.tresl.co/health) was **down**: - HTTP code: 0 - Response time: 0 ms

    Latest: In [`3874fc1`](https://github.com/tresl-co/uptime/commit/3874fc1e4e1b289645b7a7c75c9babba4a18bee2 ), api.tresl.co (https://api.tresl.co/health) was **down**: - HTTP code: 0 - Respo…

See the full Segment outage history

27 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 15 incidents
  • Audience Preview Failures Resolved
    Started Apr 29, 2026, 05:14 PM UTC · Resolved Apr 27, 2026, 05:00 PM UTC · —
  • Destinations Failing to Load in UI Ongoing
    Started Apr 29, 2026, 03:53 PM UTC · ● 2h 44m
  • Unable to add Activation to Event Triggered Journey Resolved
    Started Apr 27, 2026, 10:33 PM UTC · Resolved Apr 27, 2026, 10:00 PM UTC · —
  • 🛑 api.tresl.co is down Resolved
    Started Apr 23, 2026, 05:42 PM UTC · Resolved Apr 23, 2026, 06:08 PM UTC · 25m
  • 🛑 api.tresl.co is down Resolved
    Started Apr 23, 2026, 04:37 PM UTC · Resolved Apr 23, 2026, 05:04 PM UTC · 27m
  • 🛑 api.tresl.co is down Resolved
    Started Apr 20, 2026, 05:10 PM UTC · Resolved Apr 20, 2026, 05:35 PM UTC · 24m
  • Major Outage detected on status page Resolved
    Started Apr 19, 2026, 09:16 PM UTC · Resolved Apr 19, 2026, 09:50 PM UTC · 33m
  • Audience Preview Unavailable Resolved
    Started Apr 13, 2026, 07:19 PM UTC · Resolved Apr 13, 2026, 07:19 PM UTC · —

See Segment in your Pingoru dashboard

Monitor Segment alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Segment to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Segment incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Segment or see every provider at once.

Maintenance calendar

Scheduled Segment maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Segment status change, one inbox

Pingoru watches Segment's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Segment reports on 34 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Segment alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Segment maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Segment services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Segment from the same account, with per-user notification preferences for any monitor.

Get notified on Segment status changes

Pingoru watches Segment's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Segment free

Monitor Segment along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Segment and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Segment uptime & incident history

See 90 days of Segment uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Segment uptime history

Frequently asked questions

What is Segment's uptime?
Over the last 90 days, Segment reported 98.63% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.segment.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Segment's uptime history rolling forward in real time.
Has Segment had outages in 2026?
Yes — Segment has had 32 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Segment outage?
The most recent Segment incident was "Audience Preview Failures", which started on April 29, 2026 and was resolved on April 27, 2026. Pingoru captured this directly from https://status.segment.com. See the full incident card above for affected components and the update timeline.
How often does Segment have outages?
Based on the last 90 days, Segment averages 10.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Segment's status page?
Segment's official status page is https://status.segment.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Segment down right now?
Segment is having a partial outage. Pingoru checks the official status page every 5 minutes and flips this headline the moment Segment reports a change. Current status is based on 34 tracked services.
How does Pingoru know if Segment is down?
We read https://status.segment.com directly, using Segment's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Segment has an outage?
Create a free Pingoru account and add Segment as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Segment's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Segment incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Segment issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Segment status?
We use Segment's own status page at https://status.segment.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Partial Outage" mean?
Segment has a partial outage — one or more components are down, but the rest of the service is operational.

Stop finding out from your users.

We watch Segment's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Segment free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →