Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
Our final Monday update of July and although many of our customers are heading off on summer vacation not only are we here monitoring your websites 24/7, but we’ve got some exciting new features and improvements happening over the holiday break.
StatusCake Customer Survey – July 2018
We sent out our customer survey at the tail end of last week. If you’ve not seen the email in your in-box you can complete the survey here. The customer survey is incredibly important to us as it enables us to understand how we are doing in key areas of the service, for instance in terms of our customer support and the product itself, but it’s also your opportunity to tell us how you think we can make improvements, and what direction we should take the product in.
Please do reply. The feedback we’ve already had is invaluable – the good, the bad, and the ugly – and we do reply to every single survey response so don’t forget to leave your username or email address so that we can respond to you. It also means that you’ll be entered into our prize draw to win one of two Amazon gift cards.
The survey will be closed at midnight on Friday 10th August so there’s still plenty of time to have your say. We will be sharing all the results of the customer survey with you by the end of August, as well as setting out how we plan to implement some of the features and changes that have been driven by your feedback.
Atlassian & Slack Form Alliance, HipChat & Stride To Go & New StatusCake Integration With Telegram
Last week saw a big announcement that Atlassian was selling two of its products HipChat and Stride to messaging behemoth Slack, as well as entering into a key strategic alliance with Slack and investing in the company.
Many will know Atlassian for its popular tools such as Jira, and Bitbucket as well as products such as Trello and StatusPage.io; the latter of which StatusCake has recently sought to challenge with its StatusPage.io alternative – StatusCake Pages. Many of our existing customers have already made the transition from StatusPage.io as our very own StatusCake Pages not only integrates seamlessly with your StatusCake account but offers better value for money.
Although HipChat and Stride will be shut down by Atlassian there are many other integrations that our customers can use, including of course Slack itself and Microsoft teams. We will also continue to look at new integrations, including Telegram that will be rolled out to our customers later this week.
Chrome Browser Extension
We’ve made some improvements to our StatusCake Alerts Chrome browser extension. The Chrome extension is a great way of getting alerts on your uptime tests directly to your browser. We’d love your feedback and thoughts on how to make this even more useful. To add the extension to your browser just visit this page in the Chrome store.
Google Chrome SSL changes
The popular Chrome browser from Google has in a recent update begun to mark all sites accessed via HTTP:// and not HTTPS:// as insecure.
This means that for any sites only serving over http exclusively, or missing a redirect to the https – users will be strongly dissuaded from browsing the site and entering personal information.
If you want to check your StatusCake account right now for any offending URLs just follow the easy 2 step process below:
1 – First off use the filters in the main app dashboard to search for any URL’s that match “http://”
2 – Once that’s done simply scroll down the Status Codes for the tests, you are looking for any status code which does not begin with a 3, any that fit this criteria are likely to not have a redirect implemented, and should be checked out.
In response to these coming changes we recently implemented SSL access for both our Public Reporting and StatusCake Pages, so you won’t have to worry about users receiving any warnings when accessing these reports.
StatusCake Team
Share this
More from StatusCake
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026