User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
workbrew.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 47 min ago. Last stored result reached it in 209 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 1102 ms | 0 |
| Mon 15 | 0 | 0.0 | 707 ms | 0 |
| Mon 17 | 0 | 0.0 | 195 ms | 0 |
| Mon 19 | 0 | 0.0 | 343 ms | 0 |
| Mon 22 | 0 | 0.0 | 795 ms | 0 |
| Tue 00 | 0 | 0.0 | 203 ms | 0 |
| Tue 02 | 0 | 0.0 | 204 ms | 0 |
| Tue 04 | 0 | 0.0 | 354 ms | 0 |
| Tue 06 | 0 | 0.0 | 502 ms | 0 |
| Tue 08 | 0 | 0.0 | 225 ms | 0 |
| Tue 10 | 0 | 0.0 | 958 ms | 0 |
| Tue 12 | 0 | 0.0 | 332 ms | 0 |
| Tue 15 | 0 | 0.0 | 252 ms | 0 |
| Tue 17 | 0 | 0.0 | 216 ms | 0 |
| Tue 19 | 0 | 0.0 | 224 ms | 0 |
| Tue 21 | 0 | 0.0 | 198 ms | 0 |
| Wed 00 | 0 | 0.0 | 395 ms | 0 |
| Wed 02 | 0 | 0.0 | 1860 ms | 0 |
| Wed 04 | 0 | 0.0 | 215 ms | 0 |
| Wed 06 | 0 | 0.0 | 444 ms | 0 |
| Wed 09 | 0 | 0.0 | 308 ms | 0 |
| Wed 11 | 0 | 0.0 | 199 ms | 0 |
| Wed 13 | 0 | 0.0 | 250 ms | 0 |
| Wed 15 | 0 | 0.0 | 218 ms | 0 |
| Wed 17 | 0 | 0.0 | 211 ms | 0 |
| Wed 20 | 0 | 0.0 | 234 ms | 0 |
| Wed 22 | 0 | 0.0 | 354 ms | 0 |
| Thu 00 | 0 | 0.0 | 493 ms | 0 |
| Thu 02 | 0 | 0.0 | 277 ms | 0 |
| Thu 04 | 0 | 0.0 | 292 ms | 0 |
| Thu 06 | 0 | 0.0 | 395 ms | 0 |
| Thu 08 | 0 | 0.0 | 274 ms | 0 |
| Thu 10 | 0 | 0.0 | 262 ms | 0 |
| Thu 12 | 0 | 0.0 | 370 ms | 0 |
| Thu 15 | 0 | 0.0 | 321 ms | 0 |
| Thu 17 | 0 | 0.0 | 214 ms | 0 |
| Thu 19 | 0 | 0.0 | 684 ms | 0 |
| Thu 21 | 0 | 0.0 | 1248 ms | 0 |
| Thu 23 | 0 | 0.0 | 1119 ms | 0 |
| Fri 01 | 0 | 0.0 | 410 ms | 0 |
| Fri 03 | 0 | 0.0 | 228 ms | 0 |
| Fri 05 | 0 | 0.0 | 314 ms | 0 |
| Fri 07 | 0 | 0.0 | 230 ms | 0 |
| Fri 08 | 0 | 0.0 | 188 ms | 0 |
| Fri 10 | 0 | 0.0 | 186 ms | 0 |
| Fri 11 | 0 | 0.0 | 258 ms | 0 |
| Fri 13 | 0 | 0.0 | 245 ms | 0 |
| Fri 15 | 0 | 0.0 | 209 ms | 0 |
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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Workbrew yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Workbrew goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Workbrew alerts to Slack, Discord or a webhook — free.
Workbrew is listed in our Cloud & developer category and checked at workbrew.com. See every Homebrew package, npm package and VS Code extension on your Macs. Enforce policy and patch vulnerabilities automatically. Built for IT and security.
Workbrew publishes an official status page at status.workbrew.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 409 ms average, 85–1248 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Workbrew incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
409 ms on average over the last 24 hours (85–1248 ms).
Yes, at https://status.workbrew.com.
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 Workbrew here at once, the problem is on Workbrew'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 Workbrew. 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.