are we down yet?

Is it your code, or theirs?

As we reimagine on-call at the early stages, we’ve talked to hundreds of engineers who are building modern applications to learn about what context they need during production incidents. What are the signals they want to know when they get beeped at 3am?

Amidst the chaos of different tools folks will typically reach for, one common pattern emerged: instead of thinking about issues with their servers, they were more concerned with flagging problems with service providers they use.

Almost every day, you’ll see a tweet (or an x-post? who knows anymore) like the one from Hassan below:

How would he quickly know that Neon could be having production issues in the region where his serverless postgres resides? Could he — or anyone on his team — quickly recognize the difference between something breaking in his application code or Clerk being down?

We’ve built some novel ways of collecting and exposing this data as a core feature in the complete beeps on-call platform. It truly saves engineers time when things go awry. We’d love to hear from you if you want to check it out.

But since we like to have a little bit of fun, we thought we’d share it with y’all the only way we know how: by tapping into some community banter.

Introducing arewedownyet?

Last year, we were hanging out at Next.js conf when areweturboyet.com was announced. We immediately bought the arewedownyet.com domain and jotted down some quick ideas of what to build on it (on a side note: can we be turbo already?)

arewedownyet? takes the most frequently-posted tech stack providers that engineers are using in their modern applications and shows a global leaderboard for their most recent (24hr) uptime. It’s real-time and pretty darn accurate. You can then click through to the provider’s status page and read their updates to get more information.

Bookmark it, love it, and let us know if we’re missing any providers you’d like to see at @beepshq on x (or twitter).