Porter Status Page

Mar 9, 2026 · resolved Mar 9

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.

Aug 19, 2025 · resolved Aug 19

This incident has now been resolved.

Aug 7, 2025 · resolved Aug 7

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

Jun 25, 2025 · resolved Jun 25

This incident has been resolved.

Mar 12, 2025 · resolved Mar 12

``` 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 to a new domain - dashboard.porter.run - in line with our recent branding efforts and while we notified users we'd now be available on dashboard.porter.run, we also set up a DNS redirect on the older domain - getporter.dev - to ensure that people would never be in a situation where they can't access the dashboard, even with the older domain. On the 12th of March, our upstream DNS provider mistakenly detected what they felt was potentially fraudulent activity on our account, and froze our DNS zone file. This meant that any requests for dashboard.getporter.dev would fail, and unfortunately it also meant that we were locked out of our credentials, thus delaying efforts on our end to bring the domain back up. This didn't affect user workloads in any way, since user workloads run on users' infrastructure with their own domains. What this did affect, was the ability to push new deployments; since the Porter CLI and the Github Actions as well as our app chart repositories were on getporter.dev, users would have found themselves unable to deploy new changes to their existing apps. The issue was finally resolved once we were able to prove to the DNS provider that we were solely in control of our DNS zonefile, which led to the blocks being removed. We take this incident very seriously. We're an infrastructure company where we look ourselves as partners to our customers and the products they've built. To wit, we've started instituting a number of changes: 1. While we've been using Cloudflare for most of our domains, we're going to now migrate all domains - including getporter.dev - to Cloudflare. 2. In addition, we're going to migrate all our app template repos to porter.run, as well as fully deprecate getporter.dev going forward, in order to remove any potential gaps. We'd like to sincerely apologise for this incident, and we truly appreciate your patience through this. ```