I don't think many users will be affected by dhcp outage. Most linodes have fixed IPs.
Mine don't seem to be affected
Mine don't seem to be affected
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.
We run some Windows instances, which were DHCP out of laziness. <facepalm> [edit: It's a PITA to fire up a Windows instance on Linode. Once working, switching out of DHCP is near the bottom of the todo list.]
I would expect the opposite. Doesn't DHCP make more sense, for example, if the user creates a snapshot and restores it with a new IP? I don't use Lenode, so I can't judge, but I would expect DHCP to be default.
I learned this because I wanted to test image recovery of deleted linode. When I restored it, I got a different IP address from linode (the static IP assigned to me), and I couldn't connect to it. Using the web console I found the IP address was hard coded to the old one still.
The IP lease never changes but it's assigned by DHCP - check your settings (mine was in /etc/netplan/01-netcfg.yaml
dhcp4: yes