Is BrowserStack down?
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.
Is BrowserStack down for you right now?
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.
What BrowserStack is
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.
What BrowserStack's status feed covers
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.
BrowserStack uptime, last 30 days
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.
- No outage reported (99%+)
- 95–99%
- 80–95%
- Under 80%
- No data
Other services reporting problems right now
10 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.
CloudflarePartial System Outage
- Razorpay1 of 7 services down: Payments API
- ElasticPartial System Outage
GrafanaMinor Service Outage
- PlayStation NetworkPlayStation Store affected in Russia
- SalesforceDegraded Performance: 1 active incident
- ScalewayPartially Degraded Service
- SnowflakePartially Degraded Service
BrowserStack response time trend
Each point is one check of BrowserStack's status endpoint.
BrowserStack outage history
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.
- Low Code Automation - Builds is facing issues
resolved · Oct 13, 02:02 AM (22d ago)
- Low Code Automation - Builds is facing issues
resolved · Oct 12, 02:32 PM (22d ago)
- Accessibility DevTools is facing issues
resolved · Oct 7, 11:00 PM (27d ago)
- Spectra (Accessibility Rule Engine) is facing issues
resolved · Oct 7, 11:00 PM (27d ago)
- Automate is facing issues
resolved · Sep 25, 05:26 AM (40d ago)
- Low Code Automation - Builds is facing issues
resolved · Sep 25, 04:12 AM (40d ago)
- App Live is facing issues
resolved · Sep 22, 09:32 AM (42d ago)
- Live is facing issues
resolved · Sep 22, 09:23 AM (42d ago)
- Live is facing issues
resolved · Sep 17, 03:12 PM (47d ago)
- Observability API - Dashboard marked DOWN!
resolved · Sep 17, 12:54 PM (47d ago)
- Test Reporting & Analytics - Test Runs, Dashboards, Reports is facing issues.
resolved · Sep 17, 12:53 PM (47d ago)
- App Live is facing issues
resolved · Sep 17, 09:00 AM (47d ago)
- Live is facing issues
resolved · Sep 16, 10:18 AM (48d ago)
- App Live is facing issues
resolved · Sep 15, 02:04 PM (49d ago)
- App Live is facing issues
resolved · Sep 9, 02:22 PM (55d ago)
- Low Code Automation - Builds is facing issues
resolved · Sep 8, 11:37 PM (56d ago)
- Observability API - Dashboard marked DOWN!
resolved · Sep 7, 11:32 AM (57d ago)
- Test Reporting & Analytics - Test Runs, Dashboards, Reports is facing issues.
resolved · Sep 7, 11:31 AM (57d ago)
- Observability API - Dashboard marked DOWN!
resolved · Sep 7, 10:06 AM (57d ago)
- Test Reporting & Analytics - Test Runs, Dashboards, Reports is facing issues.
resolved · Sep 7, 10:05 AM (57d ago)
BrowserStack status — frequently asked
- Is BrowserStack down right now?
- No — BrowserStack is not down. All BrowserStack systems are reported operational. Checked (0s ago).
- What is BrowserStack's status right now?
- BrowserStack is reporting “All Systems Operational” on its official status page — Operational — as of . That status feed answered our last check in 140 ms. isuptime reads this from BrowserStack's own published feed and does not test BrowserStack independently.
- When did BrowserStack last go down?
- The most recent incident BrowserStack published was “Low Code Automation - Builds is facing issues”, opened Oct 13, 02:02 AM UTC (22d ago) and marked resolved Oct 13, 02:03 AM UTC. That is the latest entry in BrowserStack's own incident feed, not every problem users experienced.
- What is BrowserStack's uptime?
- isuptime does not measure BrowserStack's uptime directly — it reads BrowserStack's own published status feed. Over the last 30 days, BrowserStack's own status feed reported no outage in 100.00% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
- Is it just me, or is BrowserStack down for everyone?
- BrowserStack reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.
BrowserStack says operational but it is not working for me
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.