Traceroute from Dialtone Internet server to VDI.net server:

[pmak@sg1 pmak]$ traceroute 216.74.79.137
traceroute to 216.74.79.137 (216.74.79.137), 30 hops max, 38 byte packets
1 66.33.60.1 (66.33.60.1) 0.729 ms 1.040 ms 0.468 ms
2 s4-0-0.ar1.TPA1.gblx.net (64.209.252.61) 8.251 ms 7.844 ms 7.782 ms
3 pos5-2-155M.cr1.ATL1.gblx.net (208.178.116.33) 32.851 ms 32.762 ms 67.639 ms
4 pos0-0-0-155M.br1.ATL1.gblx.net (206.132.115.118) 32.553 ms 32.947 ms 32.807 ms
5 208.51.113.10 (208.51.113.10) 24.345 ms 25.239 ms 24.454 ms
6 lo0.mp1.Atlanta1.level3.net (209.247.8.247) 24.677 ms 24.355 ms 24.909 ms
7 so-0-0-0.mp1.Weehawken1.level3.net (209.247.8.46) 42.820 ms 42.736 ms 43.189 ms
8 loop0.hsa1.wee1.Level3.net (209.247.2.3) 43.689 ms 43.701 ms 43.192 ms
9 s1-0.core1.cftnnj.inet.vdi.net (63.211.88.6) 70.085 ms * 48.018 ms
10 vlan1.edge1.cftnnj.inet.vdi.net (216.74.127.226) 47.152 ms 46.732 ms 45.236 ms
11 * * *
12 * * *

Traceroute from my dialup connection to VDI.net server:

Tracing route to 216.74.79.137 over a maximum of 30 hops

1 2485 ms 1506 ms 1913 ms wdc2-dial4.popsite.net [64.24.80.229]
2 129 ms 126 ms 122 ms wdc2-core1.popsite.net [64.24.80.225]
3 125 ms 124 ms 123 ms wdc1-core1-p1-0.starnetusa.net [64.24.80.1]
4 123 ms 120 ms 121 ms main1-main2-ge.iad1.above.net [208.185.4.218]
5 127 ms 124 ms 123 ms core4-main1-oc48.iad1.above.net [208.185.0.153]

6 125 ms 121 ms 122 ms core1-iad1-oc48.iad2.above.net [209.249.0.214]
7 121 ms 121 ms 120 ms level3-above-oc12.iad2.above.net [209.249.0.174]

8 791 ms 1275 ms 1360 ms so-4-1-0.mp1.Washington1.level3.net [209.247.10.
69]
9 734 ms 259 ms 255 ms so-0-0-0.mp1.Weehawken1.level3.net [209.247.8.46
]
10 399 ms 378 ms 481 ms loop0.hsa1.wee1.Level3.net [209.247.2.3]
11 529 ms 569 ms 565 ms s1-0.core1.cftnnj.inet.vdi.net [63.211.88.6]
12 314 ms 361 ms 141 ms vlan1.edge1.cftnnj.inet.vdi.net [216.74.127.226]

13 135 ms 134 ms 134 ms 216.74.79.137

Trace complete.

What's going on here? Did VDI.net mess up their routers or something? It's been like this since at least yesterday evening.

We cannot get there either, but they may have just blocked our network:

root@secure [~]# /usr/sbin/traceroute vdi.net
traceroute: unknown host vdi.net
root@secure [~]# /usr/sbin/traceroute 216.10.16.24
traceroute to 216.10.16.24 (216.10.16.24), 30 hops max, 38 byte packets
1 65.164.177.1 (65.164.177.1) 0.858 ms 0.715 ms 0.671 ms
2 sl-gw27-pen-1-1-1.sprintlink.net (144.232.191.25) 22.892 ms 22.196 ms 23.841 ms
3 144.232.5.197 (144.232.5.197) 22.148 ms 21.792 ms 22.567 ms
4 sl-bb23-pen-11-0.sprintlink.net (144.232.16.196) 22.048 ms 22.228 ms 22.184 ms
5 sl-bb20-rly-12-0.sprintlink.net (144.232.9.13) 26.332 ms 24.940 ms 23.595 ms
6 144.232.18.170 (144.232.18.170) 26.486 ms 27.378 ms 26.913 ms
7 0.so-3-1-0.XR1.DCA8.ALTER.NET (152.63.35.190) 26.246 ms 27.358 ms 31.672 ms
8 0.so-3-0-0.TR1.DCA8.ALTER.NET (152.63.144.49) 26.116 ms 25.769 ms 26.445 ms
9 115.at-6-0-0.TR1.NYC8.ALTER.NET (146.188.141.186) 30.838 ms 28.922 ms 29.762 ms
10 285.at-2-0-0.XR1.NYC8.ALTER.NET (152.63.19.197) 28.589 ms 28.749 ms 29.012 ms
11 183.ATM7-0.GW3.NYC8.ALTER.NET (152.63.18.173) 28.939 ms 29.388 ms 29.025 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *


Sean R.
BurstNET