User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
browser-use.com · Cloud & developer
Is Browser Use down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → browser-use.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 56 min ago. Last stored result reached it in 174 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 223 ms | 0 |
| Mon 16 | 0 | 0.0 | 221 ms | 0 |
| Mon 18 | 0 | 0.0 | 146 ms | 0 |
| Mon 20 | 0 | 0.0 | 343 ms | 0 |
| Mon 22 | 0 | 0.0 | 181 ms | 0 |
| Tue 01 | 0 | 0.0 | 81 ms | 0 |
| Tue 03 | 0 | 0.0 | 59 ms | 0 |
| Tue 05 | 0 | 0.0 | 63 ms | 0 |
| Tue 07 | 0 | 0.0 | 199 ms | 0 |
| Tue 09 | 0 | 0.0 | 107 ms | 0 |
| Tue 11 | 0 | 0.0 | 81 ms | 0 |
| Tue 13 | 0 | 0.0 | 206 ms | 0 |
| Tue 16 | 0 | 0.0 | 437 ms | 0 |
| Tue 18 | 0 | 0.0 | 113 ms | 0 |
| Tue 20 | 0 | 0.0 | 71 ms | 0 |
| Tue 22 | 0 | 0.0 | 117 ms | 0 |
| Wed 00 | 0 | 0.0 | 88 ms | 0 |
| Wed 03 | 0 | 0.0 | 72 ms | 0 |
| Wed 05 | 0 | 0.0 | 226 ms | 0 |
| Wed 07 | 0 | 0.0 | 106 ms | 0 |
| Wed 09 | 0 | 0.0 | 169 ms | 0 |
| Wed 12 | 0 | 0.0 | 269 ms | 0 |
| Wed 14 | 0 | 0.0 | 218 ms | 0 |
| Wed 16 | 0 | 0.0 | 174 ms | 0 |
| Wed 18 | 0 | 0.0 | 87 ms | 0 |
| Wed 20 | 0 | 0.0 | 219 ms | 0 |
| Wed 22 | 0 | 0.0 | 108 ms | 0 |
| Thu 01 | 0 | 0.0 | 103 ms | 0 |
| Thu 03 | 0 | 0.0 | 83 ms | 0 |
| Thu 05 | 0 | 0.0 | 83 ms | 0 |
| Thu 07 | 0 | 0.0 | 117 ms | 0 |
| Thu 09 | 0 | 0.0 | 372 ms | 0 |
| Thu 11 | 0 | 0.0 | 180 ms | 0 |
| Thu 13 | 0 | 0.0 | 228 ms | 0 |
| Thu 15 | 0 | 0.0 | 232 ms | 0 |
| Thu 17 | 0 | 0.0 | 174 ms | 0 |
| Thu 19 | 0 | 0.0 | 96 ms | 0 |
| Thu 21 | 0 | 0.0 | 240 ms | 0 |
| Thu 23 | 0 | 0.0 | 90 ms | 0 |
| Fri 01 | 0 | 0.0 | 148 ms | 0 |
| Fri 03 | 0 | 0.0 | 138 ms | 0 |
| Fri 05 | 0 | 0.0 | 335 ms | 0 |
| Fri 07 | 0 | 0.0 | 85 ms | 0 |
| Fri 09 | 0 | 0.0 | 88 ms | 0 |
| Fri 11 | 0 | 0.0 | 68 ms | 0 |
| Fri 12 | 0 | 0.0 | 77 ms | 0 |
| Fri 14 | 0 | 0.0 | 112 ms | 0 |
| Fri 16 | 0 | 0.0 | 174 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Browser Use badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Browser Use yet. Outages of 10 minutes or more get their own page here.
Having trouble with Browser Use?
One report per service every 10 minutes from this network. No account.
Follow Browser Use
Get an email when Browser Use goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Browser Use alerts to Slack, Discord or a webhook — free.
About Browser Use
Browser Use is listed in our Cloud & developer category and checked at browser-use.com. Browser agents and cloud browsers: the most-starred open-source browser agent, stealth cloud browsers at $0.02/browser-hour and Browser Harness. SOC 2 Type II, on-prem, US and EU. $1 free.
Browser Use publishes an official status page at status.browser-use.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 140 ms average, 54–335 ms range across 14 successful checks.
Questions
Is Browser Use down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Browser Use last down?
We have not recorded a public Browser Use incident since monitoring began 8 days ago.
What is Browser Use's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Browser Use respond?
140 ms on average over the last 24 hours (54–335 ms).
Does Browser Use have an official status page?
Yes, at https://status.browser-use.com.
Browser Use not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Browser Use here at once, the problem is on Browser Use's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Browser Use. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.