2321 of 2463 services operational right now

Find out when a dependency breaks.

PulsAPI watches 2463+ vendor status pages (every 60 seconds while one is moving), normalizes Statuspage JSON, RSS, and custom HTML into one feed, and routes the alert before your users notice.

Start free, 30 days

Request a demo

Most recent signal changecPanel now partial outage (32s ago)

Live Status Board

Updated 32s ago

Service30d uptimeStatus

AWSCLOUD

95.4%

Partial Outage

StripeFINTECH

99.6%

Operational

GitHubDEVTOOLS

99.93%

Operational

VercelCLOUD

99.98%

Operational

CloudflareCDN

96.1%

Partial Outage

DatadogDEVTOOLS

100%

Operational

SupabaseCLOUD

99.992%

Operational

SentryDEVTOOLS

99.97%

Operational

2463 services monitored, all signals in one placeView all

AWSStripeGitHubVercelCloudflareDatadogTwilioSupabaseNetlifyPagerDutySentryMongoDBOpenAIAnthropicSnowflakeDatabricksAWSStripeGitHubVercelCloudflareDatadogTwilioSupabaseNetlifyPagerDutySentryMongoDBOpenAIAnthropicSnowflakeDatabricksAWSStripeGitHubVercelCloudflareDatadogTwilioSupabaseNetlifyPagerDutySentryMongoDBOpenAIAnthropicSnowflakeDatabricks

Across the catalog right now

Vendors monitored2463across 20 categories

Operational232194.2% of catalog

Reporting issues143needs attention

Poll cadence60swhile a vendor is moving

Median route to channelunder 4smedian time to channel

What happens when AWS posts a partial outage.

Four automated steps. Nobody has to refresh a tab.

01Detectlive
The AWS Health endpoint marks one component degraded. AWS is on the 60-second tier the moment anything stops being fully operational, so PulsAPI picks it up on the next poll.
02Normalize
Statuspage JSON, RSS, custom HTML: whatever the vendor publishes gets collapsed into one status with a confidence score.
03Route
Your alert rule matches (critical severity, on-call team, Slack and PagerDuty). The channel fires within about 4 seconds of detection.
04Log
An SLA breach opens against your downtime budget. The 90 day report and CSV export update before you finish reading the alert.

live replayt+0.0s

AWS Health · EC2 us-east-1

degradeddetected 4s ago

Increased API error rates on the AWS Health endpoint, one component affected.

Fusion Engine

Every vendor publishes status differently. You read one schema.

Atlassian uses Statuspage JSON. AWS ships RSS. GitHub Actions has its own JSON shape. Apple still serves JSONP. PulsAPI normalizes all of it so your dashboard, alert rules, and SLA math do not care which vendor broke.

canonical signal

AWSDEGRADED

componentEC2

regionus-east-1

confidence0.94

Three of the 40+ formats PulsAPI parses. RSS, Statuspage JSON, JSONP, and custom HTML all land in the same schema.

Auto-discovery

You should not have to remember what your stack depends on.

Connect a read-only AWS role or a fine-grained GitHub token. PulsAPI reads your tagged cloud resources and your production dependency manifests, then proposes the vendors it found, with the line of evidence that proved each one. Nothing is monitored until you approve it.

readspackage.json

"dependencies": {  "stripe": "^14.21.0",  "@sendgrid/mail": "^8.1.0",  "@datadog/browser-rum": "^5.9.1",  "twilio": "^4.20.0"}

Production dependency manifests. Read-only, and nothing else in the account is touched.

proposes0 of 4 found

Nothing is monitored until you approve it.Scan your stack free

01Connect

A read-only credential, scoped to one permission. Neither key can change anything in your account.

02Scan

Pick the repositories or regions to look at. Rescanned daily at 03:15, so the picture keeps up as your stack drifts.

03Approve

Every finding arrives as a proposal with its evidence. What you confirm becomes a board group and starts alerting.

Auto-discovery is available from the Starter plan, including the 30 day trial. Credentials are encrypted at rest and never leave PulsAPI.

The 2am work, without six browser tabs open.

Detection, diagnosis, alerting, and compliance reporting from one dashboard.

Detect

Catch degradations before the vendor posts about them.

Fusion Engine across 40+ vendor formats
Early warnings on component degradation
Component-level granularity (S3 us-east-1, not just "AWS")
Canonical regions across AWS, Azure, GCP

Diagnose

One view from alert to likely cause.

Incident timelines: investigating, identified, monitoring, resolved
90-day activity feed and health heatmap
Sub-component sparklines per service
Portfolio-wide health indicator

Alert

Right person, right channel, right severity.

Alert rules by service, component, severity, latency, SLA breach
Escalation policies with timed handoff to on-call
Slack, Discord, MS Teams, PagerDuty, Webex, SMS, webhooks, email
Maintenance windows that suppress noise without dropping data

Comply

Vendor accountability with receipts.

7, 30, and 90 day SLA reports with MTTR and MTTA
Downtime budget tracking against custom or vendor targets
P50, P95, P99 latency percentiles
SSO/SAML, RBAC, audit logs, CSV and PDF export

Same feed, different job.

On-call engineers, compliance leads, and the VP signing the renewal all look at the same vendor signal for different reasons.

Site Reliability

One board instead of tab-hopping at 2am.

One board for the full third-party surface
Embeddable TV dashboard for the NOC
MCP server so your on-call agent can answer "is X up?" in chat

Compliance & RevOps

Hold vendors to what they promised.

Custom SLA targets per service with breach tracking
CSV and PDF export for audit packets
SSO/SAML, RBAC, audit logs from day one on Business

Engineering Leaders

Flat pricing, no per-service surprises.

Flat per-workspace pricing
30-day Business trial, no credit card, full feature set
API keys, webhooks, Firehose SSE for your own tooling

Built for people who wire things up

REST API
Programmatic access with API keys and per-plan rate limits.
Webhooks
Outbound HTTP on every status change, incident, and SLA breach.
Firehose SSE
Real-time stream of the normalized signal.
MCP Server
Tools for Claude, ChatGPT, and custom agents.
Embeds
iframe, badge, modal, and TV widgets with theme support.
CSV / PDF
Exports of SLAs, breaches, and incidents for audits.

Simple, transparent pricing.

Three services free, forever. Unlimited email alerts, no monthly cap. Pro removes the monitor limit entirely and never meters it again, which is the part the incumbents charge you for at every step. 30 days of Business on signup, no credit card.

Free

Your three most critical vendors, watched properly.

Free

3monitored services

Enough to prove the signal is worth trusting.

Start free

Unlimited email alerts, no monthly cap
15 days of incident history
Live status dashboard and public API (10 req/min)
GitHub stack discovery scan
1 user, 1 board

Pro

When it stops being your dashboard and starts being the team's.

$29$23/mo billed annuallySave 20%

Unlimitedmonitored services

Unlimited monitors, and alerts where your team actually works.

Start 30-day trial

Slack, Discord, Microsoft Teams, Google Chat
SLA reports with MTTR, CSV and PDF export
Downtime budget tracking, P50/P95/P99 latency
90 days of incident history
Alert rules and maintenance windows
You plus 3 viewers; admin seats start on Business
3 outbound webhooks, 5 API keys, API 100 req/min
MCP server, monitor groups and tags
AI provider probes from the call site, on your own API key

Business

When you have to prove what happened, not just hear about it.

$99$79/mo billed annuallySave 20%

Unlimitedmonitored services

The audit trail: 13 months of history, SSO, and on-call escalation.

Start 30-day trial

Everything in Pro
13 months of incident history: a full audit year plus the current month
PagerDuty, Opsgenie and escalation policies
SSO / SAML, RBAC and audit logs
Alert analytics with MTTA, and executive incident reports
AI provider probes we run and pay for, $50 of usage a month included
Published status pages, embeds and the event firehose
15 admins, 5 workspaces, 25 webhooks
API 1,000 req/min · priority support

Enterprise

When procurement, not engineering, decides.

From $499

Unlimitedmonitored services

The paperwork and the guarantees.

Book a 30-minute demo

Everything in Business
Unlimited admins, viewers and workspaces
DPA / AVV, EU data residency
Custom SLA targets and retention by contract
Custom integrations and API rate limits
Named contact, onboarding and security review support

Not sure which tier fits, or need it to clear a security review? Book a 30-minute demo.

Frequently asked questions

What is PulsAPI?

PulsAPI monitors 2463+ cloud vendors in one place: live status, incident timelines, and 90-day SLA history. It is built for teams that need to know when a third-party dependency breaks before their users do.

How is PulsAPI different from checking individual status pages?

You could open 40 tabs and refresh them yourself. PulsAPI puts the same vendors in one view, tracks components and regions separately, routes alerts to Slack or PagerDuty, and keeps 90 days of SLA and MTTR data without manual spreadsheet work.

How fast are PulsAPI alerts?

The crawler polls vendor status pages every 60 seconds. Once a change is detected, alerts usually reach Slack, Discord, Microsoft Teams, PagerDuty, webhooks, or email in under 4 seconds. You can filter by service, severity, and custom rules.

What cloud services does PulsAPI monitor?

PulsAPI covers 2463+ services across cloud (AWS, GCP, Azure), dev tools (GitHub, GitLab), CI/CD, payments (Stripe, PayPal), communication (Twilio, SendGrid), monitoring, CDN, and more.

Is there a free trial?

Yes. New accounts get a 30-day Business trial with full features and no credit card. After that you drop to the free plan (3 services with email alerts, 15-day history) unless you upgrade to Pro or Business.

Can I track individual components and regions?

Yes. You can watch AWS S3 in us-east-1 separately from Lambda in eu-west-2, or Stripe API separately from the Stripe Dashboard. That matters when only one piece of a vendor is actually affecting your app.

What is the PulsAPI Fusion Engine?

Vendors publish status as Statuspage JSON, RSS, custom HTML, JSONP, and other shapes. The Fusion Engine normalizes all of them into one schema with a confidence score, so alerts and SLA math do not depend on how the vendor formats their page.

Does PulsAPI support escalation policies and maintenance windows?

Pro and Business include alert rules with severity routing, cooldowns, and per-condition channels. Business adds escalation policies that hand off between on-call channels on a timer, plus maintenance windows that mute alerts during planned work without deleting the underlying data.

Can I expose PulsAPI to my own tools through an API or MCP server?

Pro and above include REST API keys, outbound webhooks, and a Server-Sent Events Firehose of the normalized signal. Enterprise adds an MCP server so Claude, ChatGPT, or custom agents can check vendor status from chat.

What about SSO, RBAC, and audit logs for compliance?

Business includes SAML SSO, role-based access (Owner, Admin, Member), and an audit log of user, integration, and rule changes with timestamps and IP addresses. CSV and PDF export are there when compliance asks for proof.