I am from Taiwan , I try to connect to Nac.net & site5.com all day ?? But it's seem down more than 8 hours ?? :angry: :angry:

I have been on off NAC servers for the past 8 hours. Neither are down.

My servers at the NAC have been reachable and we have not seen any down notification alerts. You may want to do a trace route to see where you are loosing connectivity.

All systems are up and functional on our NAC boxes. See below for a trace that finally finished up from TW to the US.

Here's a trace from a site that I finally managed to load. Between alter.net (uu.net) and level3, the route is taking a real beating. This took forever to load, both in terms of the web page and then the trace.

From http://dorm.thu.edu.tw/cgi-bin/traceroute.cgi

1 140.128.191.250 (140.128.191.250) 1.967 ms 1.341 ms 1.367 ms
2 140.128.246.6 (140.128.246.6) 3.577 ms 1.972 ms 1.379 ms
3 140.128.248.254 (140.128.248.254) 1.963 ms 1.655 ms 1.886 ms
4 203.72.38.102 (203.72.38.102) 95.187 ms 96.155 ms 102.268 ms
5 * 203.72.38.100 (203.72.38.100) ms ms ms ms
6 TANet-Internet.edu.tw (210.70.55.18) 259.443 ms 258.341 ms 254.520 ms
7 500.Serial1-5.GW7.SEA1.ALTER.NET (208.214.96.73) 273.451 ms * ms ms ms
8 146.ATM2-0.XR1.SEA1.ALTER.NET (152.63.105.178) 277.881 ms * ms ms
9 0.so-0-0-0.XL1.SEA1.ALTER.NET (152.63.106.225) 253.580 ms 265.058 ms * ms
10 0.so-0-1-0.TL1.POR3.ALTER.NET (152.63.107.149) 274.908 ms 269.974 ms 284.803 ms
11 * 0.so-1-1-0.TL1.SAC1.ALTER.NET (152.63.0.134) ms ms ms ms ms
12 0.so-7-0-0.XL1.SAC1.ALTER.NET (152.63.53.249) 294.473 ms 227.358 ms 235.285 ms
13 * POS6-0.BR5.SAC1.ALTER.NET (152.63.52.225) ms ms ms ms ms
14 * 204.255.168.186 (204.255.168.186) ms ms ms ms ms
15 so-4-1-0.mp2.SanFrancisco1.Level3.net (209.247.10.237) 291.972 ms 307.019 ms * ms
16 so-3-0-0.mp1.SanJose1.Level3.net (64.159.1.129) 285.825 ms 293.123 ms * ms
17 * * * ms ms ms
18 * * * ms ms ms
19 * ge-3-3-0.msr1.pao.yahoo.com (216.115.101.42) ms ms ms ms
20 vl20.bas1.snv.yahoo.com (216.115.100.225) 293.841 ms 489.451 ms 425.800 ms
21 img5.yahoo.com (216.115.108.245) 284.697 ms * ms ms ms

Two more. While I'm sorry that you're having this kind of trouble, I'm sure a lot of people here are pretty happy they aren't seeing things like this:

To NAC:
1 140.128.191.250 (140.128.191.250) 1.307 ms 1.401 ms 1.523 ms
2 140.128.246.6 (140.128.246.6) 1.503 ms 1.419 ms 1.839 ms
3 140.128.248.254 (140.128.248.254) 2.101 ms 1.943 ms 1.978 ms
4 203.72.38.102 (203.72.38.102) 89.239 ms 90.223 ms 90.364 ms
5 203.72.38.100 (203.72.38.100) 96.137 ms 98.083 ms 101.693 ms
6 TANet-Internet.edu.tw (210.70.55.18) 267.398 ms 265.189 ms 256.725 ms
7 500.Serial1-5.GW7.SEA1.ALTER.NET (208.214.96.73) 243.296 ms 234.164 ms 268.687 ms
8 146.ATM3-0.XR2.SEA1.ALTER.NET (152.63.105.174) 279.105 ms 298.244 ms 299.700 ms
9 294.at-0-2-0.TR2.SEA1.ALTER.NET (146.188.200.126) 233.117 ms 227.591 ms 244.115 ms
10 * * 110.at-7-1-0.TR2.NYC8.ALTER.NET ms 344.684 ms ms
11 184.ATM6-0.XR2.NYC4.ALTER.NET (152.63.21.109) 282.522 ms 313.935 ms * ms
12 * 188.ATM6-0.GW7.NYC4.ALTER.NET (152.63.25.117) ms ms ms ms ms
13 internap-gw.customer.alter.net (157.130.50.86) 251.211 ms * ms ms ms
14 * * border11.ge2-0-bbnet1.nyc.pnap.net ms 319.655 ms ms
15 * nac-1.border11.nyc.pnap.net (209.191.130.94) ms ms ms ms ms
16 a9-0-0-8.msfc1.oct.nac.net (209.123.11.85) 318.533 ms * ms ms
17 a9-0-0-8.msfc1.oct.nac.net (209.123.11.85) 336.548 ms !X ms * ms
18 * a9-0-0-8.msfc1.oct.nac.net (209.123.11.85) ms ms ms * ms
19 * * a9-0-0-8.msfc1.oct.nac.net ms 318.351 ms !X ms
20 * * a9-0-0-8.msfc1.oct.nac.net ms 324.209 ms !X ms
21 * * a9-0-0-8.msfc1.oct.nac.net ms 308.459 ms !X ms
22 * * * ms ms ms
23 * a9-0-0-8.msfc1.oct.nac.net (209.123.11.85) ms ms ms * ms
24 a9-0-0-8.msfc1.oct.nac.net (209.123.11.85) 340.571 ms !X ms 331.150 ms


To WHT:
1 140.128.191.250 (140.128.191.250) 1.665 ms 1.372 ms 1.287 ms
2 140.128.246.6 (140.128.246.6) 1.815 ms 1.445 ms 1.978 ms
3 140.128.248.254 (140.128.248.254) 1.735 ms 1.921 ms 5.279 ms
4 203.72.38.102 (203.72.38.102) 90.163 ms 87.006 ms 98.652 ms
5 203.72.38.100 (203.72.38.100) 103.357 ms * ms ms
6 TANet-Internet.edu.tw (210.70.55.18) 217.635 ms 242.106 ms 261.456 ms
7 t3-1-3-0.ar2.SEA1.gblx.net (64.211.206.61) 265.536 ms * ms ms ms
8 pos5-0-622M.cr1.SEA1.gblx.net (206.132.41.121) 258.321 ms 215.009 ms * ms
9 64.211.147.86 (64.211.147.86) 245.020 ms 244.134 ms 257.679 ms
10 * so6-0-0-2488M.br2.PAO2.gblx.net (207.136.163.126) ms ms ms ms ms
11 * abovenet.br2.PAO2.gblx.net (208.50.13.82) ms ms ms ms ms
12 * sjc2-pao1-oc48-2.sjc2.above.net (208.185.175.161) ms ms ms ms ms
13 ord2-sjc2-oc48.ord2.above.net (208.184.233.46) 267.845 ms 316.235 ms 340.487 ms
14 lga1-ord2-oc48-2.lga1.above.net (208.185.156.158) 343.909 ms * ms ms ms
15 main1-core2-oc48.lga1.above.net (216.200.127.198) 368.738 ms 366.032 ms 361.924 ms
16 panther.webhostingtalk.com (209.249.55.203) 304.476 ms 346.171 ms * ms


Based on the screenshots you sent me from your visual route trace, it looks like the issue for your particular route is California; specifically Palo Alto, most likely on above.net.

Annette :D Thank you very very much .. I see what problem on myself...

:bawling: :bawling: :bawling:

Annette, are you in any way associated with Site5?

Coran, not at all. We maintain several boxes through Site5 and a bunch through Pegasus, all of which are at NAC, so it's something that we monitor pretty closely.