Glad the Forum is back up! (Hey, Wha Happen?)

I went into withdrawals for an evening. Glad, the forum is back in the saddle.
Never noticed it go down in the past four years.
Maybe this is regular business, maybe it was the work of some Transit owners...
Thanks moderators for your continued upkeep of the Sprinter Forum. Dale

Planned maintenance. There was a notice under forum notifications. Clearly took longer than planned; but Sikwan had a disclaimer up.


Sent from my iPhone using Tapatalk

You're not the only one having withdrawals.

The new server was up and running (and waiting) 2am this morning. However, when changing servers/ip's, it takes ~24hrs for the domain name to propagate the (domain name servers of the) world. A short 300 second TTL (Time To Live) was set around 1am this morning, but because of the server change it defaults back to ~24hrs.

There are still bugs to work out (like the wiki doesn't work), but at least the forum is up!

sikwan said:

There are still bugs to work out

Click to expand...

Typo, you mean you owe some hugs to some ppl?

You got everyone back but the RVers?

I know, I just about had a midlife crisis with the forum down. Reading the service manual kept sprinter withdrawls down, but I kept googling stuff and ending up here haha. I love this forum and all of you sprinter people

sikwan said:

There are still bugs to work out (like the wiki doesn't work), but at least the forum is up!

Click to expand...

The forum does seem to work OK, but it has become painfully slow since the server change.

mendonsy said:

The forum does seem to work OK, but it has become painfully slow since the server change.

Click to expand...

Ditto at home (Verizon + Chrome/desk - Kindle - Android/Chrome)
and office (Chrome Explorer)

Please type this in a command window...

traceroute (tracert for windows) sprinter-source.com

This is what I'm getting for my Sonic/ATT account...

1 homeportal (192.168.1.254) 59.635 ms 2.282 ms 1.918 ms
2 99-106-172-1.lightspeed.sntcca.sbcglobal.net (99.106.172.1) 20.327 ms 21.987 ms 102.519 ms
3 71.148.135.104 (71.148.135.104) 22.454 ms 21.990 ms 25.805 ms
4 * * *
5 12.83.39.193 (12.83.39.193) 23.710 ms
12.83.39.197 (12.83.39.197) 26.500 ms
12.83.39.193 (12.83.39.193) 23.891 ms
6 12.122.114.53 (12.122.114.53) 32.873 ms 22.383 ms 25.370 ms
7 10ge13-6.core1.sjc2.he.net (64.62.171.65) 32.755 ms 25.252 ms 30.337 ms
8 10ge1-1.core1.fmt1.he.net (72.52.92.109) 30.032 ms 28.674 ms 25.449 ms
9 sprinter-source.com (64.71.133.115) 27.513 ms 23.640 ms 27.628 ms

Step 4 is causing me grief.

On my Comcast account...

1 192.168.1.254 0.201ms 0.161ms 0.159ms
2 96.120.88.81 12.316ms 8.374ms 8.484ms
3 162.151.30.225 8.722ms 8.403ms 8.466ms
4 162.151.78.249 9.631ms 9.549ms 9.202ms
5 68.86.90.93 9.833ms 9.239ms 9.585ms
6 68.86.87.158 12.097ms 11.170ms 12.982ms
7 68.86.83.130 10.637ms 10.912ms 11.624ms
8 64.62.153.169 19.863ms 10.216ms 14.607ms
9 72.52.92.109 10.485ms 11.213ms 14.024ms
10 64.71.133.115 10.811ms 10.832ms 10.779ms

I get no slow down.


We experienced some heavy rains this past weekend, so a lot of power outages. Whether this is a culprit, I don't know. Changing servers do change the traceroute.

Tracing route to sprinter-source.com [64.71.133.115]
over a maximum of 30 hops:

1-3... (deleted by me)

4 4 ms 4 ms 4 ms ae0-90g.ar7.lax1.gblx.net [67.16.162.22]
5 4 ms 4 ms 4 ms ae10.edge1.losangeles9.level3.net [4.68.111.21]

6 * * * Request timed out.
7 14 ms 4 ms 6 ms 10ge9-19.core1.lax1.he.net [65.19.151.97]
8 15 ms 17 ms 54 ms 100ge14-1.core1.sjc2.he.net [184.105.223.249]
9 29 ms 15 ms 14 ms 10ge1-1.core1.fmt1.he.net [72.52.92.109]
10 13 ms 13 ms 13 ms sprinter-source.com [64.71.133.115]

Trace complete.


maybe someone is underwater...

I get my router and DSL modem (1ms each) then seven repeats of * * * Request timed out and finally sprinter-source.com (91 ms)

That is strange because none of the other sites that I visit regularly are having any problems at all.

Maybe I'm speaking too soon, but I've disabled some features that might decrease the loading speed a bit.

It's feels a bit faster, but it could be something else...


EDIT: Well, spoke too soon...

My first attempt seemed to not complete (i was feeding it into a text file, so i couldn't watch it)

Tracing route to sprinter-source.com [64.71.133.115]
1 6 ms 2 ms 1 ms 192.168.0.1
2 4 ms 3 ms 5 ms XXXgw66.tukw.qwest.net [63.231.XXX]
3 8 ms 4 ms 4 ms tukw-agw1.inet.qwest.net [71.217.186.9]
4 34 ms 6 ms 4 ms sea-brdr-02.inet.qwest.net [67.14.41.190]
5 6 ms 24 ms 22 ms 10ge2-11.core1.sea1.he.net [72.52.83.9]
6 22 ms 21 ms 22 ms 100ge11-1.core1.sjc2.he.net [184.105.223.217]

The next two (one on screen, then another file capture) did complete, but there was a noticeable pause after lines 6 and 7:
Tracing route to sprinter-source.com [64.71.133.115]
1 14 ms 2 ms 2 ms 192.168.0.1
2 4 ms 3 ms 4 ms XXXXgw66.tukw.qwest.net [63.231.XXX]
3 4 ms 6 ms 5 ms tukw-agw1.inet.qwest.net [71.217.186.9]
4 4 ms 4 ms 11 ms sea-brdr-02.inet.qwest.net [67.14.41.190]
5 17 ms 32 ms 33 ms 10ge2-11.core1.sea1.he.net [72.52.83.9]
6 29 ms 32 ms 22 ms 100ge11-1.core1.sjc2.he.net [184.105.223.217]
7 28 ms 26 ms 23 ms 10ge1-1.core1.fmt1.he.net [72.52.92.109]
8 23 ms 23 ms 29 ms sprinter-source.com [64.71.133.115]

Tracing route to sprinter-source.com [64.71.133.115]
1 2 ms 1 ms 1 ms 192.168.0.1
2 5 ms 6 ms 4 ms XXXXgw66.tukw.qwest.net [63.231.XXX]
3 4 ms 4 ms 4 ms tukw-agw1.inet.qwest.net [71.217.186.9]
4 8 ms 4 ms 4 ms sea-brdr-02.inet.qwest.net [67.14.41.190]
5 16 ms 23 ms 24 ms 10ge2-11.core1.sea1.he.net [72.52.83.9]
6 23 ms 31 ms 23 ms 100ge11-1.core1.sjc2.he.net [184.105.223.217]
7 33 ms 23 ms 29 ms 10ge1-1.core1.fmt1.he.net [72.52.92.109]
8 23 ms 24 ms 27 ms sprinter-source.com [64.71.133.115]

... and the command in Windows is "tracert sprinter-source.com"
(tests run at 3pm PST Jan 9th)
By the 3rd (and a 4th) test, there was no delay after 6&7

A ping test got 40 millisec for the first probe, 22 ms thereafter.

--dick

Thanks Dick. Your stuff looks real good.

Anyways, I contacted Hurricane Electric to verify whether it's a hardware issue and its not. The slowdown is coming from outside Hurricane Electric at AT&T.

No choice but to wait until AT&T get their machines fixed.

I'm not an expert in this realm, but I did notice most every page I open says something like "aquiring secure connection". Perhaps that is because I'm Down Under at the moment.

Serious latency issues (Comcast is my ISP). Also other issues sometimes when attempting to post - occasionally get an error message: "connection was lost" using Safari

Did you move the host to a different data center? AWS?

PortlandRV said:

Serious latency issues (Comcast is my ISP). Also other issues sometimes when attempting to post. Did you move the host to a different data center?

Click to expand...

Data center is the same. The only thing changed is the hardware (server). We went from an AMD, 2G memory, 80G (RAID mirrored) to an I3, 4G memory, 1T (Raid mirrored).

I'm sure I'm missing something...

sikwan said:

Thanks Dick. Your stuff looks real good.

Anyways, I contacted Hurricane Electric to verify whether it's a hardware issue and its not. The slowdown is coming from outside Hurricane Electric at AT&T.

No choice but to wait until AT&T get their machines fixed.

Click to expand...

Oh no!!! Finger pointing? HE is going to blame AT&T for the latency issues? What kind of bandwidth do you have coming into your cabinet? Is AT&T your Internet provider? I can hook you up with some Ethernet Dedicated Internet with Comcast Business. If you're interested you can PM me.

Seeing the same issue: "acquiring secure connection". One server timeout in two days.
Delays irregular. Sometimes non existent, sometimes 10 sec.

Whatever. It's a privilege to be here.

PortlandRV said:

Oh no!!! Finger pointing? HE is going to blame AT&T for the latency issues? What kind of bandwidth do you have coming into your cabinet? Is AT&T your Internet provider? I can hook you up with some Ethernet Dedicated Internet with Comcast Business. If you're interested you can PM me.

Click to expand...

100Mbps to the server. The same before the move.

I have Sonic/ATT and Comcast. I'm not blaming ATT. It's one of the issues I've yet to figure out.