- Level
- confirmed
- Worst impact
- Degraded
- Components
- Test Reporting & Analytics - Test Data Ingestion
- Down Index
- 9of 100
What to do
Check whether you use BrowserStack Test Reporting & Analytics - Test Data Ingestion. 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 0m it lasted.
Anything that failed between 2026-06-20 00:22 UTC and 2026-06-20 00:22 UTC may need a replay.Subscribe to BrowserStack's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=browserstack works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from BrowserStack 1
- resolved
Between June 19th 08:30 UTC & June 19th, 21:00 UTC (12.5 hours), our data ingestion pipeline was severely impacted causing delays up to 3-4 hours for tests and builds to appear on product dashboards. Automate, App Automate, Accessibility suite, Central Scanner, Test Management, Low Code Automation & Test Reporting & Analysis products were impacted. There was no data loss w.r.t ingestion during the incident.
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-affc6f48aa
Is BrowserStack still down?
No, this incident was resolved 2026-06-20 00:22 UTC. For BrowserStack's live state, see https://down.guide/browserstack.
How long did it last?
0m, from 2026-06-20 00:22 UTC to 2026-06-20 00:22 UTC, by the times BrowserStack posted.
What was affected?
BrowserStack named Test Reporting & Analytics - Test Data Ingestion.
What caused it?
BrowserStack hasn't published a root cause. If it does, it shows here.
Where does this come from?
BrowserStack's official status page, https://status.browserstack.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.