That being said, maybe check if you have `dhclient`, `dhcpcd`, `systemd-resolved`, or (less likely) `dnsmasq` or `bind` running (htop / ps aux).
If you do, your instance may fall over after its DHCP lease expires and it then presumably fails to acquire a new one and goes all 169.254.x.x on you.
The possible counterpoint / information-vacuum bit here is that I don't know what the DHCP lease time is, so the expiry may already have happened.
IOW, apparently this started 4h ago, and so the last leases were presumably issued 4h ago, and maybe the lease length is 1h, so everything's already as dead as it's going to get, so maybe if you're not already dead, you're fine.
If you do, your instance may fall over after its DHCP lease expires and it then presumably fails to acquire a new one and goes all 169.254.x.x on you.
The possible counterpoint / information-vacuum bit here is that I don't know what the DHCP lease time is, so the expiry may already have happened.
IOW, apparently this started 4h ago, and so the last leases were presumably issued 4h ago, and maybe the lease length is 1h, so everything's already as dead as it's going to get, so maybe if you're not already dead, you're fine.