Cloud Functions Incident #18033
Many GCF builds fail on Node 8; some on Node 6, due to NPM Registry outage
Incident began at 2018-09-01 04:56 and ended at 2018-09-01 11:44 (all times are US/Pacific).
|Sep 01, 2018||11:56||
We've been stable for the past hours. No further re-occurrences of the cert issue. You can also check: https://status.npmjs.org/. Thank you for your patience and let us know if you're still having issues through our support page.
|Sep 01, 2018||09:20||
The incident seems to be over. No certificate errors observed in the last 20 minutes. Overall deploy failure rate is back to its typical background (2-3%), and the failures seem to be genuine user errors. We'll post another update in the next few hours.
|Sep 01, 2018||08:35||
There are some signs of improvement, indicating that DNS caches are picking up the correct config. Deployment error rate has dropped to 10%. That said, logs indicate that the problem still actively affects some builds. We'll keep you posted for any updates.
|Sep 01, 2018||05:41||
We are experiencing an issue with Google Cloud Functions. Due to DNS misconfiguration in NPM Registry cached in ISP DNS caches, Cloud Functions is unable to fetch dependent modules declared in the package.json file. Current investigation indicates that approximately 10-20% of requests are affected by this issue. The issue is tracked by NPM at https://status.npmjs.org/. Impact is expected to last for up to 24 hours as DNS caches get refreshed globally. For everyone who is affected, we apologize for the disruption. We will provide an update by Saturday, 2018-09-01 09:30 US/Pacific with current details.