User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 11 min ago. Last stored result reached it in 292 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 345 ms | 0 |
| Tue 00 | 0 | 0.0 | 244 ms | 0 |
| Tue 02 | 0 | 0.0 | 1345 ms | 0 |
| Tue 04 | 0 | 0.0 | 247 ms | 0 |
| Tue 06 | 0 | 0.0 | 258 ms | 0 |
| Tue 08 | 0 | 0.0 | 271 ms | 0 |
| Tue 10 | 0 | 0.0 | 308 ms | 0 |
| Tue 12 | 0 | 0.0 | 273 ms | 0 |
| Tue 14 | 0 | 0.0 | 256 ms | 0 |
| Tue 17 | 0 | 0.0 | 309 ms | 0 |
| Tue 19 | 0 | 0.0 | 789 ms | 0 |
| Tue 21 | 0 | 0.0 | 532 ms | 0 |
| Tue 23 | 0 | 0.0 | 251 ms | 0 |
| Wed 02 | 0 | 0.0 | 273 ms | 0 |
| Wed 04 | 0 | 0.0 | 327 ms | 0 |
| Wed 06 | 0 | 0.0 | 289 ms | 0 |
| Wed 08 | 0 | 0.0 | 245 ms | 0 |
| Wed 11 | 0 | 0.0 | 282 ms | 0 |
| Wed 13 | 0 | 0.0 | 223 ms | 0 |
| Wed 15 | 0 | 0.0 | 251 ms | 0 |
| Wed 17 | 0 | 0.0 | 309 ms | 0 |
| Wed 19 | 0 | 0.0 | 208 ms | 0 |
| Wed 21 | 0 | 0.0 | 235 ms | 0 |
| Thu 00 | 0 | 0.0 | 1950 ms | 0 |
| Thu 02 | 0 | 0.0 | 329 ms | 0 |
| Thu 04 | 0 | 0.0 | 1252 ms | 0 |
| Thu 06 | 0 | 0.0 | 251 ms | 0 |
| Thu 08 | 0 | 0.0 | 256 ms | 0 |
| Thu 10 | 0 | 0.0 | 269 ms | 0 |
| Thu 12 | 0 | 0.0 | 277 ms | 0 |
| Thu 14 | 0 | 0.0 | 285 ms | 0 |
| Thu 16 | 0 | 0.0 | 323 ms | 0 |
| Thu 18 | 0 | 0.0 | 287 ms | 0 |
| Thu 20 | 0 | 0.0 | 243 ms | 0 |
| Thu 22 | 0 | 0.0 | 241 ms | 0 |
| Fri 00 | 0 | 0.0 | 275 ms | 0 |
| Fri 02 | 0 | 0.0 | 244 ms | 0 |
| Fri 05 | 0 | 0.0 | 221 ms | 0 |
| Fri 07 | 0 | 0.0 | 277 ms | 0 |
| Fri 09 | 0 | 0.0 | 284 ms | 0 |
| Fri 10 | 0 | 0.0 | 233 ms | 0 |
| Fri 12 | 0 | 0.0 | 258 ms | 0 |
| Fri 14 | 0 | 0.0 | 433 ms | 0 |
| Fri 16 | 0 | 0.0 | 305 ms | 0 |
| Fri 18 | 0 | 0.0 | 243 ms | 0 |
| Fri 20 | 0 | 0.0 | 286 ms | 0 |
| Fri 22 | 0 | 0.0 | 292 ms | 0 |
| Fri 23 | 0 | 0.0 | 286 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Breww 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 Breww goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Breww alerts to Slack, Discord or a webhook — free.
Breww is listed in our Productivity category and checked at breww.com. Breww is modern brewery management software designed specifically for craft breweries. Manage production, sales, deliveries, and more.
Breww publishes an official status page at status.breww.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with productivity services: files not syncing, editors not loading, and sign-in problems.
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: 278 ms average, 214–433 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Breww incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
278 ms on average over the last 24 hours (214–433 ms).
Yes, at https://status.breww.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Breww here at once, the problem is on Breww'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 Breww. 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.