Sources - StatusStack Documentation

What are Sources?

Sources are external services and platforms that StatusStack monitors for status updates, incidents, and outages. With over 11,000+ sources available, StatusStack provides comprehensive coverage of the services your applications depend on.

Source Categories

StatusStack organizes sources into logical categories to help you find and monitor the services that matter to your business:

Cloud Infrastructure

AWS, Google Cloud, Azure, DigitalOcean, Cloudflare

Payment Processing

Stripe, PayPal, Square, Braintree, Adyen

Communication

Slack, Discord, Zoom, Twilio, SendGrid

Development Tools

GitHub, GitLab, Docker Hub, NPM, CircleCI

Monitoring & Analytics

Datadog, New Relic, Google Analytics, Sentry

CDN & DNS

Cloudflare, AWS CloudFront, Fastly, Route 53

Source Structure

Each source contains detailed information about the service:

{
  "id": "01234567-89ab-cdef-0123-456789abcdef",
  "name": "Amazon Web Services",
  "key": "aws",
  "description": "Cloud computing services by Amazon",
  "status": "operational",
  "logo_url": "https://statusstack.com/logos/aws.png",
  "status_page_url": "https://status.aws.amazon.com/",
  "service_url": "https://aws.amazon.com",
  "components_count": 15,
  "incidents_count": 0,
  "categories": ["cloud", "infrastructure"],
  "last_checked_at": "2024-03-20T14:30:00Z"
}

Key Fields

string

Unique identifier for the source (e.g., “aws”, “stripe”, “github”)

string

Current overall status for monitoring: operational, degraded, down, maintenance

string

Link to the official status page maintained by the service provider

integer

Number of individual components monitored within this source

string

When StatusStack last updated the source’s status information

Source Status Levels

Sources use four operational statuses in monitoring and dashboards:

Operational

All systems functioning normallyThe service is running without any known issues. All components are operational and users should experience normal functionality.

Degraded

Some functionality may be impactedThe service is experiencing minor issues that may affect some users or features, but core functionality remains available.

Down

Service is experiencing significant issuesThe service is largely unavailable or experiencing major problems that significantly impact user experience.

Maintenance

Scheduled maintenance in progressThe service is undergoing planned maintenance. Some functionality may be temporarily unavailable.

Public source pages at /service/{source} also distinguish minor vs major in the H1, page title, and Open Graph cards. A component-only or minor incident does not headline as a vendor-wide major outage. See Public Source Pages.

Components

Most sources contain multiple components that represent individual services or features:

AWS Components Example

EC2 - Elastic Compute Cloud
S3 - Simple Storage Service
RDS - Relational Database Service
Lambda - Serverless computing
CloudFront - Content Delivery Network

Stripe Components Example

API - Core payment processing API
Dashboard - Merchant dashboard interface
Webhooks - Event notification system
Connect - Platform marketplace payments

Component Hierarchy

Some sources have hierarchical component structures:

GitHub
├── API
├── Git Operations
├── GitHub Pages
├── Actions
│   ├── Workflows
│   └── Packages
└── Issues & Pull Requests

Data Sources

StatusStack gathers source information from multiple data sources:

Official Status Pages

Primary source of truth - official status pages maintained by service providersExamples:

status.aws.amazon.com
status.stripe.com
www.githubstatus.com

RSS/Atom Feeds

Standardized feeds that provide structured status updatesBenefits:

Real-time notifications
Structured incident data
Historical information

API Endpoints

Direct integration with service provider APIs for real-time statusExamples:

Statuspage.io API
Custom provider APIs
Health check endpoints

Monitoring Frequency

StatusStack checks sources at different intervals based on their criticality and data source:

Critical Infrastructure: Every 30 seconds
High-Traffic Services: Every 1-2 minutes
Standard Services: Every 5 minutes
Low-Priority Services: Every 15 minutes

Regional Coverage

Many sources provide regional status information:

AWS Regions

us-east-1 (N. Virginia)
us-west-2 (Oregon)
eu-west-1 (Ireland)
ap-southeast-1 (Singapore)

Google Cloud Regions

us-central1 (Iowa)
europe-west1 (Belgium)
asia-east1 (Taiwan)

Multi-Region Services

Some services show global vs. regional status:

Global: Overall service availability
Regional: Specific geographic regions

Custom Sources

In addition to the 11,000+ pre-configured sources, you can create custom sources to monitor services that aren’t part of the built-in catalog. Custom sources are private to your organization and support two modes:

URL-Based Sources

Point StatusStack at any public status page URL. StatusStack matches common URL auto-detect fingerprints to choose a parser, and it can generate and parse a broader set of status page types. See the Custom Sources guide for setup steps. Common URL auto-detect fingerprints When you paste a status page URL, StatusStack matches common URL patterns. These fingerprints include:

Statuspage.io
BetterStack (BetterUptime)
Instatus
AWS Health Dashboard
Google Cloud Status
Microsoft Azure Status
GitHub Status (recognized as Statuspage.io — githubstatus.com maps to statuspage, not a separate generate type)
Cachet
OpenStatus (openstatus)

URL fingerprints are not the same as generate-source types. AWS Health, Google Cloud Status, Azure Status, and Cachet can be identified from a URL even though they are not generate-source types. Supported generate-source / parser types StatusStack can generate and parse custom sources for these types:

Adobe (adobe)
AllQuiet (allquiet)
Apple (apple)
BetterStack (betterstack)
Datadog (datadog)
Freshstatus (freshstatus)
Google (google) — this is not the Google Cloud Status URL fingerprint
Hund.io (hundio)
incident.io (incidentio)
Instatus (instatus)
Oh Dear (ohdear)
OpenStatus (openstatus)
Pingdom (pingdom)
RSS (rss)
Salesforce (salesforce)
Site24x7 StatusIQ (site24x7-statusiq)
Sorry (sorry)
Spectate (spectate)
StatusCast (statuscast)
StatusHub (statushub)
Status.io (statusio)
Statuspage.io (statuspage)
Statuspal (statuspal)
Tumblr (tumblr)
Updown (updown)
Upptime (upptime)
UptimeRobot (uptimerobot)
Microsoft 365 (microsoft365)

{
  "name": "Partner Payment Gateway",
  "status_page_url": "https://status.partnerpay.com",
  "status_page_type": "statuspage_io",
  "status": "operational"
}

Manual Sources

Create sources for internal services that don’t have a public status page. You manage the status directly from the dashboard.

{
  "name": "Internal User Service",
  "type": "manual",
  "status": "operational"
}

Organization Limits

Each organization can create up to 10 custom sources by default. Enterprise plans can request higher limits.

Website Monitors

You can also monitor your own websites and APIs with Custom Monitors:

{
  "name": "Company Website",
  "url": "https://mycompany.com",
  "check_type": "https",
  "interval": 60
}

Custom Sources Guide

Learn how to create and manage custom sources for your internal services

Public Source Pages

How /service/ vendor pages report severity, favicons, and region groups

Crowdsourced Incident Detection

StatusStack can detect service issues through community reports before official status pages update. When multiple users report problems with a service, StatusStack aggregates these reports, assigns a confidence score, and alerts your team early.

Early Warning: Get notified about outages before the provider acknowledges them
Confidence Scoring: Each crowdsourced incident is scored (0–100%) based on report volume and consistency
Detection Lead Time: Track how far ahead of the official status page the issue was detected

Crowdsourced Incidents Guide

Learn how crowdsourced incident detection works

Source Discovery

Find relevant sources for your stack:

By Technology Stack

# Get all cloud providers
GET /api/v1/sources?category=cloud

# Get payment processors
GET /api/v1/sources?category=payment

# Search for specific technologies
GET /api/v1/sources?search=kubernetes

By Dependencies

Map your application dependencies to StatusStack sources:

const myDependencies = [
  'aws',        // Infrastructure
  'stripe',     // Payments
  'sendgrid',   // Email
  'github',     // Code hosting
  'cloudflare', // CDN
  'datadog'     // Monitoring
];

// Monitor all dependencies
const sources = await Promise.all(
  myDependencies.map(key => 
    fetch(`/api/v1/sources?search=${key}`)
  )
);

Source Analytics

Track source reliability over time:

Uptime Metrics

30-day uptime percentage
Incident frequency
Average resolution time
Impact distribution

Performance Trends

Response time trends
Outage duration patterns
Peak incident times
Regional performance differences

Working with Sources

List All Sources

const sources = await fetch('/api/v1/sources');

Get Source Details

const aws = await fetch('/api/v1/sources/aws');

Monitor Specific Sources

const criticalSources = await fetch('/api/v1/sources?filter=aws,stripe,github');

Get Source Components

const awsComponents = await fetch('/api/v1/sources/aws/components');

Best Practices

Dependency Mapping

Map your infrastructure dependencies

Identify all external services your application uses
Create a dependency map showing relationships
Monitor both direct and indirect dependencies
Include backup and failover services

Criticality Assessment

Assess business impact of each source

Critical: Service unusable without this source
Important: Significant feature impact
Monitoring: Useful for awareness
Optional: Minimal business impact

Notification Strategy

Configure appropriate alerting

Immediate alerts for critical sources
Digest notifications for monitoring sources
Different channels for different severity levels
Escalation rules for prolonged outages

Status Communication

Keep stakeholders informed

Embed status widgets for customer-facing pages
Set up internal dashboards for operations teams
Prepare incident response communications
Document dependency relationships

Source Reliability

Sources are continuously validated for reliability:

Quality Metrics

Data freshness: How recently the source was updated
Accuracy: Historical accuracy of status information
Coverage: Completeness of component monitoring
Responsiveness: Speed of incident detection

Reliability Indicators

✅ Verified: Official status page with reliable data
⚡ Real-time: Sub-minute status updates
📊 Historical: Rich historical incident data
🌍 Regional: Regional status breakdown available

Common Source Patterns

SaaS Platforms

Most SaaS platforms follow similar patterns:

API endpoint monitoring
Dashboard availability
Feature-specific components
Webhook delivery status

Infrastructure Providers

Cloud providers typically organize by:

Compute services
Storage services
Networking services
Regional availability

Payment Processors

Payment services usually monitor:

Transaction processing
API availability
Webhook delivery
Dashboard access
Regional payment methods

Understanding sources helps you build comprehensive monitoring that covers all your critical dependencies and provides early warning when services your application relies on experience issues.

​What are Sources?

​Source Categories

Cloud Infrastructure

Payment Processing

Communication

Development Tools

Monitoring & Analytics

CDN & DNS

​Source Structure

​Key Fields

​Source Status Levels

​Components

​AWS Components Example

​Stripe Components Example

​Component Hierarchy

​Data Sources

​Monitoring Frequency

​Regional Coverage

​AWS Regions

​Google Cloud Regions

​Multi-Region Services

​Custom Sources

​URL-Based Sources

​Manual Sources

​Organization Limits

​Website Monitors

Custom Sources Guide

Public Source Pages

​Crowdsourced Incident Detection

Crowdsourced Incidents Guide

​Source Discovery

​By Technology Stack

​By Dependencies

​Source Analytics

​Uptime Metrics

​Performance Trends

​Working with Sources

​List All Sources

​Get Source Details

​Monitor Specific Sources

​Get Source Components

​Best Practices

​Source Reliability

​Quality Metrics

​Reliability Indicators

​Common Source Patterns

​SaaS Platforms

​Infrastructure Providers

​Payment Processors

What are Sources?

Source Categories

Source Structure

Key Fields

Source Status Levels

Components

AWS Components Example

Stripe Components Example

Component Hierarchy

Data Sources

Monitoring Frequency

Regional Coverage

AWS Regions

Google Cloud Regions

Multi-Region Services

Custom Sources

URL-Based Sources

Manual Sources

Organization Limits

Website Monitors

Crowdsourced Incident Detection

Source Discovery

By Technology Stack

By Dependencies

Source Analytics

Uptime Metrics

Performance Trends

Working with Sources

List All Sources

Get Source Details

Monitor Specific Sources

Get Source Components

Best Practices

Source Reliability

Quality Metrics

Reliability Indicators

Common Source Patterns

SaaS Platforms

Infrastructure Providers

Payment Processors