Make sure your infrastructure is ready to weather such storms - have local backups and fallbacks, make sure your code is available even if github (or the Internet) goes down.
The more I hear 'cloud', the more I try to depend only on tools that work offline.
If you are connecting different services (message queues, databases, storage, transcoding), and spinning up and down instances based on current demand and spot prices, then cloud hosting is totally different. On the other hand, if you are just renting a couple of dedicated cloud instances, then yeah - they're just (virtualized) servers.
(Because yeah, if I host a Dropbox clone on my Raspberry Pi sitting on the wardrobe, I have my files "in the cloud" now.)
We need a new word for automated, dynamic allocation/deallocation/management of remote instances for various services. Something that would differentiate it from buying a VPS.
I guess it's frustrating that cloud means quite different things depending on the context, but I guess that's true of a lot of language.
It's the cloud-based offline tool storage platform that gives you access to your offline tools...from the cloud!!