Yeah, been running for almost a year now. 768Meg, never had any probs before. Nothing has changed.
HDD ? How long since you've dumped the debug.log? Also, keep in mind Dashninja may have it's quirks from time to time. If Elb is working the backend, some funky info may result from it.
Did you try list | grep xx.xx.xx.xx ?
hmmm. Is there a way to search by IP address now?? It appears you need to search by Vin (Hash-Index), now that we use "dash-cli"

Unless theres a switch somewhere??
This gives me hope..... but also a headache!
root@vultr:~/.dash# ./dash-cli masternodelist help
error: {"code":-1,"message":"masternodelist ( \"mode\" \"filter\" )\nGet a list of masternodes in different modes\n\nArguments:\n1. \"mode\" (string, optional/required to use filter, defaults = status) The mode to run list in\n2. \"filter\" (string, optional) Filter results. Partial match by IP by default in all modes,\n additional matches in some modes are also available\n\nAvailable modes:\n activeseconds - Print number of seconds masternode recognized by the network as enabled\n (since latest issued \"masternode start/start-many/start-alias\")\n addr - Print ip address associated with a masternode (can be additionally filtered, partial match)\n full - Print info in format 'status protocol pubkey IP lastseen activeseconds lastpaid'\n (can be additionally filtered, partial match)\n lastseen - Print timestamp of when a masternode was last seen on the network\n lastpaid - The last time a node was paid on the network\n protocol - Print protocol of a masternode (can be additionally filtered, exact match))\n pubkey - Print public key associated with a masternode (can be additionally filtered,\n partial match)\n rank - Print rank of a masternode based on current block\n status - Print masternode status: ENABLED / EXPIRED / VIN_SPENT / REMOVE / POS_ERROR\n (can be additionally filtered, partial match)\n"}