Skip to main content
Browserbase

Degraded Performance on Stagehand API

Degraded Lasted 1h 11m · started · Browserbase's page

Level
confirmed
Worst impact
Degraded
Down Index
30of 100

What to do

  • Check whether your product depends on Browserbase. 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 1h 11m it lasted.

    Anything that failed between 2026-02-02 20:47 UTC and 2026-02-02 21:58 UTC may need a replay.
  • Subscribe to Browserbase's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=browserbase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Browserbase 6

  1. investigating

    **Problem**: We are experiencing degraded performance on the Stagehand API. **Impact:** Customers are encountering slow performance when accessing the Stagehand API `/replay` endpoint (used by `stagehand.metrics`). **Causes:** We identified that Stagehand session replay metrics retrieval is sporadically overloaded due to high traffic on a few outlier sessions that have thousands of actions logged. **Steps to resolve:** We have temporarily rate-limited these Stagehand API queries, updated the status page, and investigated both infrastructure and query execution, but a few customers are still experiencing degraded on `/act` and `/replay` endpoints.

    provider

  2. monitoring

    It appears the high burst traffic that was overloading session metrics retrieval has been resolved by our new rate limits and query optimizations. We are monitoring the resolution and will continue posting updates.

    provider

  3. resolved

    After monitoring the fix, we can confirm our team has resolved the disruption. We appreciate your patience and understanding with our team today as we worked to address this.

    provider

  4. resolved

    Added incident details regarding replay and metrics endpoint.

    provider

  5. resolved

    Updated timeline details.

    provider

  6. resolved

    More timeline details.

    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-51b6abc797

Is Browserbase still down?

No, this incident was resolved 2026-02-02 21:58 UTC. For Browserbase's live state, see https://down.guide/browserbase.

How long did it last?

1h 11m, from 2026-02-02 20:47 UTC to 2026-02-02 21:58 UTC, by the times Browserbase posted.

What caused it?

Browserbase hasn't published a root cause. If it does, it shows here.

Where does this come from?

Browserbase's official status page, https://status.browserbase.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.