Skip to main content
FullStory

Google outage degrading some StoryAI features

Degraded Lasted 2h 2m · started · FullStory's page

Level
confirmed
Worst impact
Degraded
Components
StoryAI
Down Index
20of 100

What to do

  • Check whether you use FullStory StoryAI. 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 2h 2m it lasted.

    Anything that failed between 2026-07-16 20:38 UTC and 2026-07-16 22:41 UTC may need a replay.
  • Subscribe to FullStory's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=fullstory works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from FullStory 2

  1. investigating

    The model behind the StoryAI features that are directly embedded within Dashboards, Segments, and Session Replay are seeing degraded availability due to a Google outage. We are working closely with their team to resolve this issue. Other AI features within Fullstory are not impacted at this time.

    provider

  2. resolved

    This incident has been resolved

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-b291411c4d

Is FullStory still down?

No, this incident was resolved 2026-07-16 22:41 UTC. For FullStory's live state, see https://down.guide/fullstory.

How long did it last?

2h 2m, from 2026-07-16 20:38 UTC to 2026-07-16 22:41 UTC, by the times FullStory posted.

What was affected?

FullStory named StoryAI.

What caused it?

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

Where does this come from?

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