Report Problems/Questions Here

[Reality Check]

The squirrel needs to do a better job. My 4 year granddaughter is staying with us and she loves the page with all the smilies. When it takes too long to load she is not happy.

[neonzx]

The squirrel needs to do a better job. My 4 year granddaughter is staying with us and she loves the page with all the smilies. When it takes too long to load she is not happy.

Yikes! You know tfb is not rated-G, right?

[bill_g]

The site is acting up again over here now. New traceroute and ping screens show a difference.

C:\Users\Bill>tracert thefogbow.com

Tracing route to thefogbow.com [199.250.206.89]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 3 ms 2 ms 2 ms 192.168.254.254
3 19 ms 19 ms 19 ms adr01.tgrd.or.nwestnet.net [50.46.181.54]
4 30 ms 29 ms 41 ms cr2-tgrdorxa-a-be-501.bb.as20055.net [64.52.97.62]
5 105 ms 110 ms 55 ms cr2-bvtnorxb-b-be-25.bb.as20055.net [198.179.53.92]
6 23 ms 27 ms 25 ms cr2-bvtnorxb-a-be-10.bb.as20055.net [107.191.236.97]
7 33 ms 39 ms 35 ms cr2-smrworxa-b-be-17.bb.as20055.net [107.191.236.120]
8 45 ms 23 ms 23 ms cr2-smrworxa-a-be-12.bb.as20055.net [107.191.236.113]
9 23 ms 23 ms 23 ms prm1-sttlwawb-b-be-15.bb.as20055.net [107.191.236.62]
10 * * * Request timed out.
11 39 ms 40 ms 47 ms 76.74.79.9
12 153 ms 102 ms 86 ms ae36.cr5-was1.ip4.gtt.net [89.149.181.50]
13 128 ms 125 ms 94 ms edge2.iad1.inmotionhosting.com [198.46.80.11]
14 87 ms 86 ms 86 ms edge2.iad1.inmotionhosting.com [198.46.80.11]
15 89 ms 98 ms 114 ms csw2.iad1.inmotionhosting.com [198.46.80.85]
16 158 ms 176 ms 104 ms eccomp4-havp12.inmotionhosting.com [104.193.140.63]
17 89 ms 89 ms 90 ms vps42141.inmotionhosting.com [199.250.206.89]

Trace complete.

C:\Users\Bill>ping 199.250.206.89 -l 2048

Pinging 199.250.206.89 with 2048 bytes of data:
Reply from 199.250.206.89: bytes=2048 time=134ms TTL=49
Reply from 199.250.206.89: bytes=2048 time=133ms TTL=49
Reply from 199.250.206.89: bytes=2048 time=115ms TTL=49
Reply from 199.250.206.89: bytes=2048 time=167ms TTL=49

Ping statistics for 199.250.206.89:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 115ms, Maximum = 167ms, Average = 137ms


I increased the mtu size to resemble actual page fetchs.

[RTH10260]

Did Soros sponsor a line of coke for the squirrel - this thing is breathtaking fast.

[keith]

Did Soros sponsor a line of coke for the squirrel - this thing is breathtaking fast.

I concur.

[neonzx]

Did Soros sponsor a line of coke for the squirrel - this thing is breathtaking fast.

I concur.

Could be a cronjob -- reboot the VPS, which is quick, and all is well for an hour or two or so.

Rebooting the VPS is not a solution to the problem. Until Foggy reports in from the tech(s), we are not at a fix.

[sad-cafe]

working awesomely right now

[Reality Check]

I was curious when this problem started and it first appeared on Tuesday July 25.

[Kriselda Gray]

I would like to suggest that until Foggy logs in and tells us that it's fixed that we assume any burst of speed that we get is just that - a burst - and not a sign that the site is fixed. We've been going back and forth between "Yea! It's fixed!" and "Oh. Never mind." for two weeks now.

[bill_g]

Sluggish again this morning. More traceroute and ping results.

C:\Users\Bill>tracert thefogbow.com

Tracing route to thefogbow.com [199.250.206.89]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 53 ms 2 ms 2 ms 192.168.254.254
3 98 ms 110 ms 50 ms adr01.tgrd.or.nwestnet.net [50.46.181.54]
4 145 ms 100 ms 61 ms cr2-tgrdorxa-a-be-501.bb.as20055.net [64.52.97.62]
5 146 ms 141 ms 57 ms cr2-bvtnorxb-b-be-25.bb.as20055.net [198.179.53.92]
6 27 ms 23 ms 24 ms cr2-bvtnorxb-a-be-10.bb.as20055.net [107.191.236.97]
7 109 ms 163 ms 171 ms cr2-smrworxa-b-be-17.bb.as20055.net [107.191.236.120]
8 25 ms 25 ms 30 ms cr2-smrworxa-a-be-12.bb.as20055.net [107.191.236.113]
9 * 167 ms 160 ms prm1-sttlwawb-b-be-15.bb.as20055.net [107.191.236.62]
10 * * * Request timed out.
11 24 ms 23 ms 22 ms 76.74.79.9
12 114 ms 109 ms 89 ms ae36.cr5-was1.ip4.gtt.net [89.149.181.50]
13 159 ms 88 ms 88 ms edge2.iad1.inmotionhosting.com [198.46.80.11]
14 296 ms 376 ms 332 ms edge2.iad1.inmotionhosting.com [198.46.80.11]
15 403 ms 481 ms 526 ms csw2.iad1.inmotionhosting.com [198.46.80.85]
16 85 ms 87 ms 85 ms eccomp4-havp12.inmotionhosting.com [104.193.140.63]
17 95 ms 86 ms 86 ms vps42141.inmotionhosting.com [199.250.206.89]

Trace complete.

C:\Users\Bill>ping 199.250.206.89 -l 2048

Pinging 199.250.206.89 with 2048 bytes of data:
Reply from 199.250.206.89: bytes=2048 time=111ms TTL=49
Reply from 199.250.206.89: bytes=2048 time=113ms TTL=49
Reply from 199.250.206.89: bytes=2048 time=111ms TTL=49
Reply from 199.250.206.89: bytes=2048 time=114ms TTL=49

Ping statistics for 199.250.206.89:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 111ms, Maximum = 114ms, Average = 112ms

[Reality Check]

I would like to suggest that until Foggy logs in and tells us that it's fixed that we assume any burst of speed that we get is just that - a burst - and not a sign that the site is fixed. We've been going back and forth between "Yea! It's fixed!" and "Oh. Never mind." for two weeks now.

Actually I would prefer the forum just be down than the current state of working 5% of the time. As is a lot of time is wasted trying to use it.

[sugar magnolia]

Any update from the techs Foggy?

I hope they're going to prorate your bill.

[neonzx]

Sluggish again this morning. More traceroute and ping results.

C:\Users\Bill>tracert thefogbow.com

Tracing route to thefogbow.com [199.250.206.89]
over a maximum of 30 hops:

Give it up, buddy. This can't be diagnosed from remote.

[Grumpy Git]

Actually I would prefer the forum just be down than the current state of working 5% of the time. As is a lot of time is wasted trying to use it.

It may be sluggish but it's certainly not as bad as 5%, at least not from here over the pond.

I will always prefer having a sluggish Fogbow than none at all.

[Tiredretiredlawyer]

Shut the Fogbow down? I join Grumpy Git in a very loud NO!!!!!!!

[Estiveo]

Well, unless it's just to unplug it, wait a minute, then plug it back in.

Have we tried unplugging it and plugging it back in?

[Kriselda Gray]

Shut the Fogbow down? I join Grumpy Git in a very loud NO!!!!!!!

Me Three.

[Reality Check]

I don’t want the Fogbow to go away. Just get fixed!

[bill_g]

Me four. If nothing else it teaches patience.

[bill_g]

Sluggish again this morning. More traceroute and ping results.

C:\Users\Bill>tracert thefogbow.com

Tracing route to thefogbow.com [199.250.206.89]
over a maximum of 30 hops:

Give it up, buddy. This can't be diagnosed from remote.

Being a transport layer wrench at heart, these things fascinate me. I'm just leaving breadcrumbs that may or may not end up being useful. When it's acting up there is a distinct difference in the times from gtt.net with subsequent increases in time from the inmotion machines. There are fewer reports from users across the pond, and more from east coast USians, suggesting there are regional gateways feeding inmotion. Might be accurate. Might not. Needs confirmation.

And!

This also means that Foggy is doing what the doctor told him to do about his arms - don't. So, I'll take a sluggish board knowing he is on the mend. We'll get it fixed when we get it fixed.

[Estiveo]

There appears to be something very wrong with page 36 of General Law & Lawsuits, unrelated, I think, to the ongoing issues. I get this error:

Estiveoshot_20230810_212347.jpg (25.33 KiB) Viewed 625 times

[RTH10260]

There appears to be something very wrong with page 36 of General Law & Lawsuits, unrelated, I think, to the ongoing issues. I get this error:

Estiveoshot_20230810_212347.jpg

Error 500 = cannot process at this time - my bet is that a technician was at work on some part (database?). Foggy would have had the Work in progress page showing.

[Slim Cognito]

I check in, if it works great, if it's sluggish I go do something else. On the bright side, my house is really clean.

[sugar magnolia]

There appears to be something very wrong with page 36 of General Law & Lawsuits, unrelated, I think, to the ongoing issues. I get this error:
Estiveoshot_20230810_212347.jpg

I'm getting that too.

[Tiredretiredlawyer]

I check in, if it works great, if it's sluggish I go do something else. On the bright side, my house is really clean.

Are you available to clean mine?