Metric Alerts Firing Incorrectly

What to do

• Check whether you use FullStory Webhooks & Alerts, Webhooks & Alerts 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 3h 17m it lasted.

  Anything that failed between 2026-06-11 13:28 UTC and 2026-06-11 16:45 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. investigatingJun 11, 2026, 1:28 PM UTC

   We are investigating an issue where Metric Alerts are triggering at thresholds that do not match the underlying metric data for customers in both our EU and NA data centers. Customers may be receiving alert notifications that appear to fire incorrectly or more frequently than expected. Our engineering team has been notified and is actively investigating. We will provide an update as soon as we have more information. We apologize for the disruption and appreciate your patience.

   provider

2. resolvedJun 11, 2026, 4:45 PM UTC

   As of 9:36 AM ET on June 11, 2026, this issue is resolved. A feature flag introduced as part of our multi-metric support rollout caused alert evaluations to diverge from actual metric values, resulting in Metric Alerts firing incorrectly even when the underlying metric had not breached its threshold. Start time of this issue: Multi-Metric Beta customers: June 4, 2026 at 10:27 AM ET All other customers using Metrics with division: June 10, 2026 at 4:25 PM ET If you continue to receive alerts you believe are incorrect, please reach out to us at support@fullstory.com. We apologize for the disruption.

   provider

Corrections

None so far.

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