Segment: Analytics.js Google Tag Manager issue

What to do

Check whether you use Segment Analytics.js CDN (US), Analytics.js CDN (EU) in eu, us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 9h 14m it lasted.
Anything that failed between 2026-02-06 21:58 UTC and 2026-02-07 07:12 UTC may need a replay.
Subscribe to Segment's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=segment works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

identifiedFeb 6, 2026, 9:58 PM UTC
We have identified an issue where Google Tag Manager doesn't initialize correctly from the latest version of Analytics.js. We've identified the cause and have deployed a fix, which will deploy across the CDN over the next few hours.
provider
monitoringFeb 7, 2026, 12:30 AM UTC
We have reverted the change and confirmed that submitting events to Google Tag Manager is working as expected. We will continue to monitor closely.
provider
resolvedFeb 7, 2026, 7:12 AM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Segment still down?

No, this incident was resolved 2026-02-07 07:12 UTC. For Segment's live state, see https://down.guide/segment.

How long did it last?

9h 14m, from 2026-02-06 21:58 UTC to 2026-02-07 07:12 UTC, by the times Segment posted.

What was affected?

Segment named Analytics.js CDN (US), Analytics.js CDN (EU) in eu, us.

What caused it?

Segment hasn't published a root cause. If it does, it shows here.

Where does this come from?

Segment's official status page, https://status.segment.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.