A question can only have one accepted answer. Are you sure you want to replace the current answer with this one?
You previously marked this answer as accepted. Are you sure you want to unaccept it?
Write for DigitalOcean
You get paid, we donate to tech non-profits.
Find and meet other developers in your city.
Contribute to Open Source
make a online chat why wont this verify its been 3 hours
Add comments here to get more clarity or context around a question. To answer a question, use the “Answer” field below.
Can Someone help me
Hi! I wonder what your policy is with regard to incoming DDoS network attacks?
* Will you try to filter the traffic based on heuristics, or just null route the affected dest IP(s)?
* What happens to my network traffic bill when somebody launches a DNS amplication attack against my VPS?
Could you please give some more detail about what is going on regarding this message when trying to setup a 512MB instance in the Amsterdam region?
"The 512MB and 1GB sizes are currently not available in the Amsterdam region due to RIPE IPv4 restrictions and limited availability of IP space."
Is this temporary or permanent?
So, hardware fails every once in a while. What is the DO best practice for handling this?
At the moment I can only see:
1) Set up a distributed filesystem across multiple DO nodes, ie Gluster (means high latency for writes)
2) Use DNS round robin and/or failover. Problems with browser and proxy caching.
But perhaps in the near future you will support:
* Floating ip
* Floating VM images
Any other options?
I think DigitalOcean should charge the plan fee once or offer a yearly fee as well so that we can pay immediately and move on with the project. It seems scary when we think of having insufficient balance on the card the day when we are being charged. one lump sum payment (monthly / yearly) is good enough and then the extra payment (of over usage) can be paid at the end of the plan or adjusted the next month. I think that would be a good option.