Forum Technical Issues

[JimClark]

Seems to be fine on my end

Sent from my SGH-T989 using Tapatalk 4

[jj2003]

I can ping hop #11 with 0% loss. 100% packet loss @ hop #14.

Pinging 69.22.142.166 with 32 bytes of data:
Reply from 69.22.142.166: bytes=32 time=99ms TTL=54
Reply from 69.22.142.166: bytes=32 time=86ms TTL=54
Reply from 69.22.142.166: bytes=32 time=84ms TTL=54
Reply from 69.22.142.166: bytes=32 time=90ms TTL=53
Reply from 69.22.142.166: bytes=32 time=84ms TTL=54
Reply from 69.22.142.166: bytes=32 time=84ms TTL=54
Reply from 69.22.142.166: bytes=32 time=85ms TTL=54
Reply from 69.22.142.166: bytes=32 time=103ms TTL=54
Reply from 69.22.142.166: bytes=32 time=81ms TTL=54
Reply from 69.22.142.166: bytes=32 time=81ms TTL=54
Reply from 69.22.142.166: bytes=32 time=82ms TTL=54
Reply from 69.22.142.166: bytes=32 time=83ms TTL=54
Reply from 69.22.142.166: bytes=32 time=82ms TTL=54
Reply from 69.22.142.166: bytes=32 time=81ms TTL=54
Reply from 69.22.142.166: bytes=32 time=81ms TTL=54
Reply from 69.22.142.166: bytes=32 time=83ms TTL=54
Reply from 69.22.142.166: bytes=32 time=82ms TTL=54
Reply from 69.22.142.166: bytes=32 time=82ms TTL=54
Reply from 69.22.142.166: bytes=32 time=82ms TTL=54
Reply from 69.22.142.166: bytes=32 time=82ms TTL=54
Reply from 69.22.142.166: bytes=32 time=81ms TTL=54
Reply from 69.22.142.166: bytes=32 time=82ms TTL=54
Reply from 69.22.142.166: bytes=32 time=82ms TTL=54
Reply from 69.22.142.166: bytes=32 time=90ms TTL=54
Reply from 69.22.142.166: bytes=32 time=83ms TTL=54
Reply from 69.22.142.166: bytes=32 time=86ms TTL=54
Reply from 69.22.142.166: bytes=32 time=84ms TTL=54
Reply from 69.22.142.166: bytes=32 time=84ms TTL=54
Reply from 69.22.142.166: bytes=32 time=81ms TTL=54
Reply from 69.22.142.166: bytes=32 time=100ms TTL=54
Reply from 69.22.142.166: bytes=32 time=80ms TTL=54
Reply from 69.22.142.166: bytes=32 time=96ms TTL=54
Reply from 69.22.142.166: bytes=32 time=87ms TTL=54
Reply from 69.22.142.166: bytes=32 time=87ms TTL=54
Reply from 69.22.142.166: bytes=32 time=83ms TTL=54
Reply from 69.22.142.166: bytes=32 time=85ms TTL=54
Reply from 69.22.142.166: bytes=32 time=81ms TTL=54


Ping statistics for 69.22.142.166:
Packets: Sent = 37, Received = 37, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 103ms, Average = 85ms

[jj2003]

OSE Timing out again.

Tried a trace and here are the results:

Tracing route to www.forums.offshoreelectrics.com [68.169.39.251]
over a maximum of 30 hops:


1 4 ms 3 ms 2 ms CISCO41605 [192.168.1.1]
2 * * * Request timed out.
3 14 ms 16 ms 14 ms 98.0.2.209
4 17 ms 15 ms 15 ms ae10-0.lncsnycd-rtr001.nyroc.rr.com [98.0.3.38]


5 29 ms 35 ms 47 ms bundle-ether6.rochnyei-rtr000.nyroc.rr.com [98.0
.3.3]
6 35 ms 35 ms 30 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
7 32 ms 30 ms 31 ms ae4.pr1.chi10.tbone.rr.com [66.109.1.66]
8 34 ms 39 ms 33 ms xe-4-0-5.ar2.ord1.us.nlayer.net [69.31.110.209]


9 80 ms 31 ms 44 ms ae2-40g.cr2.ord1.us.nlayer.net [69.31.111.149]
10 62 ms 62 ms 63 ms xe-0-2-0.cr1.den1.us.nlayer.net [69.22.142.169]


11 103 ms 104 ms 102 ms xe-2-0-0.cr2.slc1.us.nlayer.net [69.22.142.166]


12 * * * Request timed out.
13 * * * Request timed out.
14 107 ms 119 ms 105 ms 206.130.126.69.west-datacenter.net [206.130.126.
69]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.


Trace complete.


C:\Users\JOHN SR>
C:\Users\JOHN SR>tracert www.forums.offshoreelectrics.com


Tracing route to www.forums.offshoreelectrics.com [68.169.39.251]
over a maximum of 30 hops:


1 2 ms 1 ms 1 ms CISCO41605 [192.168.1.1]
2 * * * Request timed out.
3 22 ms 15 ms 15 ms 98.0.2.209
4 18 ms 15 ms 19 ms ae10-0.lncsnycd-rtr001.nyroc.rr.com [98.0.3.38]


5 48 ms 31 ms 31 ms bundle-ether6.rochnyei-rtr000.nyroc.rr.com [98.0
.3.3]
6 33 ms 31 ms 30 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
7 32 ms 31 ms * ae4.pr1.chi10.tbone.rr.com [66.109.1.66]
8 36 ms 49 ms 34 ms xe-4-0-5.ar2.ord1.us.nlayer.net [69.31.110.209]


9 35 ms 81 ms 48 ms ae2-40g.cr2.ord1.us.nlayer.net [69.31.111.149]
10 63 ms 63 ms 75 ms xe-0-2-0.cr1.den1.us.nlayer.net [69.22.142.169]


11 103 ms 117 ms 117 ms xe-2-0-0.cr2.slc1.us.nlayer.net [69.22.142.166]


12 * * * Request timed out.
13 * * * Request timed out.
14 107 ms 107 ms * 206.130.126.69.west-datacenter.net [206.130.126.
69]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.


Trace complete.

Seems to be a bottleneck out on the west coast. High traffic time out there at this time on the east coast. Maybe Steven can use the info to provide the Host and determine if it's a hosting issue or if it's in the providers backbone. Time Warner is O.K.

[SloHD]

Now this BS won't go away. WTF

[properchopper]

The Plot Thickens

[SloHD]

I'm on Bright house (Time Warner in Fl)

That seems to be in common...

[properchopper]

Doesn't even seem to be a local type of issue. we're in Ca, Fl, and NY.
I'm on Time Warner.

Time Warner RoadRunner Turbo Cisco 2100 cable modum

[marko500]

Doesn't even seem to be a local type of issue. we're in Ca, Fl, and NY.
I'm on Time Warner.

[properchopper]

I was worried that my cormputer had an issue if I was the only one experiencing this. I'm not saying that I'm happy that others are in the same boat, just that maybe our networks or some other magical/mystical tech issues are at work (or laying down on the job)

[SloHD]

Yep, that's when it happens the most for me as well.

[marko500]

Same here, seems worse in the evenings.

[properchopper]

Been happening to me ; usually in the evenings. Sometimes can't load at all. Wazzup ?

[marko500]

I've been having the same problem, started yesterday.

[Doug Smock]

Good here.

[Fluid]

Nope, I've been able to log on numerous times today from my phone. Probably your ISP.




.