right now, since last 20 minutes, i can't reach my server and vdi.net !!

is it down ! :(


Traceroute
Tracing route to vdi.net [216.10.16.24]

hop rtt rtt rtt ip address fully qualified domain name
1 0 0 0 216.46.228.241 port-216-3073265-dal16509b-drtn.devices.datareturn.net
2 0 0 0 64.29.192.237 port-64-1949933-zzt0prespect.devices.datareturn.net
3 0 0 0 64.29.192.226 port-64-1949922-zzt0prespect.devices.datareturn.net
4 0 0 0 209.246.152.201 gigabitethernet3-0-101.ipcolo2.dallas1.level3.net
5 0 0 0 209.244.15.97 gigabitethernet10-2.core1.dallas1.level3.net
6 0 0 0 209.245.240.158 ggr1.dlstx.ip.att.net
7 * * *
8 30 30 30 12.122.10.90 tbr2-p013701.sl9mo.ip.att.net
9 30 30 30 12.122.9.141 tbr1-p012401.sl9mo.ip.att.net
10 * 822 250 12.122.10.65 tbr1-p012401.wswdc.ip.att.net
11 40 40 40 12.122.10.53 tbr1-p013701.n54ny.ip.att.net
12 40 40 40 12.123.214.181 gar1-p3100.nwrnj.ip.att.net
13 40 30 40 12.119.140.50
14 40 30 40 66.78.63.246 so-0-1-0-0.core-01-teb.vdi.net
15 30 30 40 66.78.63.130
16 * * *
17 * * *
18 * * *
19 * * *

I get a reply from your IP address. Perhaps it's resolved meanwhile, OR it's related to your ISP - then it's not correct to publically blame them on this board.

Carl

well it was down for sure, i traced from 3 different locations, never mind it seems up now

Originally posted by mahinder
well it was down for sure, i traced from 3 different locations, never mind it seems up now

Do you mind to post a traceroute from the same source as the first one, just for our info ?

Thx,
Carl

Originally posted by Mango


Do you mind to post a traceroute from the same source as the first one, just for our info ?

Thx,
Carl


well it was not from my isp it was from

http://centralops.net/co/DomainDossier.vbs.asp?addr_lkup=1&dom_whois=1&net_whois=1&dom_dns=1


Traceroute
Tracing route to vdi.net [216.10.16.24]

hop rtt rtt rtt ip address fully qualified domain name
1 0 0 0 216.46.228.241 port-216-3073265-dal16509b-drtn.devices.datareturn.net
2 0 0 0 64.29.192.237 port-64-1949933-zzt0prespect.devices.datareturn.net
3 0 10 0 64.29.192.226 port-64-1949922-zzt0prespect.devices.datareturn.net
4 0 0 0 209.246.152.201 gigabitethernet3-0-101.ipcolo2.dallas1.level3.net
5 0 0 0 209.244.15.97 gigabitethernet10-2.core1.dallas1.level3.net
6 0 0 0 209.245.240.158 ggr1.dlstx.ip.att.net
7 0 0 10 12.122.12.93 tbr2-p012402.dlstx.ip.att.net
8 30 30 30 12.122.10.90 tbr2-p013701.sl9mo.ip.att.net
9 30 31 30 12.122.9.141 tbr1-p012401.sl9mo.ip.att.net
10 40 30 40 12.122.10.65 tbr1-p012401.wswdc.ip.att.net
11 40 30 40 12.122.10.53 tbr1-p013701.n54ny.ip.att.net
12 40 40 40 12.123.214.181 gar1-p3100.nwrnj.ip.att.net
13 40 30 40 12.119.140.50
14 40 30 30 66.78.63.246 so-0-1-0-0.core-01-teb.vdi.net
15 40 30 30 66.78.63.130
16 * * *
17 * * *
18 * * *
19 * * *

Trace aborted






from my isp also it was inaccesable. but now its fine

here is tracert from my isp


Tracing route to vdi.net [216.10.16.24]
over a maximum of 30 hops:

1 130 ms 121 ms 120 ms lan-202-144-113-251.maa.sify.net [202.144.113.25
1]
2 120 ms 111 ms 120 ms lan-202-144-113-242.maa.sify.net [202.144.113.24
2]
3 120 ms 111 ms 120 ms lan-202-144-83-10.maa.sify.net [202.144.83.10]
4 471 ms 401 ms 390 ms 134.159.63.125
5 381 ms 380 ms 381 ms i-15-1.wil-core01.net.reach.com [202.84.251.177]

6 380 ms 371 ms 381 ms i-5-0.wil-core02.net.reach.com [202.84.251.146]

7 390 ms 381 ms 390 ms i-10-0.sjc-core01.net.reach.com [202.84.143.34]

8 381 ms 391 ms 380 ms 134.159.63.102
9 380 ms 391 ms 390 ms p6-3.core01.sjc01.atlas.cogentco.com [154.54.2.2
33]
10 400 ms 401 ms 390 ms p13-0.core01.lax01.atlas.cogentco.com [66.28.4.7
3]
11 450 ms 401 ms 400 ms p5-0.core01.san01.atlas.cogentco.com [66.28.4.78
]
12 461 ms 471 ms 470 ms p6-0.core01.iah01.atlas.cogentco.com [66.28.4.5]

13 471 ms 471 ms 471 ms p15-0.core01.tpa01.atlas.cogentco.com [66.28.4.4
6]
14 460 ms 481 ms 471 ms p5-0.core01.mco01.atlas.cogentco.com [66.28.4.14
1]
15 470 ms 471 ms 471 ms p14-0.core01.jax01.atlas.cogentco.com [66.28.4.1
54]
16 460 ms 481 ms 461 ms p5-0.core01.atl01.atlas.cogentco.com [66.28.4.13
8]
17 460 ms 471 ms 471 ms p5-0.core02.dca01.atlas.cogentco.com [66.28.4.16
2]
18 470 ms 471 ms 471 ms p6-0.core01.jfk02.atlas.cogentco.com [66.28.4.82
]
19 470 ms 481 ms 471 ms p15-0.core01.jfk01.atlas.cogentco.com [66.28.4.9
]
20 471 ms 480 ms 481 ms g50.ba01.b002894-1.jfk01.atlas.cogentco.com [66.28.65.146]
21 470 ms 461 ms 471 ms VDI.demarc.cogentco.com [66.250.4.118]
22 471 ms 470 ms 461 ms so-0-1-0-0.core-01-teb.vdi.net [66.78.63.246]
23 471 ms 470 ms 481 ms 66.78.63.138
24 471 ms 481 ms 470 ms www.vdi.net [216.10.16.24]

Trace complete.

well, it went down again for few moments and then came up, I guess its not vdi fault, might be cogent is doing some maintenance here


C:\>tracert vdi.net

Tracing route to vdi.net [216.10.16.24]
over a maximum of 30 hops:

1 180 ms 120 ms 120 ms lan-202-144-113-251.maa.sify.net [202.144.113.25
1]
2 110 ms 120 ms 120 ms lan-202-144-113-242.maa.sify.net [202.144.113.24
2]
3 111 ms 120 ms 110 ms lan-202-144-83-10.maa.sify.net [202.144.83.10]
4 381 ms 380 ms 381 ms 134.159.63.125
5 451 ms 380 ms 381 ms i-15-1.wil-core01.net.reach.com [202.84.251.177]

6 370 ms 381 ms 380 ms i-5-0.wil-core02.net.reach.com [202.84.251.146]

7 391 ms 390 ms 381 ms i-10-0.sjc-core01.net.reach.com [202.84.143.34]

8 400 ms 381 ms 390 ms 134.159.63.102
9 451 ms 391 ms 390 ms p6-3.core01.sjc01.atlas.cogentco.com [154.54.2.2
33]
10 381 ms 380 ms 381 ms p4-0.core01.sfo01.atlas.cogentco.com [66.28.4.93
]
11 p15-0.core02.sfo01.atlas.cogentco.com [66.28.4.70] reports: Destination ho
st unreachable.

Trace complete.

the downtime was due to ATT's network being screwed up for several hours last night, not VID's fault directly though they should have a backup to route the traffic over.