Setting Up a Status Page (Atlassian/Cachet/Instatus)

Imagine: on a Friday evening the database crashes, users flood support, and you waste time replying instead of fixing. A public status page solves this: customers see current service status and subscribe to notifications. We've rolled out such pages for a dozen projects, and incidents are no longer a surprise. Instead of a wave of support tickets, the client sees: "Known issue — working on a fix. ETA 14:30." This reduces first-line load and preserves trust. According to our practice, implementing a status page cuts support ticket volume by 40%, and reduces MTTR by 30% on average. Moreover, 60% of users check the status page before contacting support, further offloading the team.

Tool Comparison: Atlassian Statuspage vs Instatus vs Cachet

Atlassian Statuspage is a mature product with ready-made integrations. Instatus is cheaper and simpler. Cachet is for those who cannot share data with external vendors. In terms of setup speed, hosted solutions are 1.5x faster.

How to Deploy Cachet on Kubernetes

If you need a self-hosted status page, use Docker Compose or a Helm chart. Example minimal docker-compose.yml:

---
version: '3.8'
services:
  cachet:
    image: cachethq/docker:latest
    environment:
      - APP_KEY=base64:your-generated-key
      - DB_DRIVER=pgsql
      - DB_HOST=postgres
      - DB_DATABASE=cachet
      - DB_USERNAME=cachet
      - DB_PASSWORD=strongpassword
      - CACHE_DRIVER=database
    ports:
      - "8080:8000"
    depends_on:
      - postgres
  postgres:
    image: postgres:14
    environment:
      - POSTGRES_DB=cachet
      - POSTGRES_USER=cachet
      - POSTGRES_PASSWORD=strongpassword
    volumes:
      - cachet-db:/var/lib/postgresql/data
---

After startup, generate the APP_KEY by running php artisan key:generate inside the container. See official Cachet documentation for details.

How to Automate Status Updates?

Manually updating the status page during an incident is a bottleneck. We integrate the status service API with Alertmanager. Here's a step-by-step guide:

1. Configure a webhook in Alertmanager to send POST requests on alert changes.
2. Create an endpoint (e.g., Node.js or a ready connector) that receives the alert and updates the component via REST API.
3. Test scenarios: Degraded Performance on firing, Operational on resolve.

Example request for Cachet:

curl -X PUT "https://status.example.com/api/v1/components/1" \
 -H "X-Cachet-Token: your-api-token" \
 -H "Content-Type: application/json" \
 -d '{"status": 3}' # status: 1=Operational, 2=Degraded, 3=Partial Outage, 4=Major Outage

This approach reduces MTTR and ensures up-to-date information for users. According to Wikipedia, public status pages are an industry standard.

receivers: - name: statuspage webhook_configs: - url: http://your-webhook-endpoint/alert send_resolved: true 

Why Hosted Solution Is Faster?

Hosted services (Atlassian Statuspage, Instatus) require no infrastructure management. You get a ready SSL, custom domain, and integrations with PagerDuty or Datadog in a couple of hours. Self-hosted Cachet gives full control but requires database setup, backups, and monitoring of the status service itself. If you have no strict confidentiality requirements, a hosted option saves time.

What's Included in the Work?

• Audit of current monitoring infrastructure (Prometheus, Datadog, etc.)
• Selection of the appropriate status service based on security and cost criteria
• Deployment (hosted or self-hosted) with custom domain and SSL
• Configuration of service components (API, DB, CDN, Payment)
• Integration with alerting systems via webhook/API
• Preparation of incident templates and update rules
• End-to-end testing and team training

Typical Implementation Mistakes

Timelines and Cost

Hosted solution (Atlassian/Instatus) — from 4 hours to a full day. Self-hosted Cachet with full infrastructure and automation — 1-2 business days. Exact timelines depend on integration complexity. Contact us — we'll assess your project and find the optimal solution. Order a consultation on status page integration — get a ready page without hidden pitfalls. Our engineers have over 10 years of DevOps experience and have implemented dozens of status pages. We guarantee your users see incident information without delays.