Skip to main content

Is BrowserStack Down?

No — BrowserStack is up

Reachable from all 8 checked regions

Average response time: 49ms

Last checked · checks run every 6 hours

Official status page: https://status.browserstack.com

BrowserStack uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
91ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 11 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

11-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: 100.00% uptime, 16 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 40 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 51 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 31 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ewr
19ms
DNS 0ms TCP 1ms TLS 4ms TTFB 9ms
fra
18ms
DNS 0ms TCP 1ms TLS 3ms TTFB 9ms
gru
33ms
DNS 0ms TCP 3ms TLS 6ms TTFB 16ms
iad
75ms
DNS 1ms TCP 8ms TLS 12ms TTFB 42ms
jnb
175ms
DNS 0ms TCP 24ms TLS 27ms TTFB 78ms
lax
28ms
DNS 1ms TCP 2ms TLS 6ms TTFB 17ms
lhr
27ms
DNS 0ms TCP 2ms TLS 4ms TTFB 12ms
nrt
16ms
DNS 0ms TCP 1ms TLS 3ms TTFB 9ms
ord
23ms
DNS 0ms TCP 1ms TLS 4ms TTFB 11ms

What BrowserStack does

BrowserStack runs real browsers and mobile devices in the cloud for testing, both interactively and from automated suites. Teams point Selenium, Cypress, Playwright and Appium runs at it so tests execute against real Safari, Chrome and physical handsets rather than emulators. Because CI pipelines call it on every commit, an outage blocks merges rather than only manual testing.

What an outage looks like

Automated test sessions fail to start, time out waiting for a device, or disconnect part-way, so CI jobs go red for reasons unrelated to the code under test. Live and App Live sessions will not launch or freeze on a blank device screen. The dashboard will not load and reports from completed runs are missing. Percy visual comparisons stop returning results.

What to do about it

Check status.browserstack.com, which reports Live, Automate, App Live, App Automate, Percy, Test Management and Authentication as separate components across roughly thirty entries. Authentication failing looks like a credentials problem in CI, so read that row before rotating keys. Avoid re-running whole pipelines repeatedly during an incident, since queued sessions compete for the same parallel slots.

Is it down for everyone, or just you?

If this page says BrowserStack is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

GitHub
GitHub
GitLab
GitLab
Docker Hub
Docker Hub
Postman
Postman

BrowserStack outage FAQ

My CI went red. Is it BrowserStack or my tests?
A BrowserStack incident usually fails at session creation or disconnects mid-run, rather than producing consistent assertion failures. If every test fails identically at startup, suspect the platform; if specific assertions fail while sessions start normally, suspect the code. Check status.browserstack.com for Automate and Authentication, which are the two components that produce CI-wide failures.
Is it an outage or am I out of parallel sessions?
Running out of parallels queues sessions rather than failing them, so tests appear slow instead of broken. An outage more often refuses the session outright. Your parallel usage is visible in the dashboard, though during an incident the dashboard itself may be the affected component. Check the status page first to tell the two apart.
Will my test results and recordings be lost?
Runs that completed before the incident are stored on BrowserStack, and Test Reporting is listed as its own component, so results can be temporarily unviewable without being gone. Sessions interrupted mid-run are the ones that genuinely produce no usable result. Re-run those once the platform is operational rather than treating the failure as a real regression.
Should CI retry automatically when BrowserStack fails?
Retry session creation a small number of times with backoff, but distinguish infrastructure failures from test failures in your reporting. A pipeline that silently retries everything hides real regressions, and one that treats a platform outage as a code failure blocks merges for no reason. Tagging the two differently is what makes the distinction visible later.
Does a BrowserStack outage affect local testing?
No. Tests running against browsers on your own machine are unaffected. What breaks is anything pointed at BrowserStack's grid, including BrowserStack Local tunnels used to reach private environments. During an incident, running a reduced suite locally is usually the fastest way to keep merging, accepting narrower browser coverage until the platform returns.

How we measure this

  • We request BrowserStack's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where BrowserStack publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when BrowserStack goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required