Degraded performance on Pulumi APIs
Update - We are continuing to investigate this issue.
Jun 22, 2026 - 11:30 PDT
Investigating - We are aware of degraded performance on Pulumi APIs and are actively investigating the issue.
Jun 22, 2026 - 11:06 PDT
Uptime over the past 90 days. View historical uptime.
API Degraded Performance
90 days ago
99.93 % uptime
Today
Console Operational
90 days ago
99.93 % uptime
Today
Deployments Degraded Performance
90 days ago
100.0 % uptime
Today
Search Degraded Performance
90 days ago
100.0 % uptime
Today
Third Party Services Operational
90 days ago
100.0 % uptime
Today
AWS ec2-us-west-2 Operational
90 days ago
100.0 % uptime
Today
AWS elb-us-west-2 Operational
AWS s3-us-west-2 Operational
90 days ago
100.0 % uptime
Today
AWS rds-us-west-2 Operational
GitHub Operational
90 days ago
100.0 % uptime
Today
Stripe API Operational
90 days ago
100.0 % uptime
Today
GitLab Operational
90 days ago
100.0 % uptime
Today
Docker Operational
90 days ago
100.0 % uptime
Today
Mailchimp Operational
90 days ago
100.0 % uptime
Today
Stripe JS Operational
Registry Operational
90 days ago
100.0 % uptime
Today
Docs Operational
90 days ago
100.0 % uptime
Today
Pulumi Copilot Operational
90 days ago
100.0 % uptime
Today
Pulumi Neo Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jun 22, 2026

Unresolved incident: Degraded performance on Pulumi APIs.

Jun 21, 2026

No incidents reported.

Jun 20, 2026

No incidents reported.

Jun 19, 2026

No incidents reported.

Jun 18, 2026

No incidents reported.

Jun 17, 2026

No incidents reported.

Jun 16, 2026

No incidents reported.

Jun 15, 2026

No incidents reported.

Jun 14, 2026

No incidents reported.

Jun 13, 2026

No incidents reported.

Jun 12, 2026

No incidents reported.

Jun 11, 2026
Bitbucket authentication failures affecting sign-in and Bitbucket-backed accounts
Resolved - The incident has now been resolved and the service is operating normally for all customers.
Jun 11, 17:17 PDT
Monitoring - Atlassian has deployed a fix for their incident affecting Bitbucket OAuth login, and we have confirmed that Bitbucket authentication requests from Pulumi Cloud are succeeding again. Error rates have returned to normal levels and sign-in with Bitbucket is working.
Jun 11, 17:02 PDT
Identified - Atlassian has acknowledged an incident affecting Bitbucket OAuth login,
which is the cause of the Bitbucket sign-in and authentication failures
affecting Pulumi Cloud. Their incident is being tracked at:
https://bitbucket.status.atlassian.com/incidents/h51sr145gsmx

The issue is external to Pulumi, and no action is required from Pulumi
customers. Until Atlassian resolves their incident, customers signing in
with a Bitbucket identity may continue to experience failed sign-ins and
intermittent Console and API errors after their current session token
expires. Customers using GitHub, GitLab, email, or SSO identities remain
unaffected.

Workaround: Customers whose Pulumi account has an additional sign-in method
(GitHub, GitLab, email/password, or SSO) can continue to sign in using that
method.
Jun 11, 15:56 PDT
Investigating - We are investigating an issue affecting customers who sign in to Pulumi Cloud
with a Bitbucket identity or use Bitbucket-connected accounts.

Beginning at approximately 06:00 UTC on June 11, requests to refresh Bitbucket
authentication tokens began failing. Affected users may experience failed
sign-ins with Bitbucket, as well as intermittent errors in the Pulumi Console
and API after their current Bitbucket session token expires (these tokens
expire every two hours). Integrations that rely on Bitbucket credentials may
also be affected.

Our investigation indicates the failures originate from Bitbucket's OAuth
token service rather than Pulumi infrastructure, and we have engaged Atlassian
support. Customers using GitHub, GitLab, email, or SSO identities
are unaffected.

Workaround: Customers whose Pulumi account has an additional sign-in method
(GitHub, GitLab, email/password, or SSO) can continue to sign in using that
method.

We will post updates as the investigation progresses.
Jun 11, 15:20 PDT
Jun 10, 2026

No incidents reported.

Jun 9, 2026

No incidents reported.

Jun 8, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage