Customers can generate hosted status pages that display the status such as availability, response time and incidents of their services (websites, API, infrastructure) to their own clients or for internal use. All status pages are hosted and maintained by our care. Users point a custom domain to our DNS, and after seconds their page is ready. Hassle free.
Embed your status page status anywhere using our API endpoint. Get the list of components and their statuses, uptime and average response time with human descriptions and indicators, and includes a top-level status to programmatically embed it anywhere. Data shows metrics for the past 24 hours. Use the status page URL to retrieve its data.
Before, to know detect a website changed its content or not, you had to manually visit the website and check by yourself. This is a thing from the past! Tools such as Hyperping can send instant alerts in case of changes. One way is making sure your API or marketing site returns the expected content. Some servers return an expected status code (200, OK) but can often return the wrong content in the response body, whether it is HTML content or JSON.
In this post, I would like to expose the mindset that helped me have my very first business profitable since day one. This is not a proven methodology, but I intend to replicate the way I started this business to maybe validate it. Before getting started, here are some metrics to put yourself in the context.
Your users are now able to subscribe to your status page to receive emails every time you publish an update during incidents! This feature, alongside the Incidents one, is only available starting the Pro plan. If you're on the basic plan, let me know in the chat or by email if you want to try out those new features!
Did you ever have your customer success team (if you have the chance to have one!) overwhelmed by customers throught the support chat when facing minor incidents or even major outages, having to update all those worried customers in real time throught dozens of different channels as the engineering team finds out and resolves the issue? Support costs time, energy and money. What if all of your users could all connect to one single status page that would answer all of their questions?
