Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hey Drew - First thing I would do is check this suggestion from the plugin author:
Can you try playing with the setting on the options page that says “How Wordfence gets IPs”? Select the option that best fits your hosting environment. If you are unsure you can select one after the other, saving in between, and check live traffic for real ip addresses to see which one fixes it. https://wordpress.org/support/topic/all-hits-from-same-ip-after-hosting-upgrade
If that doesn’t work, can you describe how your Wordpress is setup? Is it on a server with Apache or nginx? Are you running Wordpress behind a reverse proxy (where nginx or apache forwards all traffic through to a separate port) - this would cause you to see your own droplet’s IP, but it can be fixed. Do you have a service like cloudflare setup in front of wordpress - This can also be fixed