Render Status

Resolved: This incident has been resolved.

Monitoring: This issue has been mitigated.

Identified: We are seeing increased rates of 404s for valid URLs on services hosted in Oregon, including Static Sites, we are working on resolving this issue.

Resolved: This incident has been resolved. Impact to any services was mitigated as of 20:36.

Monitoring: We've identified that builds for services other than static sites were also affected. We continue to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are investigating static sites failing to build in the Oregon and Virginia regions.

Resolved: This incident has been resolved.

Monitoring: This issue has been mitigated.

Identified: We are seeing increased rates of 404s for valid URLs on services hosted in Oregon, including Static Sites, we are working on resolving this issue.

Resolved: This incident has been resolved. Impact to any services was mitigated as of 20:36.

Monitoring: We've identified that builds for services other than static sites were also affected. We continue to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are investigating static sites failing to build in the Oregon and Virginia regions.

Resolved: This incident has been resolved.

Monitoring: We’ve rolled out a mitigation that’s successfully cleared up all the 502s tied to this specific incident. Things are looking stable so far, but we’re still monitoring and working on a more permanent fix.

Identified: We’re still working on a fix and starting to see some improvements from the mitigation steps we’ve taken. We're now focusing on putting a more solid, permanent solution in place and will update this status page as soon as we’ve got more to share.

Identified: We have identified the issue and are currently working on mitigating and fixing it.

Investigating: We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Investigating: We’re still actively looking into it. So far, it seems like this is primarily affecting some newly created services in the Frankfurt region.

Investigating: Some services — mostly in the Frankfurt region — have been reported to return 502s on certain requests. It’s not hitting all services, and we can’t confirm yet if it’s limited to just one region.

We’re on it and investigating.

Resolved: We've seen no further symptoms of network congestion in this region.

Monitoring: Our upstream provider has allocated more network capacity in the congested region.

Identified: We've received confirmation from an upstream provider that they have been experiencing networking congestion in this region during these periods of impact. They are now working on a remediation.

Investigating: Despite increased networking resource allocation, we've see another instance of this issue. We're now collaborating with upstream providers to identify the source of these transient networking errors

Monitoring: We have not seen a reoccurrence of the issue after making changes yesterday afternoon, but are continuing to monitor as the problem seems to be intermittent.

Investigating: We are continuing to investigate while working on provisioning more networking resources and improving observability into the issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved. Impact to any services was mitigated as of 20:36.

Monitoring: We've identified that builds for services other than static sites were also affected. We continue to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are investigating static sites failing to build in the Oregon and Virginia regions.