← All guidesSIGNALPIER FIELD GUIDE

How to read a cloud outage report

Understand regions, components and shared dependencies before connecting an incident to your application.

01

Match the product and region

An incident in one cloud region does not establish a global outage. Match the affected service, availability zone and feature to your workload.

02

Separate platform and product status

A shared provider feed can supply context without proving that a specific product is affected. SignalPier labels these platform signals separately.

03

Inspect the original update

Read the provider’s timestamp, mitigation notes and current impact. Long-running advisories can stay open after parts of a service have recovered.

04

Check your own dependencies

Authentication, DNS, storage and third-party APIs can fail independently. An application can be unavailable even while its hosting provider reports no active incident.

05

Document observed behavior

Capture non-sensitive error codes and times for your own support team. Never paste API keys, signed URLs or customer data into a public outage report.

Find your service →