About status.buzz

You know the moment. The video stops loading, the message will not send, the page just spins. And before you can be annoyed at anyone, you have to answer one stupid question first: is it broken, or is it just me?

So you start the ritual. Reload the page. Toggle airplane mode. Restart the app. Unplug the router and count to ten like your parents taught you. Ask someone in the next room if their phone works. Five minutes later you still have no idea whether you have wasted your time or found a real problem, and the only thing you have actually achieved is losing your place.

That question has a real answer, and it is usually knowable in seconds. The information exists: the company often publishes a status feed, the servers either respond or they do not, and thousands of other people are hitting the same wall at the same moment. It is just scattered across places nobody thinks to look while they are frustrated.

status.buzz collects that answer in one place. Type a service, get a verdict. That is the whole idea.

How we actually check

Guessing is easy and useless, so every verdict says how it was reached. Each of the 27 services we track is re-checked around the clock through four levels, stepping down only when a level cannot give a clear answer:

1. Official status feed. If the company publishes a machine-readable status page, we read it first. Nothing beats the provider's own word.
2. Direct probe. No feed, or the feed is quiet? We ask the service's own servers and time the response. A 5xx or a timeout is a real signal.
3. Network ping. Some companies block automated probes. We fall back to a network-level ping to measure packet loss and round-trip time.
4. You. Machines miss things people notice immediately, like logins failing while the homepage loads fine. When reports pass our alert threshold, we flag likely problems even when every probe still looks healthy.

Every service page shows which level produced the current answer, so you are never asked to just trust a coloured dot.

What we are honest about

• We are not affiliated with any service we track. No partnerships, no inside access. Every name and logo belongs to its owner.
• We can be wrong. A service can be broken in your country while working fine from ours, or broken for one feature while the rest runs. Treat everything here as evidence, not proof.
• Reports come only from this site. Every count you see is someone clicking the report button here. We do not scrape or resell anyone else's numbers.
• We keep almost nothing. No accounts and no sign-ups. Traffic is measured with Google Analytics; we build no profiles of our own. Reports and searches are deleted after 24 hours. Comments are the exception: they are hosted by Disqus and stay until they or you remove them. See the privacy policy.

Why the name

A buzz is noise, and an outage is the internet suddenly going quiet. status.buzz exists to make noise when that happens, so you can stop restarting your router and get on with your day.

Get in touch

Want a service added, spotted a wrong verdict, or need to report a problem with the site itself? Email hello@status.buzz.