Companies/Travis CI/Incidents

Travis CI: Delayed builds and network timeouts on Linux container infrastructure for private repositories

Timeline of updates

1. resolved2015-07-20 20:34 UTC

   At this time we've worked through the backlog due to the additional capacity we added. Our preliminary investigation into the network timeouts did not lead us to any direct conclusions at this time, but in investigating we did realize that our NAT instance sizing for this environment does need to be increased to match our public Container build environment, and so we suspect that the spike in builds which caused build delays also resulted in our NAT instance being overloaded. As an initial step to help prevent our NAT instance for this environment from being overloaded like this again, we will be scheduling planned maintenance soon to upgrade the NAT instance, and we're working on identifying additional metrics and monitoring we can add to get better insight into the state and capacity of our NAT instances. Thank you for your patience during today's incident.

From Travis CI’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Impact, status and times are the vendor’s own, as last archived. View on www.traviscistatus.com (opens in new tab).

Travis CI profileRecent Travis CI incidentsAll outages on July 20, 2015Travis CI in July 2015MarkdownJSON