Skip to main content
down.guideby Sazabi
Menu
Providers
Is Segment down? · Data and storage

Segment is up

OperationalNo known problems: Segment's status page says operational

99.99% uptime, 90 days · 99.98% over 12 monthsLast incident Checked Official status pageHistory

Reports count in aggregate against normal levels; one alone never makes a claim.

Open incidents

Segment has no open incidents.

90 days

Daily history

Worst impact each day, from the provider's own incidents.

  1. 2026-08-18: 1 incident, worst partial outage
  2. 2026-08-19: no incidents
  3. 2026-08-20: no incidents
  4. 2026-08-21: no incidents
  5. 2026-08-22: no incidents
  6. 2026-08-23: no incidents
  7. 2026-08-24: no incidents
  8. 2026-08-25: no incidents
  9. 2026-08-26: no incidents
  10. 2026-08-27: no incidents
  11. 2026-08-28: no incidents
  12. 2026-08-29: no incidents
  13. 2026-08-30: no incidents
  14. 2026-08-31: no incidents
  15. 2026-09-01: no incidents
  16. 2026-09-02: no incidents
  17. 2026-09-03: 2 incidents, worst partial outage
  18. 2026-09-04: no incidents
  19. 2026-09-05: no incidents
  20. 2026-09-06: no incidents
  21. 2026-09-07: no incidents
  22. 2026-09-08: no incidents
  23. 2026-09-09: no incidents
  24. 2026-09-10: 1 incident, worst partial outage
  25. 2026-09-11: no incidents
  26. 2026-09-12: no incidents
  27. 2026-09-13: no incidents
  28. 2026-09-14: no incidents
  29. 2026-09-15: no incidents
  30. 2026-09-16: 1 incident, worst degraded
  31. 2026-09-17: no incidents
  32. 2026-09-18: no incidents
  33. 2026-09-19: no incidents
  34. 2026-09-20: no incidents
  35. 2026-09-21: no incidents
  36. 2026-09-22: no incidents
  37. 2026-09-23: no incidents
  38. 2026-09-24: no incidents
  39. 2026-09-25: no incidents
  40. 2026-09-26: no incidents
  41. 2026-09-27: no incidents
  42. 2026-09-28: no incidents
  43. 2026-09-29: no incidents
  44. 2026-09-30: no incidents
  45. 2026-10-01: 1 incident, worst degraded
  46. 2026-10-02: no incidents
  47. 2026-10-03: no incidents
  48. 2026-10-04: no incidents
  49. 2026-10-05: no incidents
  50. 2026-10-06: no incidents
  51. 2026-10-07: no incidents
  52. 2026-10-08: no incidents
  53. 2026-10-09: no incidents
  54. 2026-10-10: no incidents
  55. 2026-10-11: no incidents
  56. 2026-10-12: no incidents
  57. 2026-10-13: no incidents
  58. 2026-10-14: no incidents
  59. 2026-10-15: no incidents
  60. 2026-10-16: no incidents
  61. 2026-10-17: no incidents
  62. 2026-10-18: no incidents
  63. 2026-10-19: no incidents
  64. 2026-10-20: no incidents
  65. 2026-10-21: no incidents
  66. 2026-10-22: no incidents
  67. 2026-10-23: no incidents
  68. 2026-10-24: no incidents
  69. 2026-10-25: no incidents
  70. 2026-10-26: 1 incident, worst degraded
  71. 2026-10-27: no incidents
  72. 2026-10-28: no incidents
  73. 2026-10-29: no incidents
  74. 2026-10-30: no incidents
  75. 2026-10-31: no incidents
  76. 2026-11-01: no incidents
  77. 2026-11-02: no incidents
  78. 2026-11-03: no incidents
  79. 2026-11-04: 1 incident, worst degraded
  80. 2026-11-05: no incidents
  81. 2026-11-06: no incidents
  82. 2026-11-07: 1 incident, worst partial outage
  83. 2026-11-08: no incidents
  84. 2026-11-09: no incidents
  85. 2026-11-10: no incidents
  86. 2026-11-11: 1 incident, worst degraded
  87. 2026-11-12: 1 incident, worst degraded
  88. 2026-11-13: no incidents
  89. 2026-11-14: no incidents
  90. 2026-11-15: no incidents
90 days agoToday

Daily history for the 12 components with the most incident days. Every component's current state is in the Markdown copy.

Reliability

Last 90 days in numbers

From the provider's own posts, including history read from its archive.

Uptime
99.98%12 months
Incidents
11on 10 days
Median duration
4h 11m
Longest
21h 38m
Postmortem rate
n/apartial and major outages

People reporting problems

No reports in the last 24 hours.

Follow Segment incidents

Following several providers? Check your stack to get one feed for all of them.

https://down.guide/feed?provider=segment
Open feed

In Slack, install the RSS app and run /feed subscribe https://down.guide/feed?provider=segment in a channel. In Discord, add a feed bot such as MonitoRSS and give it this URL. Or paste it into Feedly or any RSS reader.

https://down.guide/feed?provider=segment&format=atom
Open feed

The same entries as Atom, for readers that prefer it.

https://down.guide/feed?provider=segment&format=json
Open feed

The same entries as JSON Feed 1.1, each with the full incident under _down_guide, for scripts.

https://down.guide/api/v1/incidents?provider=segment
Open feed

Pages of 30 incidents, newest first. Pass the response's next_cursor as cursor for the next page.

History

Recent incidents

The last 90 days.

All history
  1. SegmentMaintenance
    Scheduled Database Maintenance in USW2
    lasted 1h 31mWarehouse Destinations (US), Profiles Syncus
  2. SegmentDegraded
    Google Enhanced Conversions is experiencing sporadic delivery timeouts

    Segment says sporadic delivery timeouts affecting its Google Enhanced Conversions destination have been fully resolved. Timeout rates returned to normal by 17:52 UTC on 2026-11-11, and the provider marked the incident resolved at 03:04 UTC on 2026-11-12.

    lasted 10h 45mData Processing Pipeline (US), Data Processing Pipeline (EU)eu, us
  3. SegmentMaintenance
    Scheduled Database Maintenance in USW2

    Segment says scheduled maintenance on a critical internal service database in USW2 began at 6:30 AM UTC on November 11, 2026, and is in progress. Segment Data Lakes syncs (storage destinations) may be delayed, and the provider says they will resume automatically with no data lost.

    lasted 3h 1mData Lakes (US)us
  4. SegmentPartial outage
    Intermittent failures scheduling warehouse jobs and processing Profile Syncs

    Segment says intermittent failures affected scheduling warehouse jobs and processing Profile Syncs. On 2026-11-07 it reported it was monitoring elevated failures, and at 03:01 UTC it said the incident was resolved.

    lasted 2h 15mWarehouse Destinations (US), Profiles Syncus
  5. SegmentDegraded
    Delays to Realtime Audiences and Journeys
    lasted 2h 8mEngage (US), Journeys (US)us
  6. SegmentDegraded
    Segment event delivery issues
    lasted 16h 20mStreaming Destinations (US), Reverse ETL (EU), Streaming Destinations (EU) +1eu, us
  7. SegmentDegraded
    Audience & Journey data delivery delay in EU region
    lasted 1h 16mEngage (EU), Linked Audiences (EU), Journeys (EU)eu
  8. SegmentDegraded
    Braze Web Event Delivery is experience event delivery issue
    lasted 8h 33mStreaming Destinations (US), Streaming Destinations (EU)eu, us
  9. SegmentDegraded
    Actions S3 is currently experience formatting issues with the delivered events
    lasted 2h 10mStreaming Destinations (US), Engage (US), Streaming Destinations (EU) +4eu, us
  10. SegmentPartial outage
    SSO Login Issues with the Segment App
    lasted 1h 11mWeb Interface (US)us
  11. SegmentPartial outage
    Issue with Engage UI
    lasted 4h 11mWeb Interface (US), Engage (US)us
  12. SegmentDegraded
    Segment App UI Issue with Profile Traits with no recent activity
    lasted 21h 38mWeb Interface (US), Web Interface (EU)eu, us
  13. SegmentPartial outage
    Intermittent Segment application login errors
    lasted 4h 13mWeb Interface (US), Web Interface (EU)eu, us

Segment status: questions

Is Segment down right now?

No known problems: Segment's status page says operational (checked 2026-11-15 13:43 UTC from Segment's official status page).

What is Segment's uptime?

99.99% over the last 90 days and 99.98% over 12 months, from the incidents Segment posted on its own status page. A major outage counts in full and a partial outage as 30% of its time, per component.

When was Segment's last outage?

Google Enhanced Conversions is experiencing sporadic delivery timeouts, starting 2026-11-11 16:19 UTC and lasting 10h 45m: https://down.guide/DWN-4e5c0dd103

How do I get alerts when Segment goes down?

Subscribe to https://down.guide/feed?provider=segment (RSS; add format=atom or format=json). In Slack, install the RSS app and run /feed subscribe with that URL; in Discord, give it to a feed bot such as MonitoRSS. No account needed.

Where does down.guide get Segment's status?

From Segment's official status page, https://status.segment.com, read every minute. Segment's words are quoted verbatim and linked.

Related