outages.live
Live
PulumiIncident · 2026-08-17 14:05 UTC

GitHub services failing

ResolvedOfficial update

This incident has been resolved.

The latest update from Pulumi.

State

Resolved

Started

76 d ago

2026-08-17 14:05 UTC

Lasted

3 h 1 min

until 2026-08-17 17:06 UTC

Worst impact

Notice

Timeline

3 updates
14:0514:5015:3516:2117:06
NoticeUpdate postedTimes in UTC

Investigating

3 h 1 min 100%

Updates

Times in UTC

As posted by Pulumi

Resolved2026-08-17 17:06 UTC

This incident has been resolved.

Investigating2026-08-17 14:30 UTC

https://www.githubstatus.com/incidents/zkxwbgr0cnmx

Investigating2026-08-17 14:05 UTC

GitHub has reported an active, critical incident. Related functionality in the Pulumi Console is temporarily unavailable.

Affected components

2
GitHubThird Party Services - GitHub

Pulumi in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

5

Days with an incident

6

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·Bitbucket login is not available

This incident has been resolved.

Resolvedresolved 16 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

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