Euless,tx and possibly surrounding areas in AT&T Southwest

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 16:40:44 EDT

n5tkn : Hey, I was referred to this thread in response to my thread here »Increasing network latency/failures

David, I'm Jonesboro, AR, and this has been going on for me for almost a week or so now. Any ideas? Thanks! This also is a problem from my home DSL (which you helped me with last October, you probably remember me.) So its not site specific on my end, as far as I can tell.

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 13:14:17 EDT

David :

said by boeaya :

said by David :

You guys having any bandwidth troubles as of late?

Let's just say someone tipped off David 's scanners and he decided to crank them up a bit.

my dsl modem shows no connection last night and still out this morning in Euless,TX.

is the problem fixed? or is it my modem out of whack?

Possibly modem out of whack, I was mainly interested in the euless, tx area but I am glad some things came back to normal.
--
If you have a topic in the direct forum please reply to it or a post of mine, I get a notification when you do this.
Koetting Ford, Granite City, illinois... YOU'RE FIRED!!

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 13:06:10 EDT

koma3504 : I get packet loss here
ex3-p12-0.eqdltx.sbcglobal.net [69.220.8.53]

@ around 12:30 last night i could not get alot of websites including Dslr. I had some nice traceroutes and a nice ping plotter graph that I was going to post but i got up this am to find that @ 9:05 this morning somthing forced a reboot of my computer.

More websites i could not reach
Speakeasy speedtest speedtest.net yahoo.com cmt.com
www.pandora.com quit working.

I was also getting 100% packet loss @
151.164.243.97 bb2.10g3-0.rcsntx.sbcglobal.net

All of these had a ping time of 400ms and above when i could get a trace to trace.
3 bras30-l0.rcsntx.sbcglobal.net [75.11.245.198]
4 dist1-vlan120.rcsntx.sbcglobal.net [151.164.162.66]

5 151.164.93.188

This might shed some light on it.
Date: 07/18 00:00:52 Name: ICMP PING speedera
Priority: 3 Type: Misc activity
IP info: 76.203.230.232:n/a -> 99.157.25.172:n/a

Date: 07/17 20:50:13 Name: ICMP PING speedera
Priority: 3 Type: Misc activity
IP info: 99.1.109.70:n/a -> 99.157.25.172:n/a

Date: 07/17 21:02:29 Name: ICMP PING speedera
Priority: 3 Type: Misc activity
IP info: 99.148.164.49:n/a -> 99.157.25.172:n/a

Date: 07/17 21:35:13 Name: ICMP PING speedera
Priority: 3 Type: Misc activity
IP info: 76.203.226.229:n/a -> 99.157.25.172:n/a

Date: 07/17 17:37:58 Name: ICMP PING speedera
Priority: 3 Type: Misc activity
IP info: 99.1.111.131:n/a -> 99.157.25.172:n/a

Date: 07/17 12:08:32 Name: (portscan) UDP Portscan
Priority: n/a Type: n/a
IP info: 99.157.25.120:n/a -> 99.157.25.172:n/a

10:10:03 ppp0 » - UDP 99.157.25.120 1108 99.157.25.172
lookup block 99.157.25.172 161(SNMP)
10:10:24 ppp0 » - TCP 99.157.25.120 5000 99.157.25.172
lookup block 99.157.25.172 8080
10:10:37 ppp0 » - UDP 99.157.25.120 5000 99.157.25.172
lookup block 99.157.25.172 137(NETBIOS-NS)
10:10:37 ppp0 » - UDP 99.157.25.120 5000 99.157.25.172
lookup block 99.157.25.172 138(NETBIOS-DGM)

Date: 07/18 11:34:58 Name: DNS SPOOF query response with TTL of 1 min. and no authority
Priority: 2 Type: Potentially Bad Traffic
IP info: 208.67.220.220:53 -> 76.203.233.133:32768
References: none found

Date: 07/18 11:40:03 Name: DNS SPOOF query response with TTL of 1 min. and no authority
Priority: 2 Type: Potentially Bad Traffic
IP info: 208.67.220.220:53 -> 76.203.233.133:32768

--
† Koma †
If YOu Don't Think It's Possable!! It's Acually A Reality!!The best way to predict the future is to invent it. Alan Kay!!
Ya Don't Know The signal Till Ya Ride It!!
Voice Break's There's Trouble!!!!

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 10:21:01 EDT

boeaya :

said by David :

You guys having any bandwidth troubles as of late?

Let's just say someone tipped off David 's scanners and he decided to crank them up a bit.

my dsl modem shows no connection last night and still out this morning in Euless,TX.

is the problem fixed? or is it my modem out of whack?

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 09:02:50 EDT

nikertneca : Just watched stream from YouTube and CNN - both were ok. Here are some traceroutes I ran this morning:

Tracing route to www.l.google.com [64.233.167.147]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home
2 13 ms 84 ms 86 ms bras5-l0.rcsntx.sbcglobal.net [151.164.182.20]
3 10 ms 9 ms 9 ms dist2-vlan130.rcsntx.sbcglobal.net [151.164.162.131]
4 * 10 ms 11 ms bb2.10g3-0.rcsntx.sbcglobal.net [151.164.243.97]
5 34 ms 35 ms 33 ms 151.164.241.191
6 34 ms 35 ms 35 ms 151.164.251.226
7 34 ms 35 ms 34 ms 216.239.46.245
8 37 ms 61 ms 35 ms 66.249.94.133
9 36 ms 35 ms 35 ms 64.233.175.42
10 35 ms 37 ms 36 ms py-in-f147.google.com [64.233.167.147]
Trace complete.

Tracing route to www.mail.com [64.22.131.40]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home
2 13 ms 11 ms 11 ms bras5-l0.rcsntx.sbcglobal.net [151.164.182.20]
3 13 ms 11 ms 11 ms dist1-vlan120.rcsntx.sbcglobal.net [151.164.162.66]
4 10 ms 11 ms 9 ms bb1.10g5-0.rcsntx.sbcglobal.net [151.164.243.183]
5 * 12 ms 13 ms ex1-p2-0.eqdltx.sbcglobal.net [151.164.40.33]
6 12 ms 9 ms 11 ms gar6.dlstx.ip.att.net [12.122.79.65]
7 12 ms 11 ms 13 ms tbr1.dlstx.ip.att.net [12.123.16.218]
8 * 12 ms 13 ms ggr3.dlstx.ip.att.net [12.123.16.201]
9 13 ms 13 ms 13 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196.29]
10 45 ms 47 ms 46 ms cr2-pos-0-0-3-0.lay.savvis.net [204.70.203.50]
11 * 45 ms 43 ms pr2-so-1-0-0.losangelesequinix.savvis.net [204.70.203.49]
12 46 ms 46 ms 45 ms hr1-te-1-0-0.irvine2oc2.savvis.net [204.70.204.189]
13 46 ms 47 ms 46 ms ml1-rtr-pri-e.sav.irv.ptr.idpg.com [209.67.182.130]
14 45 ms 47 ms 47 ms ml1-fw-sec-e.sav.irv.ptr.idpg.com [216.177.65.93]
15 46 ms 46 ms 45 ms www.mail.com [64.22.131.40]
Trace complete.

Tracing route to www.yahoo-ht3.akadns.net [209.191.93.52]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home
2 13 ms 11 ms 11 ms bras5-l0.rcsntx.sbcglobal.net [151.164.182.20]
3 11 ms * 10 ms dist1-vlan120.rcsntx.sbcglobal.net [151.164.162.66]
4 10 ms 11 ms 9 ms 151.164.93.188
5 12 ms 11 ms 13 ms ex1-p2-1.eqdltx.sbcglobal.net [151.164.92.243]
6 12 ms 13 ms 11 ms asn10310-10-yahoo.eqdltx.sbcglobal.net [151.164.250.10]
7 13 ms 11 ms 11 ms ae1-p101.msr1.mud.yahoo.com [216.115.104.99]
8 27 ms 11 ms 11 ms te-9-1.bas-c1.mud.yahoo.com [68.142.193.9]
9 12 ms 11 ms 11 ms f1.www.vip.mud.yahoo.com [209.191.93.52]
Trace complete.

Tracing route to www.cnn.com [64.236.16.52]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home
2 13 ms 13 ms 11 ms bras5-l0.rcsntx.sbcglobal.net [151.164.182.20]
3 11 ms 11 ms 11 ms dist1-vlan120.rcsntx.sbcglobal.net [151.164.162.66]
4 10 ms 11 ms 9 ms bb1.10g5-0.rcsntx.sbcglobal.net [151.164.243.183]
5 11 ms 9 ms 11 ms ex2-p14-1.eqdltx.sbcglobal.net [151.164.242.42]
6 12 ms 13 ms 9 ms asn1668-aol.eqdltx.sbcglobal.net [151.164.248.70]
7 12 ms 13 ms 11 ms bb1-dls-p1-0.atdn.net [66.185.133.96]
8 51 ms 50 ms 52 ms bb1-atm-p7-0.atdn.net [66.185.152.184]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
...[more timeouts]
30 * * * Request timed out.
Trace complete.

Tracing route to lb1.www.ms.akadns.net [207.46.193.254]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home
2 13 ms 11 ms 11 ms bras5-l0.rcsntx.sbcglobal.net [151.164.182.20]
3 11 ms 11 ms 11 ms dist2-vlan120.rcsntx.sbcglobal.net [151.164.162.67]
4 11 ms 9 ms 9 ms bb2.10g3-0.rcsntx.sbcglobal.net [151.164.243.97]
5 46 ms 47 ms 46 ms 70.245.63.139
6 47 ms 46 ms 47 ms asn8075-microsoft.eqabva.sbcglobal.net [151.164.248.6]
7 47 ms 46 ms 47 ms 207.46.47.124
8 49 ms 48 ms 48 ms ge-7-1-0-0.blu-64c-1b.ntwk.msn.net [207.46.33.10]
9 101 ms 102 ms 100 ms ge-7-1-0-0.wst-64cb-1b.ntwk.msn.net [207.46.34.177]
10 99 ms 100 ms 100 ms ge-6-1-0-0.tuk-64cb-1b.ntwk.msn.net [207.46.35.33]
11 99 ms 100 ms 99 ms ten2-3.tuk-76c-1a.ntwk.msn.net [207.46.35.73]
12 96 ms 98 ms 97 ms po15.tuk-65ns-mcs-1a.ntwk.msn.net [207.46.35.138]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
...[more timeouts]
30 * * * Request timed out.
Trace complete.

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 03:26:11 EDT

powerspec88 : This is how long is was down here in KC.

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 03:14:05 EDT

ImTheWeasel : Indeed. Same here. Hardforum is back, but slow to XO dc. Several others slowly coming back to life.

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 03:13:14 EDT

powerspec88 : Everything is starting to work now, its a little slow to texas and i am having some packet loss. But it is getting better.

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 03:13:10 EDT

anon : I am just able to get back to a site hosted in the savvis dc in dallas, once again

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 03:07:54 EDT

ImTheWeasel : Well I was just now able to connect to all websites, and AIM came back up. Still showing router issues however...

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 03:02:30 EDT

powerspec88 : To dslreports.

C:\Documents and Settings\Admin>tracert dslreports.com Tracing route to dslreports.com [209.123.109.175]over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  192.168.1.1  2     1 ms    <1 ms    <1 ms  192.168.0.1  3     9 ms     9 ms     9 ms  ppp-70-252-149-254.dsl.ksc2mo.swbell.net [70.252.149.254]  4     9 ms     8 ms     9 ms  67.64.49.2  5     9 ms     9 ms     9 ms  bb2-tg3-0.ksc2mo.sbcglobal.net [151.164.40.233]   6    21 ms    21 ms    20 ms  ex2-p5-0.eqchil.sbcglobal.net [151.164.42.139]  7    42 ms    42 ms    42 ms  151.164.251.166  8    44 ms    44 ms    44 ms  so-5-1-0.nyc22.ip.tiscali.net [89.149.187.53]  9    47 ms    47 ms    47 ms  netaccess-gw.ip.tiscali.net [213.200.66.202] 10    43 ms    45 ms    44 ms  0.e1-1.tbr2.ewr.nac.net [209.123.10.133] 11    62 ms    46 ms    48 ms  0.e1-4.tbr2.oct.nac.net [209.123.10.126] 12    46 ms    46 ms    46 ms  vlan808.esd1.oct.nac.net [209.123.10.42] 13    44 ms    44 ms   279 ms  www.dslreports.com [209.123.109.175] Trace complete.

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 03:00:18 EDT

ImTheWeasel : Indeed.

Tracert to www.ktul.com;

gets to:

bb1-g5-0-0.tul2ok.sbcglobal.net (69.152.80.242)

then times out continually from there. IHR is showing KC to Chicago and Dallas suffering major failure.

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 02:59:13 EDT

TheWizardhfl : I'm over in Greenville, TX and we took a big hit tonight. I couldn't even get onto DSLReports. About 80% of the websites I tried to access wouldn't resolve and I lost connection to AIM, MSN, etc. I wasn't even able to load most of AT&T's website. Go figure.

I managed to get a hold of their online support, I didn't feel like sitting on hold for an hour to be told I had internet issues. According to the guy I spoke to,

quote:
Vince Stedman: There is an issue that we received regarding the state of Texas. Some members may experience Packet loss, or slow connection.

He gave me a set of DNS servers to try out while they worked on the issue:

quote:
Vince Stedman: Okay, under Primary DNS, please put in 68.94.156.1
Vince Stedman: Under Secondary 68.94.157.1
Vince Stedman: Also please try this as well Primary DNS: 68.94.156.1
Secondary DNS: 68.94.157.1

They didn't help much as far as speeding up the connection to the various websites, but at least a few of them will resolve now, like this one.

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 02:57:32 EDT

powerspec88 : We are having major problems here in KC (Raymore, MO area) Sites are not loading at all.

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 02:56:23 EDT

ImTheWeasel : Im in Bartlesville, Oklahoma. Certain sites will load others will not. No access to AIM, MSN works fine. Hardforum wont load, many others as well...

Looks like SBC/ATT Routers to Chicago and Dallas from Kansas City are experiencing major issues.

I called a spoke with ATT Engineering, they said they are looking into it...

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 02:48:21 EDT

anon : I'm out in far west texas (Presidio county). We have AT&T dsl here. We are not reaching much of the net right now (1:45 AM Central, Jul 18 2008)

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 02:42:09 EDT

shortkud : »www.internetpulse.net/ shows major issues with SBC.

Re: Euless,tx and possibly surrounding areas

Fri, 18 Jul 2008 01:20:45 EDT

David : Can you do some traceroutes for me? to say yahoo, google and such. Also try to watch some videos say on Youtube, Cnn or other news sites.

Re: Euless,tx and possibly surrounding areas

Thu, 17 Jul 2008 22:16:42 EDT

nikertneca : I'm having bandwidth issues in Bedford, which borders Euless. Any idea what's up?

Euless,tx and possibly surrounding areas

Thu, 17 Jul 2008 19:58:41 EDT

David : You guys having any bandwidth troubles as of late?

Let's just say someone tipped off David 's scanners and he decided to crank them up a bit.