User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 1 hr ago. Last stored result reached it in 748 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 922 ms | 0 |
| Mon 17 | 0 | 0.0 | 933 ms | 0 |
| Mon 19 | 0 | 0.0 | 847 ms | 0 |
| Mon 21 | 0 | 0.0 | 877 ms | 0 |
| Tue 00 | 0 | 0.0 | 508 ms | 0 |
| Tue 02 | 0 | 0.0 | 965 ms | 0 |
| Tue 04 | 0 | 0.0 | 944 ms | 0 |
| Tue 06 | 0 | 0.0 | 804 ms | 0 |
| Tue 08 | 0 | 0.0 | 924 ms | 0 |
| Tue 10 | 0 | 0.0 | 904 ms | 0 |
| Tue 12 | 0 | 0.0 | 969 ms | 0 |
| Tue 14 | 0 | 0.0 | 934 ms | 0 |
| Tue 17 | 0 | 0.0 | 1037 ms | 0 |
| Tue 19 | 0 | 0.0 | 942 ms | 0 |
| Tue 21 | 0 | 0.0 | 797 ms | 0 |
| Tue 23 | 0 | 0.0 | 879 ms | 0 |
| Wed 02 | 0 | 0.0 | 514 ms | 0 |
| Wed 04 | 0 | 0.0 | 1027 ms | 0 |
| Wed 06 | 0 | 0.0 | 872 ms | 0 |
| Wed 08 | 0 | 0.0 | 2889 ms | 0 |
| Wed 10 | 0 | 0.0 | 909 ms | 0 |
| Wed 12 | 0 | 0.0 | 877 ms | 0 |
| Wed 14 | 0 | 0.0 | 962 ms | 0 |
| Wed 16 | 0 | 0.0 | 1063 ms | 0 |
| Wed 19 | 0 | 0.0 | 896 ms | 0 |
| Wed 21 | 0 | 0.0 | 930 ms | 0 |
| Wed 23 | 0 | 0.0 | 923 ms | 0 |
| Thu 01 | 0 | 0.0 | 847 ms | 0 |
| Thu 03 | 0 | 0.0 | 967 ms | 0 |
| Thu 05 | 0 | 0.0 | 947 ms | 0 |
| Thu 07 | 0 | 0.0 | 1717 ms | 0 |
| Thu 09 | 0 | 0.0 | 897 ms | 0 |
| Thu 11 | 0 | 0.0 | 1174 ms | 0 |
| Thu 13 | 0 | 0.0 | 904 ms | 0 |
| Thu 15 | 0 | 0.0 | 944 ms | 0 |
| Thu 18 | 0 | 0.0 | 1128 ms | 0 |
| Thu 20 | 0 | 0.0 | 800 ms | 0 |
| Thu 21 | 0 | 0.0 | 968 ms | 0 |
| Thu 23 | 0 | 0.0 | 859 ms | 0 |
| Fri 01 | 0 | 0.0 | 1099 ms | 0 |
| Fri 03 | 0 | 0.0 | 509 ms | 0 |
| Fri 05 | 0 | 0.0 | 735 ms | 0 |
| Fri 07 | 0 | 0.0 | 866 ms | 0 |
| Fri 09 | 0 | 0.0 | 735 ms | 0 |
| Fri 10 | 0 | 0.0 | 919 ms | 0 |
| Fri 11 | 0 | 0.0 | 978 ms | 0 |
| Fri 12 | 0 | 0.0 | 732 ms | 0 |
| Fri 14 | 0 | 0.0 | 748 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Buzz 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 Buzz goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Buzz alerts to Slack, Discord or a webhook — free.
Buzz is listed in our AI category and checked at buzz.ai. Buzz AI Employee runs your outbound across email, LinkedIn and calls: finds leads, writes and sends sequences, and books meetings. Start free.
Buzz publishes an official status page at status.buzz.ai; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 859 ms average, 509–1128 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 Buzz incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
859 ms on average over the last 24 hours (509–1128 ms).
Yes, at https://status.buzz.ai.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Buzz here at once, the problem is on Buzz'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 Buzz. 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.