Vendor Status Watch

← all vendors

Pulumi status history

Current state: operational — “All Systems Operational” per https://status.pulumi.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

2incidents, last 30 days
5incidents, last 90 days
15incidents on record
Incidents per week, last 12 weeks:

How long do Pulumi incidents last?

114 minmedian incident duration15 measured
6.3 h90th percentile1 in 10 ran longer
5.4 hmedian, major/critical only4 incidents

From 15 incidents with a vendor-posted start and resolve time. Longest on record: AWS outage — 12.3 h (2025-10-20 15:05 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (15)

StartedIncidentStatusImpactDuration
2026-09-11 18:02 UTCNeo Outageresolvedcritical6 h 17 min
2026-08-17 14:05 UTCGitHub services failingresolvednone3 h 01 min
2026-07-24 02:56 UTCSome Team Access Token operations failingresolvedminor1 h 28 min
2026-07-08 19:09 UTCDegraded performance for Pulumi Cloud loginresolvedminor35 min
2026-06-22 18:06 UTCDegraded performance on Pulumi APIsresolvedminor1 h 46 min
2026-06-11 22:20 UTCBitbucket authentication failures affecting sign-in and Bitbucket-backed accountsresolvedminor1 h 57 min
2026-05-12 21:05 UTCElevated API error rates and latencyresolvedminor2 h 09 min
2026-04-20 10:30 UTCElevated errors when decrypting ESC environmentsresolvednone0 min
2026-04-15 09:43 UTCBitbucket Authentication Unavailableresolvedmajor4 h 27 min
2026-04-10 17:58 UTCSlowed API response timesresolvedminor11 min
2026-03-06 11:29 UTCMachine tokens unable to open referenced environments when running stack previews.resolvedminor22 min
2026-02-03 23:26 UTCErrors when creating new Pulumi Neo tasksresolvedmajor6 min
2025-11-18 13:44 UTCget.pulumi.com unreachableresolvednone2 h 01 min
2025-10-20 15:05 UTCAWS outageresolvedmajor12 h 20 min
2025-09-08 17:27 UTCIssue displaying some previews in Pulumi Cloudresolvedminor1 h 54 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Pulumi with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "pulumi"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}