Porter Outage History

Porter is up right now

Porter had 8 outages in the last 2 years totaling 13h 10m of downtime — averaging 0.3 incidents per month.

There were 8 Porter outages since September 30, 2024 totaling 13h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.porter.run

Notice March 9, 2026

Porter CLI Installer

Detected by Pingoru
Mar 09, 2026, 03:14 PM UTC
Resolved
Mar 09, 2026, 03:36 PM UTC
Duration
22m
Affected: Porter CLI Installer
Timeline · 6 updates
  1. investigating Mar 09, 2026, 03:14 PM UTC

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

  2. investigating Mar 09, 2026, 03:19 PM UTC

    We are continuing to investigate this issue.

  3. identified Mar 09, 2026, 03:22 PM UTC

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

  4. identified Mar 09, 2026, 03:23 PM UTC

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

  5. monitoring Mar 09, 2026, 03:27 PM UTC

    We're continuing to monitor our fix.

  6. resolved Mar 09, 2026, 03:36 PM 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 into how we can improve this in the future.

Read the full incident report →

Minor August 19, 2025

Issues with app activity logs

Detected by Pingoru
Aug 19, 2025, 02:04 PM UTC
Resolved
Aug 19, 2025, 03:01 PM UTC
Duration
56m
Affected: Porter UIPorter API
Timeline · 4 updates
  1. investigating Aug 19, 2025, 02:04 PM 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 Aug 19, 2025, 02:39 PM UTC

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

  3. monitoring Aug 19, 2025, 02:47 PM UTC

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

  4. resolved Aug 19, 2025, 03:01 PM UTC

    This incident has now been resolved.

Read the full incident report →

Minor August 7, 2025

Issues with app builds / CLI installation

Detected by Pingoru
Aug 07, 2025, 06:25 AM UTC
Resolved
Aug 07, 2025, 06:38 AM UTC
Duration
13m
Affected: Porter APIGitHub Actions
Timeline · 3 updates
  1. monitoring Aug 07, 2025, 06:25 AM 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 Aug 07, 2025, 06:34 AM UTC

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

  3. resolved Aug 07, 2025, 06:38 AM UTC

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

Read the full incident report →

Minor June 25, 2025

Issues with app deployments

Detected by Pingoru
Jun 25, 2025, 11:34 AM UTC
Resolved
Jun 25, 2025, 01:34 PM UTC
Duration
1h 59m
Affected: Porter API
Timeline · 6 updates
  1. investigating Jun 25, 2025, 11:34 AM UTC

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

  2. investigating Jun 25, 2025, 11:49 AM UTC

    We are continuing to investigate this.

  3. identified Jun 25, 2025, 12:16 PM UTC

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

  4. identified Jun 25, 2025, 12:51 PM UTC

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

  5. monitoring Jun 25, 2025, 01:11 PM UTC

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

  6. resolved Jun 25, 2025, 01:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 3, 2025

Auth Provider Outage

Detected by Pingoru
Mar 03, 2025, 05:20 PM UTC
Resolved
Mar 03, 2025, 08:59 PM UTC
Duration
3h 38m
Affected: Porter UIPorter API
Timeline · 5 updates
  1. identified Mar 03, 2025, 05:20 PM 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 Mar 03, 2025, 05:21 PM 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 Mar 03, 2025, 05:30 PM UTC

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

  4. monitoring Mar 03, 2025, 05:30 PM UTC

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

  5. resolved Mar 03, 2025, 08:59 PM UTC

    Issue has not occurred in 90 minutes.

Read the full incident report →

Critical September 30, 2024

Production Outage

Detected by Pingoru
Sep 30, 2024, 07:00 PM UTC
Resolved
Sep 30, 2024, 07:00 PM UTC
Duration
—
Timeline · 2 updates
  1. resolved Sep 30, 2024, 07:31 PM 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 Sep 30, 2024, 07:32 PM 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 Porter dashboard have no impact on the runtime of user workloads. If any of your CI runs failed \(e.g. Github actions\), please re-run!

Read the full incident report →