GFY under attack?

shit sorry about the double post...but at the time the board was lagging so bad i ended up hitting the submitt button twice....whats going on guys??

shit sorry about the double post...but at the time the board was lagging so bad i ended up hitting the submitt button twice....whats going on guys??

Post a tracert & ping if you can, I'd like to see it.

This is the first I been able to reach it all day.

No difference for me, running smooth from here

------------------
Phat Sites Need Phat Hosting
Get PHAT

And Now You can Get even Phatter!
TGP Hosting Special!
Sign Up Now and get 15 gigs FREE in any plan (includes TGP deal)

I couldn't get on for about an hour yesterday.

Someone show me how to ping, and i'll do it. and post the results.

i've been having trouble reaching it today too

i experience problems too. Problem located in 12th line

Tracing route to gofuckyourself.net [66.60.188.248]
over a maximum of 30 hops:

1 181 ms 160 ms 160 ms loop00-noc01.cos.internet.gr [62.1.255.203]
2 160 ms 160 ms 160 ms vlan81-csr02.core.internet.gr [62.1.0.227]
3 180 ms 160 ms 161 ms fasteth10-noc01.core.internet.gr [62.1.0.1]
4 170 ms 161 ms 160 ms athens5.gr.eqip.net [195.90.65.237]
5 260 ms 280 ms 261 ms london2.gb.eqip.net [195.206.64.133]
6 280 ms 280 ms 241 ms london50.gb.eqip.net [195.206.64.37]
7 291 ms 300 ms 281 ms amsterdam11.nl.eqip.net [195.206.64.157]
8 260 ms 261 ms 400 ms pos4-0-1-155M.br1.AMS2.gblx.net [62.8.32.109]
9 260 ms 261 ms 280 ms so3-1-0-622M.cr2.AMS2.gblx.net [62.8.32.61]
10 601 ms 461 ms 420 ms pos1-0-622M.cr2.SFO1.gblx.net [206.132.110.126]

11 440 ms 461 ms 421 ms pos4-0-0-155M.ar2.SFO1.gblx.net [206.251.1.201]

12 * * * Request timed out.
13 440 ms 421 ms 441 ms 7513-1.net.surewest.net [208.45.228.240]
14 441 ms 461 ms 420 ms 254.100MB.firstname.com [66.60.131.254]
15 461 ms 440 ms 440 ms 66.60.188.248

Trace complete.


Pinging gofuckyourself.net [66.60.188.248] with 32 bytes of data:

Reply from 66.60.188.248: bytes=32 time=541ms TTL=111
Reply from 66.60.188.248: bytes=32 time=401ms TTL=111
Reply from 66.60.188.248: bytes=32 time=430ms TTL=111
Reply from 66.60.188.248: bytes=32 time=431ms TTL=111

Ping statistics for 66.60.188.248:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 401ms, Maximum = 541ms, Average = 450ms

Is that good?

Ping

trying host: -121881534
44 bytes from 66.60.188.248: icmp_seq = 0. time: 130 ms
44 bytes from 66.60.188.248: icmp_seq = 1. time: 46 ms
44 bytes from 66.60.188.248: icmp_seq = 2. time: 48 ms
44 bytes from 66.60.188.248: icmp_seq = 3. time: 49 ms
44 bytes from 66.60.188.248: icmp_seq = 4. time: 56 ms
44 bytes from 66.60.188.248: icmp_seq = 5. time: 90 ms
44 bytes from 66.60.188.248: icmp_seq = 6. time: 46 ms
44 bytes from 66.60.188.248: icmp_seq = 7. time: 43 ms
44 bytes from 66.60.188.248: icmp_seq = 8. time: 73 ms
44 bytes from 66.60.188.248: icmp_seq = 9. time: 51 ms
44 bytes from 66.60.188.248: icmp_seq = 10. time: 44 ms
44 bytes from 66.60.188.248: icmp_seq = 11. time: 46 ms
44 bytes from 66.60.188.248: icmp_seq = 12. time: 64 ms
44 bytes from 66.60.188.248: icmp_seq = 13. time: 63 ms
44 bytes from 66.60.188.248: icmp_seq = 14. time: 81 ms
Finished.

One of the big routers on the east coast musta been down.

Seems like the problem is fixed now. Im on a full T-1 so the ping time still looks a little rough.

Tracing route to 66.60.188.13
50 bytes from 66.60.188.13: time=80 ms
Hop Avg Diff Address
1 10 10 ***MY IP**
2 30 20 64.211.111.57 s8-0-1-11-0.ar1.CLE1.gblx.net
3 95 65 206.132.111.121 pos2-0-155M.cr1.CLE1.gblx.net
4 145 50 206.132.110.94 pos0-0-622M.cr1.SFO1.gblx.net
5 220 75 206.132.110.178 pos0-1-0-155M.ar2.SFO1.gblx.net
6 130 -90 64.209.88.106 roseville-ld.atm8-1-0.ar2.SFO1.gblx.net
7 75 -55 208.45.228.240 7513-1.net.surewest.net
8 110 35 66.60.131.254 254.100MB.firstname.com
9 80 -30 66.60.188.13
host reached

____________________________________

ping 66.60.188.13 packet 1 round trip time = 130 ms. successful
ping 66.60.188.13 packet 2 round trip time = 131 ms. successful
ping 66.60.188.13 packet 3 round trip time = 150 ms. successful
ping 66.60.188.13 packet 4 round trip time = 321 ms. successful
ping 66.60.188.13 packet 5 round trip time = 100 ms. successful

You think they didn't plan that?

Maybe Lens is buying cheap bandwidth now?

It was a UUnet routing problem, they have been routed around. So any troubles today should now be over.

Thanks for the head's up.

Brad, I like my BW cheap like my women.