Porter Outage History

Porter is up right now

Porter had 3 outages in the last 2 years totaling 2h 1m of downtime — averaging 0.1 incidents per month.

There were 3 Porter outages since March 9, 2026 totaling 2h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.porter.run

Minor September 9, 2026

Authentication issues

Detected by Pingoru
Sep 09, 2026, 10:12 PM UTC
Resolved
Sep 09, 2026, 10:37 PM UTC
Duration
24m
Affected: Porter Dashboard + API
Timeline · 3 updates
  1. investigating Sep 09, 2026, 10:12 PM UTC

    We're currently experiencing increased authentication failures with the Porter dashboard and the CLI. We're investigating this, and will share more information as it becomes available.

  2. monitoring Sep 09, 2026, 10:31 PM UTC

    Our upstream authentication provider has identified the issue and is working on a fix.

  3. resolved Sep 09, 2026, 10:37 PM UTC

    Authentication is working again through the dashboard and CLI.

Read the full incident report →

Major August 28, 2026

Issue with Porter deployments

Detected by Pingoru
Aug 28, 2026, 12:00 AM UTC
Resolved
Aug 28, 2026, 01:15 AM UTC
Duration
1h 15m
Affected: Porter Dashboard + API
Timeline · 2 updates
  1. identified Aug 28, 2026, 12:00 AM UTC

    App deployments for AWS clusters are failing due to an authentication issue with ECR registries The issue has been identified and a fix is being rolled out

  2. resolved Aug 28, 2026, 01:15 AM UTC

    The fix has been rolled out and app deployments should be working again. Retrying any failed GitHub Actions runs should succeed

Read the full incident report →

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 →