Web Hosting Talk : Web Hosting Main Forums : Dedicated Server : HE.net - Fremont Problems?

[mainarea]

Just checking out a few providers and noticed that one was coming up slowly. It seems as if there's a problem at the HE.net/WCG connection:

Tracing route to gige-g9-0-27s.gsr12012.sjc.he.net [216.218.128.1]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 23 ms 14 ms 11 ms 10.107.184.1
3 12 ms 13 ms 11 ms 172.30.112.145
4 12 ms 11 ms 26 ms 172.30.111.109
5 12 ms 18 ms 15 ms 172.30.111.122
6 11 ms 22 ms 12 ms 68.39.224.162
7 19 ms 17 ms 31 ms 68.87.18.25
8 17 ms 19 ms 15 ms 68.87.16.2
9 18 ms 15 ms 16 ms 12.119.53.49
10 18 ms 19 ms 17 ms tbr1-p012401.phlpa.ip.att.net [12.123.137.45]
11 16 ms 15 ms 15 ms tbr1-cl8.n54ny.ip.att.net [12.122.2.17]
12 16 ms 25 ms 14 ms ggr1-p330.n54ny.ip.att.net [12.122.11.214]
13 192 ms 191 ms 192 ms nycmny2wcx2-pos6-3.wcg.net [64.200.68.41]
14 88 ms 91 ms 89 ms nycmny2wcx3-oc48.wcg.net [64.200.87.78]
15 95 ms 94 ms 94 ms brvwil1wcx3-pos11-0.wcg.net [64.200.210.109]
16 94 ms 91 ms 89 ms brvwil1wcx2-pos9-0-1-a0.wcg.net [64.200.103.193]

17 92 ms 95 ms 93 ms dnvrco1wcx2-pos10-0.wcg.net [64.200.210.66]
18 95 ms 93 ms 93 ms snfcca1wcx3-pos11-0.wcg.net [64.200.240.94]
19 108 ms 92 ms 92 ms snfcca1wcx2-oc48.wcg.net [64.200.199.77]
20 93 ms 93 ms 102 ms 64.200.240.98
21 93 ms 93 ms 92 ms sntcca4lcx1-pos9-0.wcg.net [64.200.240.126]
22 437 ms 438 ms 443 ms sntcca4lce1-hurricane-gige.wcg.net [64.200.150.1
06]
23 454 ms 450 ms 444 ms gige-g5-0.gsr12008.fmt.he.net [216.218.214.217]

24 448 ms 454 ms 656 ms gige-g9-0-27s.gsr12012.sjc.he.net [216.218.128.1
]

Trace complete.


I get onto HE's network fine from XO:

traceroute to 216.218.128.1 (216.218.128.1), 30 hops max, 38 byte packets
1 ge-5-0-border.scr1.hostnoc.net (64.191.0.1) 0.255 ms 0.187 ms 0.109 ms
2 66.197.191.46 (66.197.191.46) 5.214 ms 5.424 ms 5.294 ms
3 fe12-0.chr1.philadelphia-pa.us.xo.net (66.236.204.9) 5.479 ms 5.828 ms 5.330 ms
4 p4-3-0.MAR2.Philadelphia-PA.us.xo.net (207.88.87.45) 5.549 ms 5.555 ms 5.746 ms
5 p5-1-0-1.RAR2.Washington-DC.us.xo.net (65.106.3.153) 9.289 ms 9.387 ms 9.430 ms
6 p1-0.IR1.Ashburn-VA.us.xo.net (65.106.3.138) 10.378 ms 10.405 ms 10.242 ms
7 gige-g0-0-306.gsr12012.ash.he.net (64.62.227.37) 13.034 ms 12.982 ms 12.603 ms
8 pos7-0.gsr12012.pao.he.net (216.218.254.205) 87.679 ms 87.227 ms 86.981 ms
9 gige-g5-0.gsr12008.pao.he.net (216.218.254.33) 86.901 ms 87.069 ms 87.303 ms
10 * * *


- Matt

[Fremont Servers]

[pztup]

Here's my tracert on my dialup connection, seems problem free to me.

Tracing route to gige-g9-0-27s.gsr12012.sjc.he.net [216.218.128.1]
over a maximum of 30 hops:

1 133 ms 139 ms 140 ms [MASKED]
2 139 ms 134 ms 140 ms [MASKED]
3 140 ms 140 ms 138 ms 63-104-229-162.focaldata.net [63.104.229.162]
4 218 ms 140 ms 140 ms gigabitethernet8-0-106.ipcolo1.sanfrancisco1.lev
el3.net [63.211.150.101]
5 140 ms 140 ms 139 ms gigabitethernet4-0.core1.sanfrancisco1.level3.net [209.244.14.193]
6 155 ms 140 ms 139 ms so-4-0-0.mp2.sanfrancisco1.level3.net [209.247.1.0.233]
7 140 ms 140 ms 140 ms so-2-0-0.mp2.sanjose1.level3.net [64.159.0.218]

8 139 ms 140 ms 139 ms so-7-0-0.gar2.sanjose1.level3.net [64.159.1.78]

9 140 ms 139 ms 140 ms so-7-0-0.edge1.sanjose1.level3.net [209.244.3.142]
10 140 ms 140 ms 155 ms gige-g3-0.gsr12012.sjc2.he.net [216.218.214.221]

11 126 ms 140 ms 140 ms gige-g5-0.gsr12008.fmt.he.net [216.218.214.217]

12 140 ms 187 ms 140 ms gige-g9-0-27s.gsr12012.sjc.he.net [216.218.128.1
]

Trace complete.

[josh@fs]

Seems to be free and clear from our remote location in Iowa:

Note: As most of you know we host 99% of our servers in HE.net's Fremont location:

C:\>tracert powersurge.net

Tracing route to powersurge.net [216.218.202.95]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms [192.104.109.174]

2 10 ms <10 ms <10 ms [192.104.109.55]
3 <10 ms <10 ms <10 ms [192.104.109.21]
4 <10 ms <10 ms <10 ms [24.149.0.201]
5 10 ms 10 ms 10 ms 12.119.178.177
6 30 ms 20 ms 30 ms gbr6-p51.sl9mo.ip.att.net [12.123.198.134]
7 20 ms 10 ms 20 ms tbr2-p013601.sl9mo.ip.att.net [12.122.11.125]
8 20 ms 30 ms 30 ms tbr2-cl7.cgcil.ip.att.net [12.122.10.45]
9 30 ms 30 ms 30 ms ggr1-p3100.cgcil.ip.att.net [12.122.11.210]
10 40 ms 40 ms 40 ms att-gw.chi.above.net [192.205.31.206]
11 50 ms 40 ms 40 ms so-7-3-0.cr1.ord2.us.above.net [64.125.30.157]
12 80 ms 70 ms 81 ms so-3-0-0.mpr3.sjc2.us.above.net [64.125.30.205]

13 70 ms 80 ms 70 ms so-2-0-0.er10a.sjc2.us.above.net [64.125.30.90]

14 80 ms 80 ms 70 ms 208.185.182.61.he.net [208.185.182.61]
15 70 ms 90 ms 71 ms 216.218.130.8
16 70 ms 80 ms 70 ms gsr-fremont-ultraservers.hyperspace [64.71.160.4
6]
17 80 ms 80 ms 70 ms powersurge.net [216.218.202.95]

Trace complete.

Looks like there may be a peering issue between wcg.net and he.net or an issue within wcg.net alone:

21 93 ms 93 ms 92 ms sntcca4lcx1-pos9-0.wcg.net [64.200.240.126]
22 437 ms 438 ms 443 ms sntcca4lce1-hurricane-gige.wcg.net [64.200.150.1
06]
23 454 ms 450 ms 444 ms gige-g5-0.gsr12008.fmt.he.net [216.218.214.217]

Always include your local external IP when submitting traces to noc@he.net so they can test things out as well.

[peace]

[IGobyTerry]

tracert powersurge.net

Tracing route to powersurge.net [216.218.202.95]
over a maximum of 30 hops:

1 * * * Request timed out.
2 21 ms 23 ms 24 ms adsl-127-0-0-1.dsl.bcvloh.ameritech.net [68.
73.173.254]
3 24 ms 23 ms 22 ms dist1-vlan50.bcvloh.ameritech.net [66.73.20.226]

4 23 ms 22 ms 24 ms bb1-ge2-0.bcvloh.ameritech.net [66.73.20.99]
5 38 ms 40 ms 41 ms sl-gw1-pen-13-1.sprintlink.net [144.228.68.121]

6 39 ms 39 ms 37 ms sl-bb20-pen-5-0.sprintlink.net [144.232.5.1]
7 39 ms 40 ms 39 ms sl-bb21-pen-14-0.sprintlink.net [144.232.16.34]

8 41 ms 41 ms 42 ms sl-bb23-rly-0-0.sprintlink.net [144.232.20.32]
9 42 ms 41 ms 42 ms sl-gw19-rly-10-0.sprintlink.net [144.232.14.42]

10 44 ms 44 ms 47 ms sl-abovenet-19-0.sprintlink.net [144.232.247.86]

11 117 ms 115 ms 116 ms so-3-0-0.mpr3.sjc2.us.above.net [208.184.233.133
]
12 117 ms 115 ms 115 ms so-2-0-0.er10a.sjc2.us.above.net [64.125.30.90]

13 115 ms 117 ms 117 ms 208.185.182.61.he.net [208.185.182.61]
14 115 ms 118 ms 119 ms 216.218.130.8
15 118 ms 118 ms 120 ms gsr-fremont-ultraservers.hyperspace [64.71.160.4
6]
16 121 ms 117 ms 118 ms powersurge.net [216.218.202.95]

Trace complete.

Looks fine from here in Ohio.

[ThomasC]

Looks ok to me

PHP Code:

Tracing route to gige-g9-0-27s.gsr12012.sjc.he.net [216.218.128.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms     4 ms  192.168.0.1
  2    26 ms    26 ms    27 ms  lo0.plusnet.pth-ag1.plus.net [195.166.128.11]
  3    29 ms    29 ms    30 ms  gi1-2.vlan3.pth-gw3.plus.net [212.159.1.2]
  4    27 ms    26 ms    27 ms  gi5-0-4.pth-gw1.plus.net [195.166.129.21]
  5    29 ms    28 ms    29 ms  gsr12012.lon.he.net [195.66.224.21]
  6   100 ms   100 ms    96 ms  pos8-0.br1.nyc.he.net [216.218.200.101]
  7   170 ms   171 ms   181 ms  gige-g9-0-27s.gsr12012.sjc.he.net [216.218.128.1] 


[VP]

Yep, works fine for me too

[IGobyTerry]

eh, I think you guys are about 2 hours too late.

[jiida]

I also had a downtime just now on my server at HE. It was nice for last one week without any hickups, but there were some downtime last 3 days in a row with pings going up to 200 to 400 for 20 to 40 minutes. I had complaints of downtime from my customers as well. Though it doesn't seem to affect the entire network. www.he.net or fastservers.net doesn't seem to get affected, but some of the cheaper resellers also seem to get the same problem. Not all HE.net servers are the same it seem.

[Potsie]

It may have more to do with peering. During some of those spikes I get the same great pings from my DSL, but the cable connection blows. I know the AT&T peering points have been getting worse and worse for me lately - and not just to HE.
Anyway, I too saw horrendous pings and packet loss tonight and the spikes for the last few nights. Pings are currently more than twice what they normally are.