Porter

Affected: Porter UI, Porter API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-07-16 09:13 UTC

   We're currently experiencing increased authentication failure rates with the Porter dashboard and the CLI, due to an incident with an upstream provider. We're monitoring this, and will continue to roll out updates as we receive them. For more details on the upstream incident,...

2. monitoring 2026-07-16 09:25 UTC

   We've reached out to the upstream provider. They're currently investigating elevated error rates across their platforms, but as of now there are no further updates.

3. monitoring 2026-07-16 10:13 UTC

   The upstream provider is still working towards identifying the root cause and pushing a fix.

4. monitoring 2026-07-16 10:15 UTC

   The upstream provider has identified the issue and applied a fix. Authentication error rates are decreasing; however, you may still see intermittent issues with authenticating against the dashboard.

5. monitoring 2026-07-16 10:20 UTC

   While we await confirmation from the upstream provider about this incident's resolution, we can confirm that dashboard authentication errors on Porter are now down to zero. We're continuing to monitor things on our end.

6. resolved 2026-07-16 10:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Porter's status page.

Affected: Porter CLI Installer

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2026-03-09 15:14 UTC

   We are currently investigating downtime with our CLI installer at https://install.porter.run.

2. investigating 2026-03-09 15:19 UTC

   We are continuing to investigate this issue.

3. identified 2026-03-09 15:22 UTC

   The issue has been identified and a fix has been rolled out.

4. identified 2026-03-09 15:23 UTC

   A fix has been pushed live, and we're monitoring the CLI installer site to ensure it's back to normal.

5. monitoring 2026-03-09 15:27 UTC

   We're continuing to monitor our fix.

6. resolved 2026-03-09 15:36 UTC

   This incident has been resolved. We're tracing this to an inadvertent change that was pushed to our Cloudflare DNS zone which inadvertently impacted the DNS CNAME record for install.porter.run. This change didn't affect the Porter dashboard or customer workloads. We're looking...

Excerpts are shortened. Read the full incident on Porter's status page.

Affected: Porter UI, Porter API

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-19 14:04 UTC

   We're currently investigating an issue where failure notifications are triggering redeployments, when clicked on in the Porter dashboard. The issue only occurs if a user explicitly expands on an app failure notification.

2. identified 2025-08-19 14:39 UTC

   The issue has been reproduced and the root cause has been identified. We'll be pushing out a fix very soon.

3. monitoring 2025-08-19 14:47 UTC

   A fix is currently being deployed, and we're monitoring its rollout and its impact on fixing this issue.

4. resolved 2025-08-19 15:01 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Porter's status page.

Affected: Porter API, GitHub Actions

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-08-07 06:25 UTC

   We're seeing degraded performance with the Porter CLI installer(https://install.porter.run), and we've identified rate-limiting issues with the upstream Github API as the cause. A fix has been deployed, and we're monitoring the lifting of the rate limits in the next few minutes.

2. monitoring 2025-08-07 06:34 UTC

   The Porter CLI installer is back online, and we're monitoring for any residual issues over the next few minutes.

3. resolved 2025-08-07 06:38 UTC

   This incident has been resolved. A post-mortem will be available here shortly.

Excerpts are shortened. Read the full incident on Porter's status page.

Affected: Porter API

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-25 11:34 UTC

   We are currently investigating an issue where app deployments are not going through. Existing apps and workloads are not affected.

2. investigating 2025-06-25 11:49 UTC

   We are continuing to investigate this.

3. identified 2025-06-25 12:16 UTC

   The issue has been identified and a potential fix will be rolled out ASAP.

4. identified 2025-06-25 12:51 UTC

   We are rolling out a fix for this issue, and we hope to have it resolved soon.

5. monitoring 2025-06-25 13:11 UTC

   A fix has been rolled out, and we're currently monitoring to check for any issues.

6. resolved 2025-06-25 13:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Porter's status page.

Affected: Porter UI, Porter API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-03-12 05:45 UTC

   We're investigating failures with deployments on customer workloads, and our chart/app template repositories.

2. identified 2025-03-12 07:04 UTC

   The issue has been identified as a problem with an upstream DNS provider. A fix is currently being worked on, and we hope to have this resolved ASAP.

3. identified 2025-03-12 07:49 UTC

   We're continuing to work on fixing this, and are in touch with the upstream DNS provider to help resolve this speedily.

4. identified 2025-03-12 10:18 UTC

   We are rolling out a fix for this at the moment, and we'll be able to resume deployments across the board soon.

5. monitoring 2025-03-12 11:16 UTC

   We're deploying a fix for this, and are monitoring its rollout. Any failed deployments can be re-run via Github Actions or the Porter dashboard.

6. resolved 2025-03-12 11:40 UTC

   This incident has now been resolved. User workload deployments are proceeding normally; any failed deployments can be re-run via Github Actions or the Porter dashboard. A detailed RCA is included below. This RCA addresses the downtime our platform faced on the 12th of March...

7. postmortem 2025-03-17 12:10 UTC

   ``` This RCA addresses the downtime our platform faced on the 12th of March 2025, specifically with deployments to user workloads. Some context - earlier, Porter's dashboard and build/deployment endpoints were on https://dashboard.getporter.dev. Around May 2024, we migrated over...

Excerpts are shortened. Read the full incident on Porter's status page.

Affected: Porter UI, Porter API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-03-03 17:20 UTC

   Our 3rd party auth provider is having an issue, therefore our dashboard is unavailable at this time. Once this issue has been resolved on their end, re-triggering any CI failures will cause your changes to go through again.

2. identified 2025-03-03 17:21 UTC

   The 3rd party org is now aware of the issue and has been in contact with Porter. You can see their updates here: https://status.workos.com

3. identified 2025-03-03 17:30 UTC

   Some users are reporting partial return of service. We will continue monitoring and working with the provider.

4. monitoring 2025-03-03 17:30 UTC

   Some users are reporting partial return of service. We will continue monitoring and working with the provider.

5. resolved 2025-03-03 20:59 UTC

   Issue has not occurred in 90 minutes.

Excerpts are shortened. Read the full incident on Porter's status page.

Affected: Porter UI, Porter API, Porter Infrastructure Manager, Porter DNS

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-10-02 12:02 UTC

   The Porter dashboard and API are currently offline - we're investigating the issue and rolling out a fix.

2. investigating 2024-10-02 12:03 UTC

   A fix is being deployed and the dashboard + API will be back up in a few minutes.

3. monitoring 2024-10-02 12:04 UTC

   The fix has being deployed. The dashboard and API are back up, and we're monitoring all systems.

4. resolved 2024-10-02 12:07 UTC

   This incident has now been fully resolved. A postmortem will follow shortly.

5. postmortem 2024-10-02 12:08 UTC

   This post-mortem deals with a recent outage on the Porter platform on the 2nd of October 2024, which rendered the platform inaccessible for users. This incident did not affect user workloads, and only affected our users' ability to access the Porter dashboard as well as run...

Excerpts are shortened. Read the full incident on Porter's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-09-30 19:00 UTC

   We are investigating an infrastructure issue that is causing the Porter dashboard to be unresponsive. User workloads should be unaffected. We will update as the situation evolves.

2. postmortem 2024-09-30 19:32 UTC

   2:50pm EST: Service down ~2:55pm EST: Cause identified as storage limits on production database; storage increased 3:06pm EST: Initial service restoration. Users may see additional latency on the dashboard. 3:23pm EST: Full service restored. ‌ As a reminder, outages to the...

Excerpts are shortened. Read the full incident on Porter's status page.

Affected: Porter UI, Porter API, Porter Infrastructure Manager

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2023-04-18 17:11 UTC

   The Porter platform is currently down. We have identified the issue and are rolling out a fix at the moment.

2. monitoring 2023-04-18 17:13 UTC

   We are continuing to monitor for any further issues.

3. monitoring 2023-04-18 17:16 UTC

   The platform is back up, and all systems are functional.

4. resolved 2023-04-18 17:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Porter's status page.

Affected: Porter UI, Porter API

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2023-04-17 11:39 UTC

   We've identified an issue where customers may have trouble loading their current application and job workloads on the Porter dashboard. Actual applications and jobs on customer clusters are unaffected. We're working on a fix for this problem.

2. identified 2023-04-17 13:33 UTC

   We've created a fix for this issue, and will commence deploying it to our platform very shortly.

3. monitoring 2023-04-17 13:45 UTC

   A fix for this issue is being rolled out into our platform, and we're closely monitoring the deployment.

4. resolved 2023-04-17 14:21 UTC

   This incident has been resolved; application and job views are now running normally on the dashboard.

Excerpts are shortened. Read the full incident on Porter's status page.

Affected: Porter DNS

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2022-08-05 05:46 UTC

   We're facing elevated domain record lookup times with our DNS service. The root cause has been identified and a fix will be rolled out shortly.

2. monitoring 2022-08-05 05:47 UTC

   A fix has been implemented and our DNS systems are being closely monitored.

3. resolved 2022-08-05 05:48 UTC

   This incident has been resolved, and DNS lookups are being resolved normally. A detailed post-mortem analysis will be provided in a few hours.

Excerpts are shortened. Read the full incident on Porter's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2022-08-04 09:30 UTC

   An outage on Porter's infrastructure resulted in the Porter UI and API being available.

Excerpts are shortened. Read the full incident on Porter's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2022-08-03 10:28 UTC

   Let your users know once a fix is in place, and keep communication clear and precise.

2. identified 2022-08-03 10:34 UTC

   As you continue to work through the incident, update your customers frequently.

3. resolved 2022-08-03 10:38 UTC

   Empathize with those affected and let them know everything is operating as normal.

4. investigating 2022-08-03 11:04 UTC

   When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.

Excerpts are shortened. Read the full incident on Porter's status page.