Customer Specific Status Pages
A few months ago we launched Component Subscriptions as our first step towards getting the right notification to the right end user. Today, we’re taking this concept to the next level with StatusPage.io Multitenancy.
The Right Status Page For The Right User
System status is something that’s hard to get right for larger companies with thousands, if not hundreds of thousands of customers. Operations and support teams have legitimate questions around how to appropriately communicate status. At what severity level should we post an incident? Is everyone affected by this issue or just a subset of users? If it’s only a subset of users, how do we let them know without scaring the rest of our users unaffected by the issue? At what point should we send email and/or sms alerts vs. only displaying information on our status page? The list goes on.
StatusPage.io Multitenancy addresses the majority of these problems by allowing for end user specific status pages and notifications. Customer Support and Ops can sleep happy knowing they aren't scaring users with irrelevant status notifications, while end users receive a cleaner status page UI and pertinent status notifications.
See It In Action
Open multitenancydemo.statuspage.io in three incognito windows and authenticate with email@example.com, firstname.lastname@example.org, and email@example.com. You'll notice that live incidents, scheduled maintenance, components, and incident history are completely dependent on the user.
Feli’s page on the left is showing Partial System Outage since Acme's API is down, while all systems are up for Brennan since he does not use Acme’s API and is therefore not affected by the current outage.
How It Works
Let StatusPage.io know about your users and the relevant infrastructure they live on or the services they use through the API.
End users authenticate when visiting your status page in order to view the current status and subscribe to updates.
Based on end user authentication, we'll show the right system status information for that user.
Component status, live incidents, metrics, and incident histories will be completely dependent on the user.
If you’re interested in getting setup with Multitenancy, give us a shout at firstname.lastname@example.org and we’d love to line up a call to see how we can help out!