That damn router in Atlanta for Mediaone/at&t broadband
-
iBringPain
I got it here
http://www.rocketdownload.com/Details/Util/visroute.htm
http://www.rocketdownload.com/Details/Util/visroute.htm
-
aldamon
Hey Azazel, I would appreciate it if you could send me that "patch" for VisualRoute as well.
aldamon@altavista.com
Hopefully I won't need the program anymore once RR fixes this fiasco, but I only have 13 days left on it.
Thanks!
BTW, I read this on USENET:
"Apparently the entire Charlotte NC area has had poor bandwidth every night and weekend for 3 months because of router 24.88.3.149 which is in a smaller city. They must be slamming all regional RR traffic through it. We're getting slower than 56k dialup! Numerous complaints to Roadrunner Charlotte and they say it's out of their hands and only the national Roadrunner people can fix it. But they claimed it would be fixed by now and it isn't. Now someone contacted city council and folks on our local Roadrunner newsgroup are emailing complaints to their person in charge of cable contracts. She says she is working to resolve the problem and has contacted the local manager of Time Warner, as well as filing a formal complaint with Time Warner."
Hmmmm, now I see why we have such a complex explanation in NC....I knew that RR wouldn't get off its ass until people filed an official complaint. This probably could have been resolved weeks ago...
[This message has been edited by aldamon (edited 10-02-2000).]
aldamon@altavista.com
Hopefully I won't need the program anymore once RR fixes this fiasco, but I only have 13 days left on it.
Thanks!
BTW, I read this on USENET:
"Apparently the entire Charlotte NC area has had poor bandwidth every night and weekend for 3 months because of router 24.88.3.149 which is in a smaller city. They must be slamming all regional RR traffic through it. We're getting slower than 56k dialup! Numerous complaints to Roadrunner Charlotte and they say it's out of their hands and only the national Roadrunner people can fix it. But they claimed it would be fixed by now and it isn't. Now someone contacted city council and folks on our local Roadrunner newsgroup are emailing complaints to their person in charge of cable contracts. She says she is working to resolve the problem and has contacted the local manager of Time Warner, as well as filing a formal complaint with Time Warner."
Hmmmm, now I see why we have such a complex explanation in NC....I knew that RR wouldn't get off its ass until people filed an official complaint. This probably could have been resolved weeks ago...
[This message has been edited by aldamon (edited 10-02-2000).]
-
Kip Patterson
You guys are really getting a bad deal, and ought to be complaining. To make it the most effective, you might want to note a couple of pints:
1) The router in question is not very apt to be in Herndon, VA. There is no location listed for it in the database. Your traceroute programs are displaying the address of Roadrunner as their best guess.
2) The problem is not in a router. If you try traceroutes from some of the mirror sites that happen to come at it from another direction the response time is fine. The router is doing exactly what it is supposed to do - queue up the packets, which causes all the TCP/IP connections using that router to slow down to match the capacity of the circuit.
The problem is an overloaded circuit. There's only a few folks that actually own fiber - everybody else is dependant upon them for their connections. If you want to blame somebody, blame the Communication Wrokers of America - they're the ones that went on strike. No amount of complaining to local cable authorities is going to do anything but frustrate RR while they're sitting there waiting just like you.
1) The router in question is not very apt to be in Herndon, VA. There is no location listed for it in the database. Your traceroute programs are displaying the address of Roadrunner as their best guess.
2) The problem is not in a router. If you try traceroutes from some of the mirror sites that happen to come at it from another direction the response time is fine. The router is doing exactly what it is supposed to do - queue up the packets, which causes all the TCP/IP connections using that router to slow down to match the capacity of the circuit.
The problem is an overloaded circuit. There's only a few folks that actually own fiber - everybody else is dependant upon them for their connections. If you want to blame somebody, blame the Communication Wrokers of America - they're the ones that went on strike. No amount of complaining to local cable authorities is going to do anything but frustrate RR while they're sitting there waiting just like you.
-
Merc
-
Merc
-
aldamon
-
Merc
ok my email is blachaze@mediaone.net
update!!!!
Road Runner customers may experience slow browsing/latency outside of the Road Runner Network when visiting certain web sites, especially during peak usage times. The slow browsing is occurring in all of North Carolina, South Carolina and the Atlanta metropolitan area. We will be adding additional circuits in the coming days to alleviate this issue, starting with an OC3 that will provide a significant increase in bandwidth out of North Carolina and onto the Internet. Cable & Wireless is currently testing this circuit and it should be fully functional by this Friday, 10/6/00. We are still waiting for firm dates on other circuits from AT&T which will also increase bandwidth onto the Internet. We apologize for any inconvenience this may cause. Please check this page for daily updates on this issue.
there ya go guys :-)
Road Runner customers may experience slow browsing/latency outside of the Road Runner Network when visiting certain web sites, especially during peak usage times. The slow browsing is occurring in all of North Carolina, South Carolina and the Atlanta metropolitan area. We will be adding additional circuits in the coming days to alleviate this issue, starting with an OC3 that will provide a significant increase in bandwidth out of North Carolina and onto the Internet. Cable & Wireless is currently testing this circuit and it should be fully functional by this Friday, 10/6/00. We are still waiting for firm dates on other circuits from AT&T which will also increase bandwidth onto the Internet. We apologize for any inconvenience this may cause. Please check this page for daily updates on this issue.
there ya go guys :-)
-
aldamon
Thanks for clarification Kip, but RR provides NETWORK STATUS PAGES so we can monitor NETWORK STATUS. This problem has been present for weeks yet RR posted no updates. Only after people "complained to local authorities" did RR seem interested in keeping its customer based truly informed about NETWORK STATUS.Originally posted by Kip Patterson:
You guys are really getting a bad deal, and ought to be complaining. To make it the most effective, you might want to note a couple of pints:
1) The router in question is not very apt to be in Herndon, VA. There is no location listed for it in the database. Your traceroute programs are displaying the address of Roadrunner as their best guess.
2) The problem is not in a router. If you try traceroutes from some of the mirror sites that happen to come at it from another direction the response time is fine. The router is doing exactly what it is supposed to do - queue up the packets, which causes all the TCP/IP connections using that router to slow down to match the capacity of the circuit.
The problem is an overloaded circuit. There's only a few folks that actually own fiber - everybody else is dependant upon them for their connections. If you want to blame somebody, blame the Communication Wrokers of America - they're the ones that went on strike. No amount of complaining to local cable authorities is going to do anything but frustrate RR while they're sitting there waiting just like you.
I understand that RR is in a pickle, but for weeks I saw no status updates on their page, only more "sign up now" commercials so more people could dilute our precious bandwidth. It is frustrating situation that could have been handled better with a little more communication.
-
aldamon
Hey Azazel, you might want to crop and JPEG your screenshots before posting....we are bandwidth starved you knowOriginally posted by Azazel:
as promised here is a tracert to yahoo.com
I see that our favorite router isn't there anymore yet still we get bad pings....not as bad as we used to though so that shows that they are trying at least.
-
Kip Patterson
-
aldamon
Keep us posted about what happens at the meeting. I'm interested in hearing what the suits have to say about RR's future since they obviously can't keep up with demand in a timely fashion.Originally posted by Kip Patterson:
For aldamon:
Boy, are you right about the status pages. Here in Columbus the page is always out of date, and I'm never quite sure what language it is in. Not the English I know, that's for sure.
Time Warner is hosting a public meeting a week from tomorrow. Should be interesting.
I know At&t can still use the RR network to shove it's mediaone ppl thru till like 2002 or something near that which is their deadline to decide that after mediaone is out of it's contract with road runner what to do as far as the network is concerned. I wonder if the mediaone ppl are gonna get shoved into at&t's @home network(that should be painfully interesting to watch) and will we get the same caps that their customers are currently getting their or will we get shoved back into the RR pipe which at&t can do by renting the lines from RR are we going to stay at the current caps that we are currently paying for and go thru RR's faulty network that makes 4 states in the south east share basically the same pipe therefore when something occurs it slows down everyone going through there. I well just somethings I have been pondering
.
-
30thAnnZ
I quit working for RR over several things, but this was a main one... I got really tired of the BS over and over again. Don't get me wrong, I'm not a gamer, and this problem was little more than an inconvenience to me during times when I was rarely online anyway, but I got tired of the way the Tier 1 techs were treated over this.
In a nutshell, they really wouldn't (or couldn't actually, on the local level at least) tell us anything, and expected us to basically "say whatever" to the customer and just deal with it...
I didn't like that. I also didn't like the fact that when these problems first started popping up, we were told that they would be fixed "in two weeks" but not to tell the customers that. Those two weeks turned into four, then six, then eight.
I don't mind helping customers out with their problems, and I can understand the customers being upset over this, but I just couldn't deal with 99% of the customers being angry about something that I had no control over and that I was given absolutely no information about.
Once again, I didn't blame the customers. As a matter of fact I completely agreed with them.
It was just sorry. That's all. Sorry.
[This message has been edited by 30thAnnZ (edited 10-03-2000).]
In a nutshell, they really wouldn't (or couldn't actually, on the local level at least) tell us anything, and expected us to basically "say whatever" to the customer and just deal with it...
I didn't like that. I also didn't like the fact that when these problems first started popping up, we were told that they would be fixed "in two weeks" but not to tell the customers that. Those two weeks turned into four, then six, then eight.
I don't mind helping customers out with their problems, and I can understand the customers being upset over this, but I just couldn't deal with 99% of the customers being angry about something that I had no control over and that I was given absolutely no information about.
Once again, I didn't blame the customers. As a matter of fact I completely agreed with them.
It was just sorry. That's all. Sorry.
[This message has been edited by 30thAnnZ (edited 10-03-2000).]
hey man I understand where you're coming from that's why I never get mad at tech support cause most of the time they don't know what's going on. I get pissed at the ppl that work on the networks and keep up with things with not informing us about the problems occuring. I mean if you are having a serious problem "state it from the beginning" don't just try to sugar coat it telling us it'll be fixed by this and this date cause when that date comes up and it's not fixed it's just going to light more fuel to the fire. I sympathize with ya and know that it's hard to go under the customer firing squad when you can't do anything to affect the problem. What I believe is those anti social network admins need to get someone to give the customers an update on the webpage(which not many companies do well) or let the techs know whats going on and tell let them inform the customers on the problem yes the customers will get angry but at least they aren't left in the blue.
well just my two cents on the situation.
well just my two cents on the situation.
-
aldamon
Gentlemen, it is 8:00 PM EST and life is GOOD in NC now. Tracert to yahoo:
Tracing route to www.yahoo.akadns.net [216.32.74.50]
over a maximum of 30 hops:
1 8 ms 8 ms 8 ms 10.25.18.1
2 7 ms 8 ms 8 ms 24.25.1.25
3 7 ms 10 ms 7 ms 24.93.64.97
4 20 ms 35 ms 18 ms 24.93.64.45
5 18 ms 21 ms 24 ms pos0-1.hrndva1-brt1.rr.com [24.128.6.2]
6 19 ms 23 ms 21 ms pos1-0.hrndva1-brt2.rr.com [24.218.188.186]
7 67 ms 68 ms 67 ms pos0-2.vinnva1-brt3.rr.com [24.218.188.158]
8 30 ms 32 ms 37 ms srp3-0.vinnva1-brt1.rr.com [24.218.189.166]
9 104 ms 103 ms 106 ms pos1-1.plalca1-brt3.rr.com [24.218.188.217]
10 104 ms 104 ms 104 ms srp3-0.plalca1-brt2.rr.com [24.218.189.197]
11 107 ms 106 ms 106 ms rr-px.paix.core.exodus.net [209.185.249.33]
12 106 ms 109 ms 111 ms bbr01-p2-0.sntc03.exodus.net [209.1.169.22]
13 108 ms 110 ms 107 ms bbr02-g3-0.sntc03.exodus.net [216.33.153.2]
14 95 ms 98 ms 99 ms bbr01-p2-0.stng01.exodus.net [209.1.169.166]
15 96 ms 98 ms 100 ms dcr04-g10-0.stng01.exodus.net [216.33.96.162]
16 101 ms 95 ms 96 ms csr22-ve241.stng01.exodus.net [216.33.98.11]
17 97 ms 99 ms 97 ms 216.35.210.122
18 98 ms 99 ms 98 ms www.yahoo.akadns.net [216.32.74.50]
Trace complete.
OH YEAH!!!!
Updated message from NC RR:
Internet Access: Road Runner customers may experience slow browsing/latency outside of the Road Runner Network when visiting certain web sites, especially during peak usage times. The slow browsing is occurring in all of North Carolina, South Carolina and the Atlanta metropolitan area. We are adding additional circuits to alleviate this issue, starting with an OC3 that will provide a significant increase in bandwidth exiting out of North Carolina and onto the Internet. Cable & Wireless is currently testing this circuit and we expect it to be fully functional by this Friday, 10/6/00. A DS3 circuit was installed in Charlotte, further alleviating the bandwidth crunch, thus providing more exit bandwidth to Raleigh area customers. We are also adding more circuits that will not only provide more bandwidth in the short term, they will ensure fast speed well into the foreseeable future. We apologize for any inconvenience this may cause. Please check this page for daily updates on this issue.
Things are going to get even better....
[This message has been edited by aldamon (edited 10-03-2000).]
Tracing route to www.yahoo.akadns.net [216.32.74.50]
over a maximum of 30 hops:
1 8 ms 8 ms 8 ms 10.25.18.1
2 7 ms 8 ms 8 ms 24.25.1.25
3 7 ms 10 ms 7 ms 24.93.64.97
4 20 ms 35 ms 18 ms 24.93.64.45
5 18 ms 21 ms 24 ms pos0-1.hrndva1-brt1.rr.com [24.128.6.2]
6 19 ms 23 ms 21 ms pos1-0.hrndva1-brt2.rr.com [24.218.188.186]
7 67 ms 68 ms 67 ms pos0-2.vinnva1-brt3.rr.com [24.218.188.158]
8 30 ms 32 ms 37 ms srp3-0.vinnva1-brt1.rr.com [24.218.189.166]
9 104 ms 103 ms 106 ms pos1-1.plalca1-brt3.rr.com [24.218.188.217]
10 104 ms 104 ms 104 ms srp3-0.plalca1-brt2.rr.com [24.218.189.197]
11 107 ms 106 ms 106 ms rr-px.paix.core.exodus.net [209.185.249.33]
12 106 ms 109 ms 111 ms bbr01-p2-0.sntc03.exodus.net [209.1.169.22]
13 108 ms 110 ms 107 ms bbr02-g3-0.sntc03.exodus.net [216.33.153.2]
14 95 ms 98 ms 99 ms bbr01-p2-0.stng01.exodus.net [209.1.169.166]
15 96 ms 98 ms 100 ms dcr04-g10-0.stng01.exodus.net [216.33.96.162]
16 101 ms 95 ms 96 ms csr22-ve241.stng01.exodus.net [216.33.98.11]
17 97 ms 99 ms 97 ms 216.35.210.122
18 98 ms 99 ms 98 ms www.yahoo.akadns.net [216.32.74.50]
Trace complete.
OH YEAH!!!!
Updated message from NC RR:
Internet Access: Road Runner customers may experience slow browsing/latency outside of the Road Runner Network when visiting certain web sites, especially during peak usage times. The slow browsing is occurring in all of North Carolina, South Carolina and the Atlanta metropolitan area. We are adding additional circuits to alleviate this issue, starting with an OC3 that will provide a significant increase in bandwidth exiting out of North Carolina and onto the Internet. Cable & Wireless is currently testing this circuit and we expect it to be fully functional by this Friday, 10/6/00. A DS3 circuit was installed in Charlotte, further alleviating the bandwidth crunch, thus providing more exit bandwidth to Raleigh area customers. We are also adding more circuits that will not only provide more bandwidth in the short term, they will ensure fast speed well into the foreseeable future. We apologize for any inconvenience this may cause. Please check this page for daily updates on this issue.
Things are going to get even better....
[This message has been edited by aldamon (edited 10-03-2000).]
-
Kip Patterson
I can't resist pointing out the clarity with which someone at RR wrote that message.
Let me give you a comparison:
9/28/00 10:30am all roadrunner buisness customers in columbus were unable to access there email accounts, this was a intermittent problem due to equipment problems...#31525
One misspelled word, one comma splice, one incorrect word, 3 instances of missing capitalization.
Pardon the lecture, but these things count in the business world.
Let me give you a comparison:
9/28/00 10:30am all roadrunner buisness customers in columbus were unable to access there email accounts, this was a intermittent problem due to equipment problems...#31525
One misspelled word, one comma splice, one incorrect word, 3 instances of missing capitalization.
Pardon the lecture, but these things count in the business world.
-
30thAnnZ
-
Kip Patterson
-
64bit
Well I know how you guys down south feel. The phantom number 5 is 24.131.0.105 and anything through that thing well as you can see it drops everything. I have had this service for a year now and they always keep saying(mw.mediaone.net)the problem will be fixed in the coming weeks. Now they say they will not take on any new subcribers till the problem is fixed. YA RIGHT
p.s. hey Azazel can ya find it in your heart to send that "fix" this way. bigreasy@hotmail.com
[This message has been edited by 64bit (edited 10-04-2000).]
[This message has been edited by 64bit (edited 10-04-2000).]