Time: Sept. 6, 2024, 1:33 a.m.

Status: Resolved

Update: This incident has been resolved.

Time: Sept. 5, 2024, 11:58 p.m.

Status: Monitoring

Update: The fix has been implemented and deployed. We are now observing successful clones, assuming that the issue has been resolved.

Time: Sept. 5, 2024, 11:19 p.m.

Status: Identified

Update: We have identified the issue and are actively taking steps to resolve it. We will issue further updates within the next 30 minutes or as new information becomes available.

Time: Sept. 5, 2024, 10:49 p.m.

Status: Identified

Update: We have identified the issue and are currently taking preliminary steps to resolve it. We will provide further updates in 30 minutes or as additional information becomes available.

Time: Sept. 5, 2024, 10:19 p.m.

Status: Identified

Update: We are currently investigating reports of 404 errors when accessing static file assets after a clone. Affected sites may experience these errors in the destination environment following the successful cloning of files between environments. Our engineering team is aware of the issue and is actively working on a resolution. If you encounter this issue, please reach out to support for assistance. We will provide further updates in 30 minutes or as more information becomes available.

Time: Aug. 28, 2024, 6:35 p.m.

Status: Resolved

Update: This incident has been resolved, but if you encounter any further issues, please don’t hesitate to contact our support team. We appreciate your patience and understanding.

Time: Aug. 28, 2024, 5:51 p.m.

Status: Monitoring

Update: We are actively monitoring the situation to ensure everything continues to run smoothly. We will provide updates and share any significant developments as they occur. Should you encounter any further issues, please do not hesitate to contact our support team. We appreciate your patience and understanding.

Time: Aug. 28, 2024, 11:59 a.m.

Status: Monitoring

Update: We're continuing to monitor the situation to ensure everything is running smoothly. We'll keep you updated and share any important developments as they arise.

Time: Aug. 28, 2024, 9:01 a.m.

Status: Monitoring

Update: We are closely monitoring the situation to ensure everything remains stable. We'll keep you informed and will share another update within the next few hours.

Time: Aug. 28, 2024, 6:56 a.m.

Status: Monitoring

Update: We are continuing to monitor for any further issues and will provide another update in the next few hours.

Time: Aug. 28, 2024, 5:09 a.m.

Status: Monitoring

Update: Our systems are currently stable, but we remain vigilant and are actively monitoring for any potential issues.

Time: Aug. 28, 2024, 1:50 a.m.

Status: Monitoring

Update: We are closely monitoring the situation and addressing issues with customer sites as they arise. Once all sites have been fully remediated, we will provide an update. Please know that our team is dedicated to resolving this, and we’re here to support you throughout the process. If you encounter any additional issues, please reach out to our support team. We’re here to help. Thank you for your continued patience.

Time: Aug. 27, 2024, 11:18 p.m.

Status: Monitoring

Update: We are actively monitoring the situation for any further issues. We are continuing to remediate issues with customer sites as they emerge and will announce when remediation for all sites is complete. Please rest assured that our team is fully committed to resolving this, and we’re here to support you every step of the way. If you experience any further issues, don’t hesitate to reach out to our support team—we’re here for you. Thank you for your patience.

Time: Aug. 27, 2024, 8:42 p.m.

Status: Monitoring

Update: We are continuing to monitor for any further issues.

Time: Aug. 27, 2024, 7:22 p.m.

Status: Monitoring

Update: We are actively monitoring the situation, and our systems are indicating a stable status. We will provide another update in the next 30 minutes to 1 hour, or sooner if new information becomes available.

Time: Aug. 27, 2024, 4:43 p.m.

Status: Monitoring

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

Time: Aug. 27, 2024, 1:57 p.m.

Status: Identified

Update: We've resolved the majority of impacted sites and are continuing to address any new ones as they come up. We're working diligently to resolve the issue as quickly as possible.

Time: Aug. 27, 2024, 10:31 a.m.

Status: Identified

Update: We are diligently addressing the issues affecting the impacted sites and will continue to provide timely updates as we make progress.

Time: Aug. 27, 2024, 8:11 a.m.

Status: Identified

Update: We are continuing our work to resolve the remaining affected sites and will share updates within the next few hours.

Time: Aug. 27, 2024, 6:06 a.m.

Status: Identified

Update: We are continuing our efforts to remediate the remaining affected sites and will provide updates within the next few hours.

Time: Aug. 27, 2024, 4:48 a.m.

Status: Identified

Update: We are actively working on remediating all affected sites and will provide updates as progress is made.

Time: Aug. 27, 2024, 1:22 a.m.

Status: Identified

Update: We are seeing elevated 504 errors on customer sites in different regions. Our engineering team is aware of the issue and is actively working on a resolution. We are committed to resolving the situation as quickly as possible and will keep you updated as we make progress.

Time: Aug. 27, 2024, 12:01 a.m.

Status: Identified

Update: We are continuing to work on a fix for this issue.

Time: Aug. 26, 2024, 10:23 p.m.

Status: Identified

Update: The issue remains identified, and our engineering teams are now manually applying the necessary fixes to the affected resources. We are working diligently to resolve the situation and will provide further updates as progress is made.

Time: Aug. 26, 2024, 9:31 p.m.

Status: Monitoring

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

Time: Aug. 26, 2024, 9:17 p.m.

Status: Identified

Update: The issue has been identified, and preliminary steps are being made for resolution.

Time: Aug. 26, 2024, 8:26 p.m.

Status: Investigating

Update: Our internal team has identified workflow errors affecting several sites in the North America (Canada) region. We are actively investigating this with the highest priority and will provide updates as soon as we have more information.

Time: Aug. 26, 2024, 4:36 p.m.

Status: Resolved

Update: We apologize for the inconvenience, this incident has been resolved.

Time: Aug. 26, 2024, 3:36 p.m.

Status: Monitoring

Update: The issue has been identified, preliminary steps are made for resolution, and we are monitoring the results.

Time: Aug. 26, 2024, 3:20 p.m.

Status: Investigating

Update: Internal monitoring has detected elevated site availability issues for some sites in our NA (Canada) region. There are also elevated workflow errors on the platform. We are actively investigating this at the highest priority and will update as soon as we have more information.

Time: July 16, 2024, 12:13 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: July 16, 2024, 5:51 a.m.

Status: Monitoring

Update: A fix has been implemented and we are continuing to monitor the result for another 6 hours.

Time: July 15, 2024, 10:52 p.m.

Status: Investigating

Update: Our Engineering team is actively working on identifying the cause of this issue. If you encounter any SFTP-related problems with your sites, please contact Support for assistance. We will provide updates in around 6 hours or as soon as we have more information available.

Time: July 15, 2024, 1:34 p.m.

Status: Investigating

Update: We are actively investigating the issue and will provide an update within the next 6 hours, or sooner if more information becomes available. For immediate assistance, please reach out to our support team via chat. We appreciate your patience and understanding.

Time: July 15, 2024, 7:33 a.m.

Status: Investigating

Update: We are currently investigating the issue and will provide an update within the next 6 hours or sooner as soon as more information becomes available. For urgent assistance, please reach out to support via chat.

Time: July 15, 2024, 1:44 a.m.

Status: Investigating

Update: Our team is actively investigating the issue. We will update you within the next 6 hours or as soon as we have more information. For urgent matters, please contact support via chat.

Time: July 14, 2024, 7:53 p.m.

Status: Investigating

Update: Our dedicated team of Engineers are continuing to investigate this issue. We'll provide an update within the next 6 hours, or as soon as we have more details. For urgent issues, please contact support by opening a support chat.

Time: July 14, 2024, 1:32 p.m.

Status: Investigating

Update: Our team of dedicated engineers is diligently investigating the issue. We aim to provide an update within the next 6 hours. Should you require immediate assistance, please initiate a support chat with our team.

Time: July 14, 2024, 7:34 a.m.

Status: Investigating

Update: Our team of dedicated engineers is actively investigating this issue. We will provide an update within the next 6 hours. For immediate assistance, please open a support chat with our support team.

Time: July 14, 2024, 1:32 a.m.

Status: Investigating

Update: Our dedicated team of Engineers are continuing to investigate this issue. We'll provide an update within the next 6 hours, or as soon as we have more details. For urgent issues, please contact support by opening a support chat.

Time: July 13, 2024, 7:30 p.m.

Status: Investigating

Update: We have detected elevated reports for the Dashboard related to SFTP development mode. These may manifest as the dashboard not reflecting changes when updating code via SFTP. While we are investigating the issue, we recommend using Terminus env:commit as a workaround: https://docs.pantheon.io/terminus/commands/env-commit If using Terminus is not possible, you may use Git mode to commit the code, otherwise please reach out to support.

Time: July 13, 2024, 12:53 a.m.

Status: Postmortem

Update: On July 8th, 2024 at 18:30 UTC, Pantheon Engineering received reports that customers trying to visit their websites encountered a "Connection Failure" message. This was caused by infrastructure issues with Pantheon’s CDN provider due to an unusually high number of simultaneous deployments. This affected customers who were trying to access sites through the CDN’s Newark, New Jersey POP \(Point of Presence\). During the incident, the sites remained available and accessible through all other PoPs. Maintaining site availability is Pantheon’s top-most priority, and we remain committed to sustaining the trust you demonstrated when choosing Pantheon. We apologize for the impact caused to our customers. We are taking measures to improve our monitoring and alerting of similar issues in the future and remain committed to providing reliable and secure hosting services.

Time: July 8, 2024, 7:52 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: July 8, 2024, 7:23 p.m.

Status: Investigating

Update: We have been alerted to issues with sites showing "Connection Failure" which is isolated to traffic flowing through our CDN partner’s Newark, NJ, data center. Affected environments should see a "Connection Failure" when accessing their sites. If you need immediate assistance, please open a support chat or submit a ticket with our support team. Thank you for your patience!