Loading status…
BrowserStack status · Developer Tools · checked (0s ago)
Also searched as BrowserStack Automate, BrowserStack App Automate, BrowserStack Live.
No — BrowserStack is not down. All BrowserStack systems are reported operational.
According to BrowserStack's official status page, BrowserStack was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, BrowserStack's feed reported no outage in 100.00% of our checks.
Everything above is read from BrowserStack's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported BrowserStack in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
BrowserStack runs real browsers and real mobile devices in the cloud for testing — interactive sessions, automated Selenium, Cypress and Playwright grids, and app testing on physical handsets. Test suites in CI are the heaviest users, so an incident usually appears as a pipeline that stalls rather than a page that fails.
The status page separates Live and App Live from the Automate grids and from the dashboard, which is the split that matters — the automation grid can be queueing badly while interactive sessions start fine. Device availability for specific models is not something the page reports, and it is a common source of failures that look systemic.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where BrowserStack's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days BrowserStack was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 0s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of BrowserStack's status endpoint.
BrowserStack has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what BrowserStack posted itself — not every problem users hit.
resolved · Sep 17, 03:12 PM (2d ago)
resolved · Sep 17, 12:54 PM (2d ago)
resolved · Sep 17, 12:53 PM (2d ago)
resolved · Sep 17, 09:00 AM (2d ago)
resolved · Sep 16, 10:18 AM (3d ago)
resolved · Sep 15, 02:04 PM (4d ago)
resolved · Sep 9, 02:22 PM (10d ago)
resolved · Sep 8, 11:37 PM (11d ago)
resolved · Sep 7, 11:32 AM (12d ago)
resolved · Sep 7, 11:31 AM (12d ago)
resolved · Sep 7, 10:06 AM (12d ago)
resolved · Sep 7, 10:05 AM (12d ago)
resolved · Sep 7, 10:03 AM (12d ago)
resolved · Sep 7, 10:02 AM (12d ago)
resolved · Sep 7, 06:00 AM (13d ago)
resolved · Sep 2, 09:23 AM (17d ago)
resolved · Sep 1, 01:31 PM (18d ago)
resolved · Aug 31, 11:07 AM (19d ago)
resolved · Aug 31, 11:07 AM (19d ago)
resolved · Aug 27, 03:13 PM (23d ago)
Tests waiting rather than failing are almost always parallel-session limits on your plan, not an incident: BrowserStack queues instead of rejecting. A session that starts and then dies is more often your test's timeout or a local tunnel dropping than the grid. If only one browser version misbehaves, that is the browser, and BrowserStack does not post per-version notices.
