sortofageek
Premium,Mod
join:2001-08-19
Valhalla Dr
clubs: | reply to JeepMatt
Re: [Connectivity] Philly Router is Bombing tonight..
Possibly related topics:
»[Split] High Pings in Philadelphia, PA
» [Split] More High Pings in Philadelphia, PA |
|
RdKryton
Premium
join:2002-03-17
Downingtown, PA
 ·Comcast
| reply to JeepMatt
Maybe for you it is better but....
7 12 ms 43 ms 13 ms po90-ar01.401nbroadst.pa.panjde.comcast.net [68.86.208.29]
8 54 ms 113 ms 61 ms 68.86.211.14
9 94 ms 219 ms 64 ms 12.119.53.53
10 84 ms 84 ms 100 ms tbr2-p012401.phlpa.ip.att.net [12.123.137.49]
11 75 ms 76 ms 77 ms tbr1-cl9.wswdc.ip.att.net [12.122.2.85]
12 99 ms 128 ms 158 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
13 175 ms 113 ms * tbr2-cl2.sffca.ip.att.net [12.122.10.42]
14 73 ms 76 ms 123 ms 12.123.13.178
15 100 ms 122 ms 146 ms idf22-gsr12-1-pos-7-0.rwc1.attens.net [12.122.255.218]
16 119 ms 98 ms 183 ms rwcsbix12-3-1.attbi.com [63.241.85.242]
17 * * * Request timed out.
18 167 ms 98 ms 80 ms www.comcast.net [216.148.227.202]
--
Stop yelling at me! I'm stupid not deaf.... |
|
swagdogpsu69
join:2006-04-01
Harrisburg, PA | reply to JeepMatt
Well praise the lord.......let me do the jig |
|
JeepMatt
Delaware Fios
Premium
join:2001-12-28
Wilmington, DE
 ·Verizon FIOS
1 edit | reply to lshale
It looks like the Philly area ATT routers are now back online. This "should" alleviate all issues.
My reverse route now shows the St Louis - DC - Philly routing as it was before the mess last Thursday.
8 tbr2-cl21.sl9mo.ip.att.net (12.122.10.13) 72.694 ms 68.283 ms 70.124 ms
9 tbr1-cl24.sl9mo.ip.att.net (12.122.9.141) 69.664 ms 67.877 ms 67.692 ms
10 tbr1-cl4.wswdc.ip.att.net (12.122.10.29) 67.8 ms 68.483 ms 68.585 ms
11 tbr2-cl9.phlpa.ip.att.net (12.122.2.86) 68.705 ms 67.826 ms 67.769 ms
12 gar2-p390.phlpa.ip.att.net (12.123.137.50) 67.923 ms 67.996 ms 67.425 ms
13 12.119.53.54 (12.119.53.54) 67.065 ms 144.434 ms 66.903 ms
14 68.87.16.1 (68.87.16.1) 67.546 ms 101.309 ms 67.728 ms
15 te-8-3-ar01.plainfield.nj.panjde.comcast.net (68.86.211.5) 68.629 ms 67.542 ms 67.471 ms
16 po80-ar01.audubon.nj.panjde.comcast.net (68.86.208.2) 70.101 ms 70.294 ms 70.151 ms
17 po10-ar01.wallingford.pa.panjde.comcast.net (68.86.208.26) 72.378 ms 71.472 ms 71.267 ms
18 po90-ur02.norristown.pa.panjde.comcast.net (68.86.209.105) 75.529 ms 75.101 ms 73.964 ms
19 po90-ur01.norristown.pa.panjde.comcast.net (68.86.209.101) 74.889 ms 76.992 ms 74.018 ms
20 po90-ur01.claymont.de.panjde.comcast.net (68.86.209.97) 76.116 ms 75.099 ms 75.139 ms
21 ge-0-1-ubr01.claymont.de.panjde.comcast.net (68.86.216.214) 76.149 ms 76.573 ms 76.19 ms
--
"ONE team - ONE city - ONE dream!!" |
|
lshale
join:2004-07-16
Newark, DE
| reply to JeepMatt
From Newark, DE: I have been noticing the same slowdowns over the past few days so I called Comcast last night and told them about the problem. They did a test and agreed that the ping rates were terrible for me and want to send someone out to my house to check the line. At the time, I was getting speed results of under 1000kbps down. At 4 AM this morning, I am at 8456/354. I will watch it and see what happens as I am betting it will get worse as the day goes on.
1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 7 ms 6 ms 7 ms ge-9-2-ur01.frenchtown.de.panjde.comcast.net [68
.86.217.9]
4 12 ms 9 ms 7 ms ge-9-24-ur01.uofdelaware.de.panjde.comcast.net [
68.86.209.113]
5 7 ms 7 ms 8 ms ge-2-24-ur01.limstonedr.de.panjde.comcast.net [6
8.86.209.109]
6 9 ms 13 ms 9 ms te-9-1-ur02.coatesville.pa.panjde.comcast.net [6
8.86.209.77]
7 14 ms 12 ms 8 ms te-9-1-ur01.coatesville.pa.panjde.comcast.net [6
8.86.209.73]
8 8 ms 9 ms 11 ms po80-ar01.coatesville.pa.panjde.comcast.net [68.
86.209.69]
9 9 ms 9 ms 9 ms po90-ar01.wallingford.pa.panjde.comcast.net [68.
86.208.37]
10 10 ms 9 ms 11 ms po90-ar01.401nbroadst.pa.panjde.comcast.net [68.
86.208.29]
11 14 ms 14 ms 14 ms 68.86.211.14
12 15 ms 14 ms 13 ms 12.119.53.49
13 15 ms 16 ms 16 ms mdf1-gsr12-1-pos-6-0.nyc3.attens.net [12.122.255
.126]
14 16 ms 16 ms 38 ms sccsbix11-1-4.attbi.com [63.240.64.34]
15 * * * Request timed out.
16 * * * Request timed out.
17 15 ms 14 ms 14 ms www.comcast.net [63.240.76.72] |
|
actor90
Never a dull moment
Premium
join:2003-07-21
L.E.H.T., NJ
·Comcast
| reply to JeepMatt
I am having the same issues to, I created a poll on the AT&T backbone here:
»[Connectivity] Poll Should Comcast get rid of the AT&T backbone?
Hopefully, someone at Comcast will actually pay attention to what is going on. I'm reminded of the new Comcast commercial with the turtles, talking about how Comcast is too fast and DSL is slow and perfect. I imagine tonight DSL is faster in the North East then Comcast, It's Comcastic! What will it take for Comcast to turn up the heat on AT&T?
--
Whatever doesn't kill us, makes us stronger... |
|
docshawnc
join:2000-12-14
Blue Bell, PA
| reply to JeepMatt
This problem is not going away and it doesn't look like comcast is even concerned about approaching ATT (it's their POS router causing the problem) - This has been a problem since Thurs
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
H:\>tracert www.comcast.com
Tracing route to www.comcast.com [164.109.28.3]
over a maximum of 30 hops:
1 2 ms 1 ms 3 ms 192.168.1.1
2 * * * Request timed out.
3 14 ms 10 ms 11 ms ge-2-2-ur01.norristown.pa.panjde.comcast.net [68
.86.216.237]
4 10 ms 14 ms 13 ms po10-ur02.norristown.pa.panjde.comcast.net [68.8
6.209.102]
5 15 ms 15 ms 14 ms po21-ar01.wallingford.pa.panjde.comcast.net [68.
86.209.106]
6 17 ms 29 ms 33 ms po90-ar01.401nbroadst.pa.panjde.comcast.net [68.
86.208.29]
7 18 ms 19 ms 18 ms 68.86.211.14
8 252 ms 254 ms 279 ms 12.119.53.49
9 266 ms 281 ms 271 ms tbr1-p012401.phlpa.ip.att.net [12.123.137.45]
10 272 ms 279 ms 267 ms tbr1-cl8.n54ny.ip.att.net [12.122.2.17]
11 277 ms 267 ms 269 ms ggr3-g00.n54ny.ip.att.net [12.123.0.97]
12 270 ms 265 ms 285 ms att-gw.dc.aol.com [192.205.32.2]
13 255 ms 260 ms 261 ms 0.so-6-0-0.XL1.NYC4.ALTER.NET [152.63.21.78]
14 270 ms 285 ms 272 ms 0.so-6-0-0.XL1.DCA6.ALTER.NET [152.63.38.70]
15 286 ms 311 ms 280 ms 0.so-6-0-0.GW6.DCA6.ALTER.NET [152.63.41.221]
16 284 ms 261 ms 260 ms digex-gw.customer.alter.net [157.130.214.102]
17 288 ms 294 ms 281 ms 164.109.3.218
18 284 ms 271 ms 276 ms 164.109.31.219
19 276 ms 283 ms 282 ms 164.109.28.3
Trace complete.
btw, I'm over in Blue Bell not trenton as it say under my name - time to fix that |
|
JeepMatt
Delaware Fios
Premium
join:2001-12-28
Wilmington, DE
·Verizon FIOS
1 edit | reply to chris2topher
Looks like it's all about the reverse route again - I'm on different IP's for those NY area ATT.net hops - and haven't had an issue since Thursday night...
1 v253-gw.usc.edu (128.125.253.254) 0.459 ms 0.288 ms 0.278 ms
2 v251-gw-19.usc.edu (128.125.251.155) 0.3 ms 0.284 ms 0.29 ms
3 130.152.181.129 (130.152.181.129) 0.217 ms 0.274 ms 0.195 ms
4 198.172.117.161 (198.172.117.161) 0.581 ms 0.85 ms 0.63 ms
5 xe-1-0-0.r20.lsanca03.us.bb.verio.net (129.250.5.32) 0.578 ms 0.546 ms 0.525 ms
6 p16-0.att.lsanca03.us.bb.verio.net (129.250.9.110) 0.66 ms 0.639 ms 0.817 ms
7 12.123.222.22 (12.123.222.22) 69.419 ms 69.167 ms 69.956 ms
8 tbr2-cl21.sl9mo.ip.att.net (12.122.10.13) 88.881 ms 69.664 ms 69.511 ms
9 tbr2-cl7.cgcil.ip.att.net (12.122.10.45) 71.028 ms 70.407 ms 70.815 ms
10 tbr1-cl22.cgcil.ip.att.net (12.122.9.133) 70.261 ms 72.903 ms 70.175 ms
11 tbr1-cl14.n54ny.ip.att.net (12.122.10.1) 71.182 ms 70.395 ms 71.256 ms
12 gar5-p300.n54ny.ip.att.net (12.123.3.9) 69.289 ms 69.222 ms 70.017 ms
13 12.118.149.10 (12.118.149.10) 69.674 ms 69.78 ms 70.699 ms
14 te-8-3-ar01.plainfield.nj.panjde.comcast.net (68.86.211.5) 70.622 ms 70.679 ms 70.575 ms
15 po80-ar01.audubon.nj.panjde.comcast.net (68.86.208.2) 73.942 ms 73.822 ms 72.919 ms
16 po10-ar01.wallingford.pa.panjde.comcast.net (68.86.208.26) 73.723 ms 72.883 ms 73.096 ms
17 po90-ur02.norristown.pa.panjde.comcast.net (68.86.209.105) 77.213 ms 76.174 ms 76.256 ms
18 po90-ur01.norristown.pa.panjde.comcast.net (68.86.209.101) 75.636 ms 75.608 ms 75.611 ms
19 po90-ur01.claymont.de.panjde.comcast.net (68.86.209.97) 77.672 ms 76.903 ms 77.015 ms
20 ge-0-1-ubr01.claymont.de.panjde.comcast.net (68.86.216.214) 78.916 ms 78.831 ms 78.656 ms
21 c-68-x-x-x.hsd1.de.comcast.net (68.x.x.x) 83.388 ms 84.671 ms 96.913 ms
--
"ONE team - ONE city - ONE dream!!" |
|
chris2topher
@comcast.net | reply to JeepMatt
this has been the behavior for the past three nights. Seems as if they are working on that backbone/router. |
|
aaldere1
join:2004-11-21
Santa Monica, CA
| reply to RdKryton
Hey guys. Looks like things are turning back to normal for me.
HOST LOSS RCVD SENT BEST AVG WORST
ge1-8-1000m.sw1.easynews.com 0% 10 10 0.39 0.48 0.58
e-2-11-1000m.core-03.phx1.puregig.net 0% 10 10 0.31 6.67 54.40
ve5-10G.core-04.phx2.puregig.net 0% 10 10 0.31 5.58 37.91
12.117.165.93 0% 10 10 0.67 1.07 3.04
12.122.81.94 0% 10 10 59.18 60.83 72.52
tbr2-cl1592.dlstx.ip.att.net 0% 10 10 59.62 72.06 148.67
tbr1-cl6.sl9mo.ip.att.net 0% 10 10 58.79 66.96 99.20
tbr1-cl4.wswdc.ip.att.net 0% 10 10 58.83 68.53 106.61
tbr2-cl27.wswdc.ip.att.net 0% 10 10 59.22 65.05 89.62
tbr2-cl15.n54ny.ip.att.net 0% 10 10 59.53 66.25 108.56
gar7-p390.n54ny.ip.att.net 0% 10 10 57.54 80.78 241.04
12.118.102.22 0% 10 10 58.84 60.56 67.70
68.87.16.6 0% 10 10 59.03 63.43 89.25
te-7-1-ar01.audubon.nj.panjde.comcast.net 0% 10 10 59.02 61.13 78.40
po10-ar01.wallingford.pa.panjde.comcast.net 0% 10 10 58.98 59.12 59.48
po90-ur01.greenwayave.pa.panjde.comcast.net 0% 10 10 59.81 63.96 94.99
po90-ur01.columbsblvd.pa.panjde.comcast.net 0% 10 10 60.87 63.19 75.28
po90-ur01.christianst.pa.panjde.comcast.net 0% 10 10 60.27 60.94 63.97
po90-ur01.fairmountave.pa.panjde.comcast.net 0% 10 10 61.65 62.56 67.22
po90-ur01.wayneave.pa.panjde.comcast.net 0% 10 10 60.67 65.95 111.39
po90-ur01.chestnuthill.pa.panjde.comcast.net 0% 10 10 61.01 69.99 107.28
ge-0-2-ubr01.chestnuthill.pa.panjde.comcast.net 0% 10 10 62.73 70.48 110.98
pcp0011892214pcs.jdover01.nj.comcast.net 10% 9 10 66.24 72.29 106.87 |
|
RdKryton
Premium
join:2002-03-17
Downingtown, PA
·Comcast
| reply to JeepMatt
Mine sucks too... Everything is fine right up to hop #10
8 41 ms 13 ms 14 ms 68.86.211.14
9 17 ms 14 ms 16 ms 12.119.53.53
10 280 ms 278 ms 279 ms tbr2-p012401.phlpa.ip.att.net [12.123.137.49]
11 282 ms 272 ms 280 ms tbr1-cl9.wswdc.ip.att.net [12.122.2.85]
--
Stop yelling at me! I'm stupid not deaf.... |
|
SolidWing68
join:2002-09-20
Jersey City, NJ
| reply to JeepMatt
Since about a day or 2 ago my latency has been very high at times and then like around 2-3 am it would be ok, but even today around morning time up til now my latency is still high..here is my tracert
Tracing route to www.comcast.net [204.127.205.8]
over a maximum of 30 hops:
1 * * * Request timed out.
2 16 ms 7 ms 9 ms ge-2-2-ur01.jerseycity.nj.panjde.comcast.net [68.86.220.177]
3 8 ms 23 ms 10 ms po10-ur02.jerseycity.nj.panjde.comcast.net [68.86.209.246]
4 7 ms 7 ms 12 ms po10-ur01.narlington.nj.panjde.comcast.net [68.86.209.250]
5 10 ms 9 ms 12 ms po70-ar01.verona.nj.panjde.comcast.net [68.86.209.254]
6 9 ms 9 ms 10 ms ar01.plainfield.nj.panjde.comcast.net [68.86.208.5]
7 18 ms 10 ms 10 ms 68.86.211.2
8 200 ms 203 ms 202 ms 12.118.102.17
9 204 ms 204 ms 197 ms tbr1-p010101.n54ny.ip.att.net [12.123.3.82]
10 197 ms 193 ms 198 ms ar1-p312.n54ny.ip.att.net [12.123.0.49]
11 198 ms 198 ms 199 ms mdf1-gsr12-2-pos-7-0.nyc3.attens.net [12.122.255.162]
12 198 ms 198 ms 194 ms sccsbix12-1-4.attbi.com [63.240.64.46]
13 * * * Request timed out.
14 * * * Request timed out.
15 222 ms 211 ms 211 ms www.comcast.net [204.127.205.8]
Trace complete. |
|
HARMANE
join:2006-03-30 | reply to JeepMatt
i asked the same thing and they told me it wasn't going to cost anything. |
|
snookies
join:2005-08-11
Philadelphia, PA
| reply to HARMANE
i called on thursday and they told me if i wanted, they'd send a tech out but if they found nothing wrong then i'd have to pay a service charge... i said i can't control UR servers. i said what if the guy comes and my speed returns to normal and it was actually ur server which im almost certain about... they said theres nothin i can do but take that risk. i said forget it, don't send me a tech becuz i can't control ur speeds and im not willin to pay if u guys decide to return my speeds to normal for something that is comcast's fault... pile a bs. |
|
HARMANE
join:2006-03-30 | reply to JeepMatt
called comcast AGAIN and they've been getting calls all day about this. then he said something really funny. apparently there's not enough calls to do anything about this for a couple more days. good stuff. |
|
swagdogpsu69
join:2006-04-01
Harrisburg, PA | reply to aaldere1
snookie......I live in Harisburg, PA, and mine has been bad since Thursday night as well |
|
aaldere1
join:2004-11-21
Santa Monica, CA
4 edits | reply to freaked
Hey guys. Good to know people are having issues with their connect. For awhile there, I thought I was the only one. You know that feeling. It's completely BOMBED over the past many days. 40-50k/sec downloads from servers where I normally get 600+k/sec. It's ridiculous. I hope they get their act together. The AT&T location seems to be having serious issues.
»/quality/nil/2015285
That is the speed test. Even though most 'pass' you can see that 12.118.102.22 is where my ping goes to around 155.80 average. By the time it reaches me, my pings are horrible. I can tell the difference, since just browsing web pages is slower.
ge1-8-1000m.sw1.easynews.com 0% 10 10 0.38 0.57 2.01
e-2-11-1000m.core-03.phx1.puregig.net 0% 10 10 0.27 0.31 0.35
ve5-10G.core-04.phx2.puregig.net 0% 10 10 0.34 1.13 7.36
12.117.165.93 0% 10 10 0.64 0.83 1.18
12.122.81.94 0% 10 10 59.31 59.62 60.26
tbr2-cl1592.dlstx.ip.att.net 0% 10 10 59.68 60.43 61.55
tbr1-cl6.sl9mo.ip.att.net 0% 10 10 58.61 58.92 59.13
tbr1-cl4.wswdc.ip.att.net 0% 10 10 58.71 59.99 66.42
tbr2-cl27.wswdc.ip.att.net 0% 10 10 59.27 60.11 60.78
tbr2-cl15.n54ny.ip.att.net 0% 10 10 59.56 69.01 151.66
gar7-p390.n54ny.ip.att.net 0% 10 10 57.43 66.64 101.81
12.118.102.22 0% 10 10 207.51 233.54 392.99
68.87.16.6 0% 10 10 207.60 228.75 343.08
te-7-1-ar01.audubon.nj.panjde.comcast.net 0% 10 10 208.37 223.66 293.24
po10-ar01.wallingford.pa.panjde.comcast.net 0% 10 10 208.27 218.34 243.38
po90-ur01.greenwayave.pa.panjde.comcast.net 0% 10 10 207.73 216.62 222.64
po90-ur01.columbsblvd.pa.panjde.comcast.net 0% 10 10 207.93 218.09 224.83
po90-ur01.christianst.pa.panjde.comcast.net 0% 10 10 207.56 216.74 223.68
po90-ur01.fairmountave.pa.panjde.comcast.net 0% 10 10 207.39 217.19 223.61
po90-ur01.wayneave.pa.panjde.comcast.net 0% 10 10 206.05 216.56 222.61
po90-ur01.chestnuthill.pa.panjde.comcast.net 10% 9 10 211.86 218.12 223.64
ge-0-2-ubr01.chestnuthill.pa.panjde.comcast.net 10% 9 10 212.89 220.66 227.36
pcp0011892214pcs.jdover01.nj.comcast.net 10% 9 10 218.12 236.31 261.91 |
|
freaked
@comcast.net | reply to JeepMatt
Still Getting igh ping :; |
|
snookies
join:2005-08-11
Philadelphia, PA | reply to HARMANE
in PA area and my services have gone as slow as 56k speeds or slower... its spiking like crazy that when i do play games. it stutters when it spikes lol... its been like this since thursday for me... |
|
HARMANE
join:2006-03-30
| reply to JeepMatt
traceroute to www.comcast.net (63.240.76.72), 30 hops max, 40 byte packets
1 * * * Request timed out.
2 68.86.156.65 (68.86.156.65) 8.989 ms 12.178 ms 8.259 ms
3 po10-ur01.wayneave.pa.panjde.comcast.net (68.86.208.69) 8.038 ms 9.662 ms 9.583 ms
4 po10-ur01.fairmountave.pa.panjde.comcast.net (68.86.208.65) 9.251 ms 9.313 ms 8.256 ms
5 po10-ur01.christianst.pa.panjde.comcast.net (68.86.208.61) 8.311 ms 9.464 ms 30.168 ms
6 po10-ur01.columbsblvd.pa.panjde.comcast.net (68.86.208.57) 10.970 ms 8.921 ms 8.234 ms
7 po10-ur01.greenwayave.pa.panjde.comcast.net (68.86.208.53) 18.252 ms 10.795 ms 11.487 ms
8 po20-ar01.wallingford.pa.panjde.comcast.net (68.86.208.49) 10.323 ms 11.968 ms 11.435 ms
9 po90-ar01.401nbroadst.pa.panjde.comcast.net (68.86.208.29) 10.415 ms 11.566 ms 10.645 ms
10 68.86.211.14 (68.86.211.14) 13.111 ms 13.780 ms 13.035 ms
11 12.118.114.9 (12.118.114.9) 185.616 ms 183.149 ms 179.202 ms
12 tbr2-p012301.phlpa.ip.att.net (12.123.137.66) 178.301 ms 179.983 ms 181.988 ms
13 gar2-p390.phlpa.ip.att.net (12.123.137.50) 198.516 ms 185.325 ms 197.548 ms
14 mdf1-gsr12-1-pos-6-0.nyc3.attens.net (12.122.255.126) 190.451 ms 191.383 ms 192.508 ms
15 mdf2-bi8k-2-ve-25.nyc3.attens.net (63.240.64.98) 202.576 ms 198.483 ms 193.868 ms
16 * * * Request timed out.
17 * * * Request timed out.
18 www.comcast.net (63.240.76.72) 182.921 ms 182.232 ms 186.354 ms
Trace complete
still awesome here in philly! |
|
