Guidewire incident
TeamCity Build Service Interruption in Non-Production Environments affecting some customers in AMER Region
Guidewire experienced a major incident on February 19, 2025 affecting Montréal and N. Virginia, lasting 2h 15m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 19, 2025, 03:06 PM UTC
Guidewire Support is aware of an issue with TeamCity builds not starting due to the unavailability of agents for some customers in the AMER region. All necessary resources are engaged to restore this service as quickly as possible. We will post regular updates on our progress.
- investigating Feb 19, 2025, 03:08 PM UTC
We are continuing to investigate this issue.
- identified Feb 19, 2025, 03:29 PM UTC
Guidewire Support has identified the cause of this incident, which is impacting TeamCity Builds not starting due to the unavailability of agents in Non-Production Environments and are actively working to restore service. We will post regular updates on our progress.
- identified Feb 19, 2025, 04:15 PM UTC
The restoration path has been identified for the affected customers and are actively working to restore service. We will post regular updates on our progress.
- monitoring Feb 19, 2025, 04:23 PM UTC
The fix has been implemented. Builds are running successfully. we are currently actively monitoring the situation.
- resolved Feb 19, 2025, 05:22 PM UTC
The affected services have been restored successfully. Please open a Community case if you are still experiencing any service interruption.
- postmortem Mar 05, 2025, 04:02 PM UTC
Please refer to the Knowledge Article via this [**link**](https://community.guidewire.com/s/article/TeamCity-Builds-have-no-Agents-to-run)[ ](https://community.guidewire.com/s/article/Integrations-were-Failing-with-Authentication-Error-with-Existing-ClientID-and-Secret)for more information.