XF official forum issue

Peggy, if you can get through, and the forum needs attention there are a couple of ways you can contact me, and those work fine. It is painfully intermittent from Silicon valley area.
 
@ Dean - I'm not able to quote your post for whatever reason. I'm here and posting now, but on my way to bed.
I hope that whatever it is, is cleared up by tomorrow.

Y'know what I find strange?..... I have no problem with any other site. Only xf.com. How odd is that?
 
Seems like whatever it was has been fixed. Definitely was driving me crazy all afternoon though. lol Was only this site too for whatever reason. {shrug}

Edit: spoke too soon. still happening /wrists
 
Peggy, if you can get through, and the forum needs attention there are a couple of ways you can contact me, and those work fine. It is painfully intermittent from Silicon valley area.

@ Dean - I'm not able to quote your post for whatever reason. I'm here and posting now, but on my way to bed.
I hope that whatever it is, is cleared up by tomorrow.

Y'know what I find strange?..... I have no problem with any other site. Only xf.com. How odd is that?

Who is your ISP?
 
AT&T U-Verse for me.
Same here, though I don't like them much.
rolleyes.png
 
Still.... why would this be the only site we are having issues with? You'd think we'd have issues with the entire internet?
 
Houston, we have a problem.

I did a tracert - the problem is in Houston.. More strangely, for me, I can tracert http://xenforo.com but it is intermittent. I cannot tracert www.xenforo.com. They take very different paths.

For me...

and some omissions...

C:\>tracert www.xenforo.com

Tracing route to xenforo.com [174.123.247.179]
over a maximum of 30 hops:

5 14 ms 14 ms 13 ms BE14-lsanca4-rt1.socal.rr.com [66.75.151.3]
6 11 ms 12 ms 14 ms ae-6-0.cr0.lax00.tbone.rr.com [66.109.6.212]
7 10 ms 12 ms 14 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
8 11 ms 10 ms 12 ms xe-4-2-0.edge1.LosAngeles6.Level3.net [4.26.0.77]
9 12 ms 15 ms 22 ms vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]
10 13 ms 12 ms 12 ms ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.17]
11 46 ms 51 ms 53 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 50 ms 55 ms 51 ms ae-81-88.ebr1.Dallas1.Level3.net [4.69.146.82]
13 54 ms 49 ms 50 ms ae-1-13.bar1.Houston1.Level3.net [4.69.137.137]
14 57 ms 63 ms 52 ms ae-0-11.bar2.Houston1.Level3.net [4.69.137.134]
15 54 ms 54 ms 64 ms THE-PLANET.bar2.Houston1.Level3.net [4.78.10.30]
16 52 ms 53 ms 54 ms te2-1.dsr02.hstntx1.networklayer.com [207.218.223.34]
17 53 ms 52 ms 64 ms po2.car03.hstntx1.networklayer.com [207.218.245.10]
18 52 ms 52 ms 51 ms b3.f7.7bae.static.theplanet.com [174.123.247.179]

Trace complete.

C:\>tracert xenforo.com

Tracing route to xenforo.com [174.123.247.179]
over a maximum of 30 hops:

5 12 ms 21 ms 12 ms BE14-lsanca4-rt1.socal.rr.com [66.75.151.3]
6 14 ms 12 ms 12 ms ae-6-0.cr0.lax00.tbone.rr.com [66.109.6.212]
7 12 ms 15 ms 12 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
8 11 ms 11 ms 13 ms xe-4-2-0.edge1.LosAngeles6.Level3.net [4.26.0.77]
9 22 ms 9 ms 14 ms vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]
10 11 ms 12 ms 12 ms ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.17]
11 48 ms 53 ms 53 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 50 ms 53 ms 52 ms ae-81-88.ebr1.Dallas1.Level3.net [4.69.146.82]
13 51 ms 50 ms 50 ms ae-1-13.bar1.Houston1.Level3.net [4.69.137.137]
14 52 ms 53 ms 54 ms ae-0-11.bar2.Houston1.Level3.net [4.69.137.134]
15 54 ms 55 ms 55 ms THE-PLANET.bar2.Houston1.Level3.net [4.78.10.30]
16 53 ms 58 ms 52 ms te2-1.dsr02.hstntx1.networklayer.com [207.218.223.34]
17 54 ms 51 ms 50 ms po2.car03.hstntx1.networklayer.com [207.218.245.10]
18 53 ms 53 ms 50 ms b3.f7.7bae.static.theplanet.com [174.123.247.179]

Trace complete.
 
Still.... why would this be the only site we are having issues with? You'd think we'd have issues with the entire internet?

Not necessarily, it all depends on what path your connection takes to get to it's destination. Each site you access probably has a different route and it all depends on the transit providers between you and the destination. A tracert would identify who the lame duck is in your routing path.
 
These are the last hops that work for tracert to www.xenforo.com:


9 72 ms 56 ms 55 ms ae-0.r21.lsanca03.us.bb.gin.ntt.net [129.250.3.34]
10 95 ms 98 ms 98 ms xe-6-4.r03.hstntx01.us.bb.gin.ntt.net [129.250.3.122]
11 98 ms 96 ms 98 ms xe-6-3.r03.hstntx01.us.ce.gin.ntt.net [128.241.1.6]
12 * * * Request timed out.
13 96 ms 97 ms 98 ms te2-5.dsr01.hstntx1.networklayer.com [207.218.245.26]

The problem is in Houston, possibly inside the Planet headquarters.. though keep in mind I do not know a lot about these things.
 
I think it's finally resolved for me, hours later. Made sure it didn't cause problems after loading this thread but looks like it finally sorted itself. :)
 
Back
Top Bottom