Pulumi reported "Bitbucket login is not available" on its status page at 2026-10-16 10:48 UTC.

Pulumi lists these components: API, Console.

When did the incident start and end?

It started at 2026-10-16 10:48 UTC and ended at 2026-10-16 13:30 UTC. It lasted 2 h 43 min.

How do I get alerts for Pulumi?

Subscribe to the Pulumi live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Pulumi. outages.live reads it every few minutes and keeps every update.

PulumiIncident · 2026-10-16 10:48 UTC

Bitbucket login is not available

ResolvedOfficial update

This incident has been resolved.

The latest update from Pulumi.

State

Resolved

Started

16 d ago

2026-10-16 10:48 UTC

Lasted

2 h 43 min

until 2026-10-16 13:30 UTC

Worst impact

Partial outage

Timeline

3 updates

10:4811:2912:0912:5013:30

Partial outageUpdate postedTimes in UTC

Identified

1 h 6 min 40%

Monitoring

1 h 37 min 60%

Updates

Times in UTC

As posted by Pulumi

Resolved2026-10-16 13:30 UTC

This incident has been resolved.

Monitoring2026-10-16 11:54 UTC

A fix has been deployed and we're monitoring the results.

Identified2026-10-16 10:48 UTC

We know about a problem with Bitbucket login for Pulumi Cloud. The problem started on 15 October 2026 at approximately 16:51 UTC. You cannot log in to Pulumi Cloud with your Bitbucket account at this time. After you log in at Bitbucket, Pulumi Cloud shows the message "Internal Server Error". Other login methods or Bitbucket repository integrations and deployments are not affected.

Affected components

APIConsole

Pulumi in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 43 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 h 18 min

median 2 h 43 min

90 days agoToday

Other Pulumi incidents

All incidents

Pulumi·Elevated error rates and intermittent failures across Pulumi Cloud

This incident has been resolved. Error rates and latency have been normal since 19:24 UTC, and all systems are operating normally.

Resolvedresolved 2 d ago

Pulumi·Issues with Pulumi OIDC (inbound)

This incident has been resolved.

Resolvedresolved 26 d ago

Pulumi·Neo Outage

This incident has been resolved.

Resolvedresolved 51 d ago

Pulumi·GitHub services failing

This incident has been resolved.

Resolvedresolved 76 d ago

Follow Pulumi

Your coding agent knows when Pulumi is down, and tells you when a failure is theirs, not yours. You can also get Pulumi incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "pulumi" and tell me if Pulumi has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=pulumi

Slack

/feed subscribe https://outages.cc/feed.xml?providers=pulumi

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane