Instatus

Overview

Instatus, acquired by Grafana Labs in 2022, provides a platform for creating and managing status pages to communicate service incidents and scheduled maintenance. The platform is designed to help organizations maintain transparency with their users and internal stakeholders during periods of service disruption or planned downtime. It offers tools for publishing real-time updates on system status, managing incident workflows, and notifying subscribers through various channels.

The primary use case for Instatus is incident communication, allowing companies to inform their customers about outages, performance issues, and resolution progress. This capability is critical for sectors where service availability directly impacts user trust and business operations, such as SaaS providers, e-commerce platforms, and online service providers. Instatus supports both public-facing status pages, accessible to all users, and private status pages, restricted to internal teams or specific client groups.

Organizations utilize Instatus to centralize incident information. During an incident, teams can update the status page directly, detailing the problem, its impact, and the steps being taken to resolve it. This reduces the volume of support requests by proactively addressing user concerns. The platform also includes features for automating notifications, ensuring that subscribers receive updates via email, SMS, or other integrated services as soon as new information is available. This proactive communication strategy aims to mitigate the negative impact of downtime on user experience and satisfaction.

For developers and technical buyers, Instatus offers a REST API that enables programmatic interaction with status pages and incident management workflows. This allows for integration with existing monitoring systems, CI/CD pipelines, and incident response tools, automating the creation and updating of incidents based on system alerts. The API's straightforward design facilitates embedding status page management into broader operational processes, enhancing the efficiency of incident response. The platform's emphasis on customization allows companies to brand their status pages to match their corporate identity, reinforcing a consistent user experience even during service interruptions.

Key features

• Public and Private Status Pages: Create public pages for customer communication and private pages for internal teams or specific clients.
• Incident Management: Tools for declaring incidents, updating their status (e.g., investigating, identified, resolved), and detailing impact.
• Scheduled Maintenance: Communicate planned downtimes in advance, allowing users to prepare for service interruptions.
• Automated Notifications: Send updates to subscribers via email, SMS, Slack, and other channels upon incident status changes or new posts.
• Customization: Brand status pages with custom domains, logos, and styling to align with corporate identity.
• Component-Based Status: Display the status of individual system components (e.g., API, database, website) separately.
• Historical Uptime: Provide historical data on component uptime and performance trends.
• API Access: A REST API for programmatic incident creation, updates, and status page management (Instatus API documentation).
• Subscription Management: Allow users to subscribe to updates for specific components or all incidents.
• Multi-language Support: Offer status pages in multiple languages to cater to a global user base.

Pricing

Instatus offers a free tier and various paid plans that scale based on the number of subscribers and features. The pricing structure is designed to accommodate different organizational sizes and communication needs.

For detailed and up-to-date pricing information, refer to the official Instatus pricing page.

Common integrations

Instatus integrates with various services to automate incident reporting and notification processes. Common integrations include:

• Monitoring Tools: Connect with services like Grafana, Datadog, or Prometheus to automatically create incidents based on alerts.
• Communication Platforms: Integrate with Slack, Microsoft Teams, or PagerDuty for internal team notifications and incident response coordination.
• CRM & Support Systems: Link with platforms like Salesforce or Freshworks to log incidents or inform support agents.
• CI/CD Pipelines: Incorporate status page updates into deployment workflows to announce planned maintenance.

Alternatives

Several platforms offer similar status page and incident communication capabilities. These alternatives often vary in pricing, feature sets, and integration ecosystems:

• Statuspage (Atlassian): A widely used status page solution offering extensive integrations and enterprise features.
• Better Uptime: Combines uptime monitoring, incident management, and status pages into a single platform.
• Status.io: Provides advanced multi-component status pages and extensive notification options for complex infrastructures.

Getting started

To get started with Instatus using its API, you can create an incident programmatically. This example uses cURL to create a new incident on a specified status page. You will need your API key and the ID of your status page.

First, ensure you have an Instatus account and have generated an API key from your dashboard. You will also need the ID of the status page where you want to post the incident. This can typically be found in the URL when viewing your status page in the Instatus dashboard (e.g., https://instatus.com/dashboard/pages/[PAGE_ID]).

# Replace 'YOUR_API_KEY' with your actual Instatus API key
# Replace 'YOUR_PAGE_ID' with the ID of your status page
# Replace 'YOUR_COMPONENT_ID' with the ID of the affected component (optional)

curl -X POST \
  https://api.instatus.com/v1/pages/YOUR_PAGE_ID/incidents \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -d '{ 
    "name": "Website experiencing degraded performance", 
    "message": "We are currently investigating an issue causing slow load times on our website. Updates will be posted here.", 
    "status": "investigating", 
    "components": ["YOUR_COMPONENT_ID"], 
    "notify": true 
  }'

This cURL command sends a POST request to the Instatus API endpoint for creating incidents. The name field provides a summary, and the message field contains a more detailed description. The status field indicates the current state of the incident (e.g., investigating, identified, resolved). The components array allows you to link the incident to specific system components, and notify determines whether subscribers receive an immediate notification. Upon successful execution, the API will return a JSON object confirming the incident's creation, including its ID and other details.