This should now be addressed by our new release (v0.1.3) – it was due to rate-limiting by one of our providers related to authentication which we’ve now fixed. Let us know if you continue to see any behaviour like this. Thanks all for helping us reproduce and fix this one!