Reference · built on requestConnectorIdentity, IT & observability

Statuspage

Incidents, component operational statuses, scheduled maintenance, and subscriber notifications via the Atlassian Statuspage REST API.

Request accessPricing ↗

About

Statuspage is an incident communication platform managed by Atlassian that keeps customers and internal teams informed during downtime and maintenance events. Its REST API allows organizations to programmatically manage public and private status pages, update service component health states, post real-time incident messages, and schedule maintenance windows.

Through Fibric, an operator correlates infrastructure alerts with customer-facing status pages, proposing incident updates or component status changes for human sign-off.

This is a reference listing. It documents what Fibric would read from Statuspage and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Page details and overall status configuration via GET /v1/pages/{page_id}
  • Components, component groups, and operational statuses through GET /v1/pages/{page_id}/components
  • Active and resolved incidents with update histories from GET /v1/pages/{page_id}/incidents
  • Scheduled maintenance events and windows through GET /v1/pages/{page_id}/incidents/scheduled
  • Page subscriber counts and notification preferences via GET /v1/pages/{page_id}/subscribers

Proposed actions

  • Target capability: propose creating an incident with component updates via POST /v1/pages/{page_id}/incidents
  • Target capability: propose posting a real-time progress update to an active incident
  • Target capability: propose updating a component status to operational, degraded, or outage
  • Target capability: propose scheduling a maintenance event with specified start and end times

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Publish incident notices during critical outages

    When core service health checks fail, draft an incident description and propose updating public component statuses so users receive prompt notice.

    With Uptime Response, On-call Handoff

  • Automate scheduled maintenance announcements

    Parse approved maintenance calendar entries and propose scheduled maintenance events on Statuspage, detailing affected systems and planned windows.

    With Patch Window, Change Freeze

  • Resolve incidents after monitoring recovers

    When telemetry confirms metrics returned to healthy baselines for 15 minutes, propose closing the open Statuspage incident with an all-clear message.

    With Uptime Response

Requirements

  • An active Atlassian Statuspage subscription with an established page ID
  • An API key with permission to create incidents and update components on the target page
  • Defined service component structures reflecting actual architecture tiers
Authentication
Statuspage API key passed as an Authorization header with OAuth scheme against api.statuspage.io/v1/.

Limits

  • The Statuspage REST API limits requests to 60 calls per minute per IP address and API key
  • Public status pages restrict maximum component counts to 100 components per page
  • Subscriber notifications sent via SMS and email are throttled to prevent messaging provider blocks

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Statuspage ↗

Questions and answers

What component statuses does Statuspage support?
Statuspage supports operational, degraded_performance, partial_outage, major_outage, and under_maintenance. Fibric can propose updating any component to reflect observed infrastructure health.
Can Fibric notify subscribers directly without creating an incident?
Statuspage notifications are tied to incidents or maintenance posts. Subscribers receive email, SMS, or webhook alerts whenever an incident is created or updated with notification flags enabled.
Does Fibric post public status updates without human approval?
No. Fibric drafts the incident headline, component impacts, and customer-facing update text for operator review. A designated engineer must approve the proposal before it publishes.
Ask about Statuspage

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Statuspage through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy