I just resized a 1024 to a 2048 and immediately after the resize, I cannot connect to the server. Running mtr --report via lish on the box never gets out. Running mrt --report from the house gets all the way to linode internal routers. The last I heard from them, it was something outside their network. I feel like I'm the only one not on crack. Am I missing something?

from the house:
Start: Sun May 31 13:28:08 2015
HOST: Michaels-Air.home Loss% Snt Last Avg Best Wrst StDev
1.|-- wireless_broadband_router 0.0% 10 1.5 8.1 1.2 65.4 20.1
2.|-- l100.lsanca-vfttp-99.veri 0.0% 10 3.7 8.8 3.0 41.6 11.9
3.|-- g102-0-0-0.lsanca-lcr-21. 0.0% 10 8.7 9.8 6.8 18.9 3.4
4.|-- ae1-0.lax01-bb-rtr1.veriz 0.0% 10 62.2 23.6 6.5 62.2 20.3
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 0.ae5.br1.lax15.alter.net 0.0% 10 9.3 10.5 9.3 13.0 1.1
7.|-- ae6.edge1.losangeles9.lev 0.0% 10 9.4 14.3 7.7 52.3 13.6
8.|-- ae-4-90.edge5.dallas3.lev 70.0% 10 39.9 48.8 38.0 68.6 17.2
9.|-- ae-4-90.edge5.dallas3.lev 60.0% 10 38.4 37.9 37.3 38.4 0.0
10.|-- ae4-bbr01.eq01.dal03.netw 0.0% 10 57.4 41.6 38.7 57.4 5.6
11.|-- po31.dsr02.dllstx3.networ 0.0% 10 40.4 40.9 39.4 47.0 2.1
12.|-- po31.dsr01.dllstx2.networ 0.0% 10 40.3 41.5 40.3 44.5 1.1
13.|-- po1.car01.dllstx2.network 0.0% 10 37.5 43.0 36.8 68.8 11.2
14.|-- router1-dal.linode.com 0.0% 10 41.6 42.2 41.3 44.9 0.9
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

from the box:
Start: Sun May 31 12:59:11 2015
HOST: elisha Loss% Snt Last Avg Best Wrst StDev

The first time I ran traceroute, everything stopped after going through a series of linode routers. I just ran it again and it is hanging outside. That will teach me to upgrade.

1 wireless_broadband_router (192.168.1.1) 3.569 ms 1.201 ms 1.106 ms
2 l100.lsanca-vfttp-99.verizon-gni.net (98.112.16.1) 2.571 ms 2.870 ms 2.395 ms
3 g102-0-0-0.lsanca-lcr-21.verizon-gni.net (100.41.132.0) 7.480 ms 7.415 ms 7.868 ms
4 * ae2-0.lax01-bb-rtr1.verizon-gni.net (130.81.209.254) 7.994 ms 7.177 ms
5 * 0.ae5.br1.lax15.alter.net (140.222.225.135) 9.005 ms *
6 ae6.edge1.losangeles9.level3.net (4.68.62.169) 7.109 ms
0.ae5.br1.lax15.alter.net (140.222.225.135) 11.985 ms 8.564 ms
7 * ae-4-90.edge5.dallas3.level3.net (4.69.145.209) 39.126 ms
ae-2-70.edge5.dallas3.level3.net (4.69.145.78) 37.182 ms
8 ae-4-90.edge5.dallas3.level3.net (4.69.145.209) 38.693 ms *
ae-2-70.edge5.dallas3.level3.net (4.69.145.78) 36.144 ms
9 ae4-bbr01.eq01.dal03.networklayer.com (4.59.32.38) 38.585 ms 39.723 ms 37.010 ms
10 po31.dsr02.dllstx3.networklayer.com (173.192.18.227) 41.152 ms
ae4-bbr01.eq01.dal03.networklayer.com (4.59.32.38) 36.889 ms 38.436 ms
11 po31.dsr02.dllstx3.networklayer.com (173.192.18.227) 40.474 ms 40.331 ms
po32.dsr02.dllstx2.networklayer.com (70.87.255.70) 39.171 ms
12 po2.car02.dllstx2.networklayer.com (70.87.254.86) 37.944 ms
po1.car02.dllstx2.networklayer.com (70.87.254.82) 37.113 ms
po32.dsr02.dllstx2.networklayer.com (70.87.255.70) 38.635 ms
13 po1.car01.dllstx2.networklayer.com (70.87.254.74) 36.403 ms * 40.367 ms
14 * *

I don't know if there's any clear documentation about this, but apparently Linode is phasing out DHCP for IP address assignments in favor of Network Helper. It's possible your Linode is not acquiring an IP address due to some weird interaction after the resize. If you put in a support ticket you should get a more direct response.