You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
And if you're doing more than one thing you're better off with a single large server rather than multiple small instances, plus unless you're all-in on containers/"let other people configure my stuff" (which only works for a subset of things) it means more boxes to admin.
If you need better reliability in case of hardware failure, and you know what you're doing, you're still better off just renting two servers and doing DRBD and floating an IP or something like that, depending on what services you run.
Heck even at three servers and a Pacemaker cluster (so you can do quorum) you're still doing it cheaper, and then you get some experience with HA platforms :-) (of course, that also takes more time to set up and admin)
Also, with unlimited bandwidth, you don't need to worry about "oops, my backups failed and ran in a loop / someone DoSed me / I got redditted / someone pointed their Docker at an image I host for their entire cluster" and suddenly you have a $1k bill.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
