Building Trust with Public Status Pages
Learn how to create transparent, beautiful status pages that build customer confidence. With recent performance improvements for faster historical data, your customers get real-time insights into your service health.
There’s a particular moment of panic that every SaaS company knows. Your monitoring just lit up red, something’s broken, and your support inbox is about to flood with the same question: “Is it down?” You’ve got engineers scrambling to fix the issue, but meanwhile your customers are left in the dark, refreshing their browsers, wondering if anyone even knows there’s a problem.
We built status pages into Loggy because that silence hurts more than the incident itself. Customers don’t mind when things break occasionally—they mind being kept in the dark about it. A public status page is more than a technical tool. It’s a signal to your customers that you take transparency seriously, that you’ll tell them when something’s wrong before they have to ask.
Acme Inc Status
status.acme.com
Degraded Performance
We're experiencing elevated latency on payment processing. Our team is investigating.
Last updated: 10:36 PM
90-Day Uptime History
Recent Incidents
Elevated latency on payment processing
Scheduled Maintenance Completed
What a Status Page Actually Does
At its core, a status page is a simple promise: we’ll tell you how our systems are doing, openly and honestly. But the impact runs deeper than that. When a customer sees a green checkmark next to “API” and knows their integration is working fine, they don’t have to waste time debugging their own code. When you post about an incident before they notice it, you’re showing them that you’re already on it.
The psychology here matters. Customers who check your status page and see honest, timely information are customers who trust you. They’re customers who stick around. Compare that to the alternative: a customer hits an error, assumes it’s on their end, spends an hour debugging, and only then discovers it was your problem all along. That’s the kind of experience that makes people look for alternatives.
Setting Up Your First Status Page
Creating a status page in Loggy takes about five minutes, but there are some decisions worth thinking through. Start by heading to the Status Pages section in your dashboard and clicking “New Status Page.” You’ll need a name and a slug—that’s the URL your customers will visit. Something like status.yourcompany.com works well, but you can also use the default loggy.dev domain to get started quickly.
The real work is deciding what to monitor. You have three options, and most pages use a mix of all three.
Heartbeat Monitors are perfect for internal systems your customers depend on but don’t directly interact with. Your nightly database backup job, your report generation cron, your cleanup scripts—anything that runs on a schedule and needs to report in. When these ping successfully, your customers see green. When they go silent, the status page reflects that honestly.
Uptime Monitors watch external URLs that your customers actually hit. Your API endpoints, your web app, your documentation site. Loggy checks these every few minutes and reports their status in real time. This is what most customers care about most directly—can they reach your service right now?
Direct URL Monitors let you monitor any arbitrary URL with custom configuration. This is useful for third-party dependencies your service relies on, or for endpoints that need specific headers or authentication to check properly.
Customization That Matches Your Brand
Your status page shouldn’t look like a generic template. It should feel like part of your product. Loggy lets you customize the company name, upload your logo, and set a primary color that matches your brand. You can choose between light and dark themes, add your Twitter handle for updates, and include contact information for support.
The customization goes deeper than just colors and logos. You can choose whether to show the “Powered by Loggy” badge—though we’d appreciate if you keep it—and you can control exactly which monitors appear on the page and in what order. Put your most critical services at the top where customers look first.
Custom Domains for Professional Status Pages
Once you’ve got your page configured, you can set up a custom domain. Instead of loggy.dev/status/your-slug, your customers visit status.yourcompany.com. It requires a simple CNAME record pointing to status.loggy.dev. You’ll need to configure your own SSL certificate through your DNS provider or CDN.
The custom domain feature is available on Pro and Team plans, and it’s worth the upgrade for the professionalism alone. When customers see status.yourcompany.com, they know you’re serious about transparency. It’s a small detail that signals maturity.
The Public API: Building Your Own Integrations
Every status page comes with a public JSON API that returns the current status of all your monitors. It’s available at https://loggy.dev/api/status-pages/public/:slug with no authentication required. This means you can build your own integrations—embed status indicators in your app, build widgets for your documentation, or create internal dashboards.
The API response includes the current status of each monitor, recent uptime percentages, and any active incidents. It’s the same data we use to render the status page, so you’re always getting the most current information.
What We’ve Been Improving
Recently we spent some time optimizing how status pages handle historical data. When you visit a status page and see that 90-day uptime chart, or when you scroll through incident history, that data needs to load fast and render smoothly.
We’ve improved our database indexing strategy for ping history, which means those historical uptime charts now load significantly faster. For pages with lots of monitors or long histories, the difference is especially noticeable. We’ve also optimized the queries that power the public API, so external integrations get snappy responses.
These improvements are live now for all status pages, and they make the experience better for everyone—your customers checking your status, and developers building integrations on top of our API.
The Incident Communication Workflow
A status page is only as good as the communication that happens during incidents. Here’s a workflow that works well for teams using Loggy.
When an alert fires or a monitor goes down, the first step is confirming the issue. Check your logs, look at your traces, verify it’s a real problem and not a false alarm. Once you’ve confirmed, declare an incident on your status page immediately. Click “Declare Incident” in your status page settings, give it a title like “API Degraded Performance,” set the severity (minor, major, or critical), and select which monitors are affected.
Your customers now know you’re aware and working on it. They don’t need to flood support or wonder if anyone noticed. The incident appears on your public status page with a status of “Investigating.”
As you learn more, update the incident. Change the status to “Identified” once you know what’s wrong, and add updates to the timeline. When you identify the cause, share it—your technical customers will appreciate the transparency, and it shows you understand the problem deeply. Change the status to “Monitoring” while you watch for recovery, and finally mark it “Resolved” when everything is back to normal.
Each update you add creates a timestamped entry in the incident timeline, so customers can follow along with your progress. This rhythm—acknowledge, investigate, resolve, follow up—builds trust even when things go wrong. Customers remember how you handled the incident more than the incident itself.
Managing Incidents in Loggy
To create and manage incidents, open your status page settings and scroll to the Incidents section. Click “Declare Incident” to create a new one. You’ll need to provide:
- Title: A brief description of what’s happening
- Description: Optional details about the issue
- Status: Investigating → Identified → Monitoring → Resolved
- Severity: Minor, Major, or Critical
- Affected Monitors: Which services are impacted
As the situation evolves, click the edit button on the incident to update its status and add timeline updates. Each update you add appears on your public status page with a timestamp, showing customers that you’re actively working on the problem.
Incidents are displayed on your public status page in a dedicated “Recent Incidents” section, showing the last 10 incidents with their full timeline of updates. Resolved incidents stay visible so customers can see your track record of transparency.
When Silence Is the Right Choice
There’s one exception to the transparency rule: security incidents. If you’re dealing with an active security issue that could put customer data at risk if disclosed publicly, it’s okay to handle that internally first. Communicate directly with affected customers once you’ve secured things. But for operational issues—downtime, performance degradation, service outages—your status page should be your first communication channel, not your last.
Free for Everyone
Status pages are available on all Loggy plans, including the free tier. You get one status page with up to three monitors—enough to cover your core services and show customers you care about transparency. As you grow, Pro and Team plans give you more status pages and more monitors per page, plus custom domains.
We made status pages a core feature because we believe every service, no matter how small, should be able to communicate openly with its customers. Transparency isn’t a premium feature—it’s a baseline expectation.
Getting Started
To create your first status page, head to the Status Pages section in your Loggy dashboard. Add a heartbeat for your background jobs, an uptime monitor for your API, and customize the page to match your brand. Share the URL with your customers, add it to your footer, put it in your support auto-responder.
Then, the next time something breaks, update the page first. Watch how it changes the tone of your customer conversations. Instead of “Is it down?” you’ll get “Saw the status page—thanks for the quick update.” That’s the difference transparency makes.
Happy monitoring!