Open vincenthuynh opened 8 years ago
If executing the API calls directly doesn't cause a problem, if the problem exists at the vagrant level, then there's not much that Phil or I can to to help.
The calls appear to be timeout issues which could be a problem at our end, but it could also very well be a problem anywhere in the network between you client and our servers.
At about 22:00 EST, the timeout issues look to have been resolved upstream and we have been able to provision using vagrant again.
@SLsthompson: Do you know if there was an upgrade happening yesterday based on the timing that might explain this?
Thanks, Vincent-
I do not know. I'm not directly tied into the release schedules for the main system.
Hello,
Is anyone else experiencing issues provisioning as of 18:00 EST today? We have not been able to provision or destroy instances since this began. The errors we're encountering are as follows:
Other errors we're also seeing:
Executing API calls directly seem to be working fine.
Paging...@SLsthompson, @underscorephil
Thanks! Vincent-