Damn, is it down?

All services / Entertainment

segment.com · Entertainment

Is Segment down?

Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.

What's broken? (optional)
Is it just me?
No problems detected

Live diagnosis

Is it just me?

Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.

Your browser → segment.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—

Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.

Live outage map

No reports in the last 24 hours.

Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.

User reports

0

Near baseline. 0 in the last hour. Typical hour is about 0.

Our checks

Reaching it

Last check reached it in 1282 ms · 1 min ago.

Reports and checks

Reports compared with the typical volume, with check latency and failures overlaid102007 ms14:1520:1502:1508:0014:00
ReportsTypical baselineCheck latencyFailed checkTimes in UTC
Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
03:1500.01161 ms0
03:3000.01060 ms0
03:4500.01552 ms0
04:0000.01222 ms0
04:1500.01238 ms0
04:3000.02007 ms0
04:4500.0699 ms0
05:0000.0663 ms0
05:1500.01278 ms0
05:3000.01205 ms0
05:4500.0949 ms0
06:0000.0909 ms0
06:1500.01093 ms0
06:3000.01827 ms0
06:4500.01728 ms0
07:0000.0707 ms0
07:1500.01483 ms0
07:3000.01396 ms0
07:4500.0564 ms0
08:0000.01688 ms0
08:1500.0534 ms0
08:3000.01645 ms0
08:4500.01395 ms0
09:0000.0668 ms0
09:1500.01442 ms0
09:3000.01218 ms0
09:4500.0500 ms0
10:0000.01212 ms0
10:1500.01287 ms0
10:3000.0728 ms0
10:4500.0637 ms0
11:0000.01071 ms0
11:1500.0645 ms0
11:3000.0999 ms0
11:4500.0596 ms0
12:0000.0528 ms0
12:1500.0923 ms0
12:3000.01488 ms0
12:4500.0500 ms0
13:0000.0950 ms0
13:1500.0663 ms0
13:3000.01657 ms0
13:4500.01740 ms0
14:0000.01716 ms0

Reliability

Score 100/100 · grade A

100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage

90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.

Segment status badge Embed a live Segment status badge

Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server

Segment status and 30-day uptime badge

Past outages

No outages on record for Segment yet. Outages of 10 minutes or more get their own page here.

All Segment outages · Every recent outage

Having trouble with Segment?

One report per service every 10 minutes from this network. No account.

What's broken? (optional)

Notes are stored for rate-limit context and are not shown publicly.

Runs on: AWS, Twilio

Questions

Is Segment down right now?

Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.

Segment not working for me but the status is fine. What now?

If Segment is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Segment's side.

How does Damn is it down decide Segment's status?

Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.

How often is Segment checked?

About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.