Pulumi status history
Current state: operational — “All Systems Operational” per https://status.pulumi.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Pulumi incidents last?
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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-11 18:02 UTC | Neo Outage | resolved | critical | 6 h 17 min |
| 2026-08-17 14:05 UTC | GitHub services failing | resolved | none | 3 h 01 min |
| 2026-07-24 02:56 UTC | Some Team Access Token operations failing | resolved | minor | 1 h 28 min |
| 2026-07-08 19:09 UTC | Degraded performance for Pulumi Cloud login | resolved | minor | 35 min |
| 2026-06-22 18:06 UTC | Degraded performance on Pulumi APIs | resolved | minor | 1 h 46 min |
| 2026-06-11 22:20 UTC | Bitbucket authentication failures affecting sign-in and Bitbucket-backed accounts | resolved | minor | 1 h 57 min |
| 2026-05-12 21:05 UTC | Elevated API error rates and latency | resolved | minor | 2 h 09 min |
| 2026-04-20 10:30 UTC | Elevated errors when decrypting ESC environments | resolved | none | 0 min |
| 2026-04-15 09:43 UTC | Bitbucket Authentication Unavailable | resolved | major | 4 h 27 min |
| 2026-04-10 17:58 UTC | Slowed API response times | resolved | minor | 11 min |
| 2026-03-06 11:29 UTC | Machine tokens unable to open referenced environments when running stack previews. | resolved | minor | 22 min |
| 2026-02-03 23:26 UTC | Errors when creating new Pulumi Neo tasks | resolved | major | 6 min |
| 2025-11-18 13:44 UTC | get.pulumi.com unreachable | resolved | none | 2 h 01 min |
| 2025-10-20 15:05 UTC | AWS outage | resolved | major | 12 h 20 min |
| 2025-09-08 17:27 UTC | Issue displaying some previews in Pulumi Cloud | resolved | minor | 1 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
}