• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Giganews - Problems!

L

LarryS

Golden Member
Anyone having problems with Giganews lately? For the past two weeks I've been getting SLOW speeds.. IE - 250kbps. I emailed them twice and got a canned response about a bottleneck between me and them. Apparently it's affecting A LOT of people.

Anyone else?
 
Does this tell you anything? (I have no idea)


news-40.giganews.com
1 330.ge-4-2-0.mpr2.iah1.us.above.net (64.125.104.19) 0.878 ms 0.793 ms 0.715 ms
2 so-0-0-0.mpr1.iah1.us.above.net (64.125.31.61) 0.966 ms 0.776 ms 0.779 ms
3 pos2-0.er1.atl4.us.above.net (64.125.31.26) 13.499 ms 13.321 ms 13.352 ms
4 so-4-0-0.cr1.lga2.us.mfnx.net (208.184.232.166) 28.887 ms 28.738 ms 28.684 ms
5 so-0-0-0.cr1.lga1.us.mfnx.net (208.185.0.245) 28.793 ms 28.706 ms 28.682 ms
6 pos11-0.pr1.lga1.us.above.net (64.125.30.186) 28.751 ms 28.583 ms 28.629 ms
7 above-oc12.lga.att.net (64.125.12.106) 50.611 ms 50.671 ms *
8 tbr1-p012402.n54ny.ip.att.net (12.122.11.213) 48.930 ms 51.763 ms 50.299 ms
9 tbr1-cl8.phlpa.ip.att.net (12.122.2.18) 52.359 ms 53.131 ms 53.524 ms
10 gar3-p300.phlpa.ip.att.net (12.123.137.61) 52.417 ms 53.042 ms 50.546 ms
11 12.118.114.10 (12.118.114.10) 51.211 ms 52.716 ms 52.521 ms
12 68.87.16.10 (68.87.16.10) 55.336 ms 54.264 ms 54.280 ms
13 68.87.18.10 (68.87.18.10) 55.270 ms 55.230 ms 55.088 ms
14 68.46.145.5 (68.46.145.5) 50.604 ms 56.878 ms 54.306 ms
15 * 172.30.118.84 (172.30.118.84) 54.679 ms 53.354 ms
16 * * *
17 * * *
Max number of unresponsive hops reached (firewall or filter?)

news-60.giganews.com
1 gw2-vlan201.ash.giganews.com (216.196.98.3) 1 ms 0 ms 0 ms
2 ge-4-3-0.mpr1.iad10.above.net (209.249.11.97) 0 ms 0 ms 0 ms
3 so-4-0-0.mpr1.iad2.us.above.net (64.125.30.118) 0 ms 0 ms 0 ms
4 so-4-0-0.cr2.iad1.us.above.net (209.249.0.133) 0 ms 0 ms 0 ms
5 so-2-0-0.cr2.lga1.us.mfnx.net (208.184.233.66) 5 ms 4 ms 5 ms
6 pos1-0.pr1.lga1.us.mfnx.net (208.184.233.218) 4 ms 4 ms 4 ms
7 above-oc12.lga.att.net (64.125.12.106) 26 ms * 26 ms
8 tbr1-p011601.n54ny.ip.att.net (12.123.1.122) 25 ms 27 ms 27 ms
9 tbr1-cl8.phlpa.ip.att.net (12.122.2.18) 30 ms * 28 ms
10 gar3-p300.phlpa.ip.att.net (12.123.137.61) 27 ms 27 ms 29 ms
11 12.118.114.10 (12.118.114.10) 29 ms 28 ms 27 ms
12 68.87.16.10 (68.87.16.10) 30 ms 28 ms *
13 68.87.18.10 (68.87.18.10) 37 ms 28 ms 30 ms
14 * 68.46.144.165 (68.46.144.165) 34 ms 32 ms
15 * 172.30.118.84 (172.30.118.84) 29 ms 30 ms
16 * * *
Max number of unresponsive hops reached (firewall or filter?)
 
i had this exact problem a month ago with usenetserver, and they gave me the response you got - some bottleneck between your isp and their servers

i contacted my isp to let them know about it, maybe it was some security measure they recently implemented - whatever

its fine now though i dont know which end was the problem and which one fixed

so do what you can contacting ppl, but dont worry, if there are others like you it'll be fixed soon, after all they want you as a customer
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top