HTTPError Could not fetch specs #3437 solved

1 min read

HTTP Error started  error about an hour ago Could not fetch specs #3437 solved when trying to deploy to production. This issue is really kicked off and it irritates. The solution which is available on web may not really have fixed it although an established engineering team says they are aware.

According to various people on Twitter, this outage is caused by Digital Ocean –

“Our engineering team is aware of connectivity issues in the SFO2 region, and we are actively working towards a resolution. During this time you may experience slow, or no connection to your droplets. We will provide an update soon.” – 2017-04-11 07:00:01 UTC.

Read also The webpage might be temporarily down – Namecheap Error resolved

Leave a Reply

Your email address will not be published.

Latest from Uncategorized