| [Speed Problem] Problem in the AT&T GA Data Center? Its not my I've been having a problem with my connection for the past several days. It started we think on 7/14 as our connection became very slow. I called AT&T support and they say its my modem....the problem is I have a secondary modem, tried it and same problem.
So here is why I'm asking of this is a problem in the data center. I've used various tools (PingPlotter, as well as some of the tools on this site) and am seeing that the data is leaving my network, but I get dropped packets it appears after I hit the next hop after 68.208.254.4. Typically the network trace works for a while then packets start dropping and its ALWAYS after that router no matter what endpoint I am pinging. I've been using the following four targets: download.cnet.com, www.pingplotter.com, www.google.com and 206.16.60.41 (High Tech Creations / Aces High 2 server). The drops happen every few minutes and last for up to a minute. |
|
| Re: [Speed Problem] Problem in the AT&T GA Data Center? Its not I few other items to note:
1.) This doesn't appear to be a PPPoE issue - I've seen nothing in my firewall logs indicating authentication or problems getting to the auth servers.
2.) the path my packets are taking change for a specific destination. I realize this can happen, but the one path that appears to be the most problematic deal with paths that take 74.253.202.21 as the next hop after 68.208.254.4. |
|
 graysonfPremium,MVM
join:1999-07-16
Fort Lauderdale, FL | reply to KeithVaughan
You should try a simpler tool between you and your gateway first.
Assuming you have Windows, then open a command prompt and enter:
ping -t a.b.c.d
where a.b.c.d is your next hop past your modem - d is almost always a 1.
Watch it for a while.
If your ATM link between you and the ISP ingress router is hosed, you'll see frequent intermittent packet loss. |
|
| I've actually been trying that very apprach. The next hop after the internal interface of my firewall (192.168.100.254) is 68.208.254.4, which geotraces to somewhere in Atlanta. Pings to that address do not drop and are typically between 7 and 8 ms (the odd ping goes from 15 to 100ms but that's very infrequent). I'm wondering if that is the "ISP facing" address of the DSL modem given the low latency, in which case it may well be my modem.
My firewall does the PPPoE auth and gets my static ISP assigned IP so I'm not sure if the DSL modem actually gets an IP given my setup. Sorry, I'm a system admin..not much on telco / DSL tech. |
|
graysonfPremium,MVM
join:1999-07-16
Fort Lauderdale, FL | Your public IP address can be determined by going to a host such as
»checkip.dns.he.net/
7 to 8 ms is way too long to be your modem. It would be an excellent time to reach your ISP gateway though.
Your "modem" is doing NAT, so your public IP is on the modem and can be determined as above or by looking on its WAN status page.
Geotrace returned data is often questionable. The whois data below makes more sense.
BellSouth.net Inc. BELLSNET-BLK11 (NET-68-208-0-0-1) 68.208.0.0 - 68.223.255.255
CLT-BMF Charlotte BLS-68-208-254-0-1006150909 (NET-68-208-254-0-1) 68.208.254.0 - 68.208.255.255 |
|
| I know my PublicIP, and that address isnt it. I just wasnt sure if my modem itself was also getting an IP.
Still seems like an issue with either the line (which AT&T says is "clean") or somewhere upstream. What's leading me to believe that is that I am now continually pinging the next hop (68.208.254.4) and the two addresses after that hop that appear whenever I do a traceroute (68.208.254.85 and 74.253.202.21). I've not had a single packet drop to any of those hosts, the latency is about 7 to 8 ms for all three (with the odd packet coming in at 10-15 every few minutes). That doesnt add up to me to a problem with my modem as the AT&T tech support call tried to give me. |
|
| "I know my PublicIP, and that address isnt it."
Just reread my post and its confusing....just to clarify, by "that address" I meant 68.208.254.4 is not my assigned static IP so I know its not my firewall's external interface. What I meant was I wasnt sure if it was my modem's address. |
|
graysonfPremium,MVM
join:1999-07-16
Fort Lauderdale, FL | The problem is either within the AT&T network or beyond it. AT&T can not solve problems beyond their network.
Not much you can do other than report the problem to AT&T if it's within their network. Once you have ruled out problems before your first hop, you can ignore AT&T suggestions that it's your modem, and tell them why you intend to ignore them. That puts the ball in their court and it's up to them to either solve the problem or drop the ball. |
|
| reply to KeithVaughan
I have been having problems as well with games and I know its not my modem cause it is only a month old. I have been running trace rt at the time when I have a high ping in games and it all ways point at the data center in GA. I also get lost packets from them as well. This is during none peak time. |
|
cubguy
join:2010-07-09
Greenwood Springs, MS | Lost,
I am sure you probably feed thru the same ingress router that I do (I am outside Aberdeen)...Most of the time we go to (98.95.147.1) adsl.jan.bellsouth.net, which then reroutes thru the data center on registered on Mornosgo in Atlanta. I have noticed the same slow down this week on games. The latency seems to be alot higher. I know they are doing so fiber lays nearby so I am not sure if that is the problem, or if they are moving us to different nodes to spread out the traffic. Can anyone shed any light on this subject? |
|
 Hayward K A R - 1 2 0 CPremium
join:2000-07-13
Key West, FL
kudos:1
1 edit | reply to lostinms
said by lostinms:I have been having problems as well with games and I know its not my modem cause it is only a month old.
What makes you so sure, if not tested or another modem tried?
MOST electronics that do fail will in 30-90 days which is why a 90 day vs 1 year warranty is really not that big a deal. This is especially true for always on or high use electronics.
At a year it is more likely a physical failure, like switches, keyboard, HDD, etc.
--
|
|
| because if it was the modem then it would appear more at the 1st and 2nd hop not all the way in the 13th hop.
Most of the issue is around ip address 12.123.22.153 attga02jt.ip.att.net I get some packet loss there allot usually around 10 to 20%
There is also 80.91.246.76 ash-bb1-link.telia.net that I get packet loss and ping errors from.
It is those to that really make video watching and gaming horrible. This happens during the day and nights.
|
|
Hayward K A R - 1 2 0 CPremium
join:2000-07-13
Key West, FL
kudos:1 | said by lostinms:because if it was the modem then it would appear more at the 1st and 2nd hop not all the way in the 13th hop.
Most of the issue is around ip address 12.123.22.153 attga02jt.ip.att.net I get some packet loss there allot usually around 10 to 20%
OK well you gave no real detail before just can't be because its on a month old.
--
|
|
