  JeepMatt Delaware Fios Premium join:2001-12-28 Wilmington, DE
·Verizon FIOS
·Comcast
| [Connectivity] Philly Router is Bombing tonight..
Man - What's going on with the last Comcast hop in the PA/DE region tonight?? Holy crap! -- "ONE team - ONE city - ONE dream!!" |
|
  LiamJunket Premium join:2002-03-03 Ocean City, NJ
·Comcast
| said by JeepMatt :Man - What's going on with the last Comcast hop in the PA/DE region tonight?? Holy crap! It looks to me like the problem is in the handoff from a Comcast router to the AT&T backbone router. -- -- Join Red Room Forum BLOG tkjunkmail.blogspot.com My Web Page |
|
  JeepMatt Delaware Fios Premium join:2001-12-28 Wilmington, DE | reply to JeepMatt Yep- Reverse trace routes are showing the normal routers into the network are apparently down.... -- "ONE team - ONE city - ONE dream!!" |
|
  JeepMatt Delaware Fios Premium join:2001-12-28 Wilmington, DE
·Verizon FIOS
·Comcast
1 edit | Looks like the router shit out around 7 tonight... -- "ONE team - ONE city - ONE dream!!" |
|
  JeepMatt Delaware Fios Premium join:2001-12-28 Wilmington, DE
·Verizon FIOS
·Comcast
1 edit | Wow- Now I realize how all the people with latency feel..lol..
I tried Live Chat - but that was worthless, as usual.
The Comcast.net Help Forums are down as well.. what's going on tonight?? Guess no XBox for me ...
Looks like there is either an issue in DC or Philly with ATT.net - my reverse trace always went through there - tonight it's going to Chicago then through NY - so basically it looks like a main fiber is down - and everyone is this area is going through 1 pipe. -- "ONE team - ONE city - ONE dream!!" |
|
  LiamJunket Premium join:2002-03-03 Ocean City, NJ | Yeah, it looks like a meltdown on the connection between Comcast and the AT&T backbone in Philadelphia. All my speed tests and latency tests show major problems there from South Jersey. |
|
  SterlingJ85 Obama 2008
join:2000-11-19 Millville, NJ
·PHONE POWER
·TowerStream
| reply to JeepMatt
 3/30/06 11:41 PM |
This is rediculous -- -Sterling |
|
 HARMANE
join:2006-03-30
| reply to JeepMatt i had this same issue tonight, called comcast and the person i spoke with said i needed a tech to come out cause "there's a weak signal from my modem", even though i told them there's a major jump from comcast to at&t (8ms to 200+ms). whatever.
these are the results im getting now on gold tier 8000/768:
Last Result: Download Speed: 11405 kbps (1425.6 KB/sec transfer rate) Upload Speed: 588 kbps (73.5 KB/sec transfer rate)
upload isn't accurate cause i throttle via router and have 2 on lan running bt. |
|
  SparkChaser 'til we outnumber em Premium join:2000-06-06 Downingtown, PA
·Verizon FIOS
·Comcast
| reply to JeepMatt Same here in the western burbs, running 1.5-3k on Speakeasy at 9PM, 7K at 2AM. You can see the handoff from 68.86.208.29 to 68.86.211.14.
Ron -- Hard work never killed anybody but why should I take the chance |
|
  JeepMatt Delaware Fios Premium join:2001-12-28 Wilmington, DE
·Verizon FIOS
·Comcast
1 edit | Looks like the bum ATT router is now back online - I can tell by my reverse route. If you look at hops 10-13, I now go back into the Comcast network through DC and Philly. Last night - during the mess - it was going through Chicago to NY.
1 v253-gw.usc.edu (128.125.253.254) 0.449 ms 0.301 ms 0.277 ms 2 v251-gw-19.usc.edu (128.125.251.155) 0.344 ms 0.31 ms 0.267 ms 3 130.152.181.129 (130.152.181.129) 0.244 ms 0.281 ms 0.22 ms 4 198.172.117.161 (198.172.117.161) 0.606 ms 51.793 ms 5.249 ms 5 xe-1-0-0.r20.lsanca03.us.bb.verio.net (129.250.5.32) 0.589 ms 0.591 ms 0.541 ms 6 p16-0.att.lsanca03.us.bb.verio.net (129.250.9.110) 0.68 ms 0.636 ms 0.586 ms 7 12.123.222.22 (12.123.222.22) 69.188 ms 68.163 ms 67.808 ms 8 tbr2-cl21.sl9mo.ip.att.net (12.122.10.13) 67.341 ms 67.316 ms 67.254 ms 9 tbr1-cl24.sl9mo.ip.att.net (12.122.9.141) 67.958 ms 67.132 ms 67.958 ms 10 tbr1-cl4.wswdc.ip.att.net (12.122.10.29) 67.903 ms 67.215 ms 67.441 ms 11 tbr2-cl9.phlpa.ip.att.net (12.122.2.86) 67.84 ms 67.886 ms 68.82 ms 12 gar4-p390.phlpa.ip.att.net (12.123.137.73) 66.23 ms 66.948 ms 66.94 ms 13 12.118.118.22 (12.118.118.22) 67.423 ms 68.435 ms 67.301 ms 14 68.87.16.5 (68.87.16.5) 68.629 ms 67.913 ms 68.741 ms 15 te-8-3-ar01.plainfield.nj.panjde.comcast.net (68.86.211.5) 68.82 ms 68.881 ms 67.912 ms 16 po80-ar01.audubon.nj.panjde.comcast.net (68.86.208.2) 71.208 ms 70.389 ms 70.417 ms 17 po10-ar01.wallingford.pa.panjde.comcast.net (68.86.208.26) 72.662 ms 72.676 ms 71.87 ms 18 po90-ur02.norristown.pa.panjde.comcast.net (68.86.209.105) 74.527 ms 75.379 ms 75.445 ms 19 po90-ur01.norristown.pa.panjde.comcast.net (68.86.209.101) 74.333 ms 74.436 ms 74.267 ms 20 po90-ur01.claymont.de.panjde.comcast.net (68.86.209.97) 76.567 ms 75.596 ms 75.554 ms 21 ge-0-1-ubr01.claymont.de.panjde.comcast.net (68.86.216.214) 77.176 ms 77.06 ms 76.191 ms 22 c-68-.hsd1.de.comcast.net (68.85.x.x) 81.365 ms 81.909 ms 94.371 ms -- "ONE team - ONE city - ONE dream!!" |
|
  JeepMatt Delaware Fios Premium join:2001-12-28 Wilmington, DE
·Verizon FIOS
·Comcast
1 edit | One thing I do realize - is that Hop 12 and 13 are NOT the same IP address it always is. So there definitely may still be issues with ATT. I'm curious to see if that IP changes at all during the day today. -- "ONE team - ONE city - ONE dream!!" |
|
  JeepMatt Delaware Fios Premium join:2001-12-28 Wilmington, DE | I'm reverse routing back through Chicago and NY again - looks like they're working on it... -- "ONE team - ONE city - ONE dream!!" |
|
  RickRude
@208.17.x.x | reply to JeepMatt from what I heard ATT had to replace equiptment so they had to reroute traffic off of that router, which was bottlenecking the other routers. Could be just hearsay tho. |
|
  JeepMatt Delaware Fios Premium join:2001-12-28 Wilmington, DE | That's a very viable answer - figuring i'm still reversing through New York.
Looks like as of 1:07pm - the Philly ATT routers are still offline. -- "ONE team - ONE city - ONE dream!!" |
|
 HARMANE
join:2006-03-30
| reply to JeepMatt yeah im having issues again as well
traceroute to www.comcast.net (204.127.205.8), 30 hops max, 40 byte packets 1 * * * Request timed out. 2 68.86.156.65 (68.86.156.65) 8.008 ms 8.233 ms 12.706 ms 3 po10-ur01.wayneave.pa.panjde.comcast.net (68.86.208.69) 18.146 ms 30.430 ms 8.249 ms 4 po10-ur01.fairmountave.pa.panjde.comcast.net (68.86.208.65) 17.549 ms 11.701 ms 8.707 ms 5 po10-ur01.christianst.pa.panjde.comcast.net (68.86.208.61) 8.267 ms 9.576 ms 8.255 ms 6 po10-ur01.columbsblvd.pa.panjde.comcast.net (68.86.208.57) 9.604 ms 9.193 ms 10.724 ms 7 po10-ur01.greenwayave.pa.panjde.comcast.net (68.86.208.53) 10.681 ms 15.724 ms 10.589 ms 8 po20-ar01.wallingford.pa.panjde.comcast.net (68.86.208.49) 10.869 ms 10.826 ms 14.502 ms 9 po90-ar01.401nbroadst.pa.panjde.comcast.net (68.86.208.29) 9.627 ms 35.737 ms 11.059 ms 10 68.86.211.14 (68.86.211.14) 19.108 ms 22.426 ms 13.078 ms 11 12.119.53.53 (12.119.53.53) 37.591 ms 39.355 ms 39.034 ms 12 mdf1-gsr12-1-pos-6-0.nyc3.attens.net (12.122.255.126) 42.670 ms 42.702 ms 40.826 ms 13 sccsbix11-3-1.attbi.com (63.240.64.54) 36.808 ms 37.415 ms 42.210 ms 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 www.comcast.net (204.127.205.8) 56.224 ms 49.451 ms 67.639 ms Trace complete |
|
 swagdogpsu69
join:2006-04-01 Harrisburg, PA
| reply to JeepMatt Tracing route to www.comcast.net [204.127.195.15] over a maximum of 30 hops:
1 * * * Request timed out. 2 35 ms 6 ms 9 ms ge-2-2 ur02.lowerpaxton.pa.panjde.comcast.net [68.86.216.21] 3 40 ms 7 ms 7 ms te-9-1-ur01.lowerpaxton.pa.panjde.comcast.net [68.86.208.197] 4 16 ms 7 ms 9 ms te-8-1-ar01.lowerpaxton.pa.panjde.comcast.net [68.86.208.193] 5 15 ms 12 ms 11 ms po90-ar01.coatesville.pa.panjde.comcast.net [68.86.208.41] 6 12 ms 14 ms 12 ms po90-ar01.wallingford.pa.panjde.comcast.net [68.86.208.37] 7 41 ms 11 ms 12 ms po90-ar01.401nbroadst.pa.panjde.comcast.net [68.86.208.29] 8 15 ms 16 ms 16 ms 68.86.211.14 9 22 ms 24 ms 42 ms 12.119.53.49 10 245 ms 220 ms 222 ms tbr2-p012401.phlpa.ip.att.net [12.123.137.49] 11 263 ms 220 ms 221 ms tbr1-cl9.wswdc.ip.att.net [12.122.2.85] 12 223 ms 217 ms 221 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30] 13 225 ms 217 ms 221 ms tbr2-cl2.sffca.ip.att.net [12.122.10.42] 14 231 ms 236 ms 216 ms 12.123.13.178 15 216 ms 216 ms 221 ms idf22-gsr12-1-pos-6-0.rwc1.attens.net [12.122.255.222] 16 223 ms 222 ms 245 ms 63.241.85.98 17 * * * Request timed out. 18 225 ms 222 ms 227 ms www.comcast.net[204.127.195.15]
Trace complete. |
|
  JeepMatt Delaware Fios Premium join:2001-12-28 Wilmington, DE
·Verizon FIOS
·Comcast
| Is that a live trace from right now?? man - there is something going on out in your area...
Tracing route to www.comcast.net [204.127.195.15] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1 2 8 ms 11 ms 10 ms 73.151.88.1 3 7 ms 11 ms 8 ms ge-6-3-ur01.claymont.de.panjde.comcast.net [68.8 6.213.149] 4 13 ms 9 ms 8 ms po10-ur01.norristown.pa.panjde.comcast.net [68.8 6.209.98] 5 26 ms 8 ms 9 ms po10-ur02.norristown.pa.panjde.comcast.net [68.8 6.209.102] 6 29 ms 11 ms 11 ms po21-ar01.wallingford.pa.panjde.comcast.net [68. 86.209.106] 7 25 ms 11 ms 14 ms po90-ar01.401nbroadst.pa.panjde.comcast.net [68. 86.208.29] 8 15 ms 15 ms 17 ms 68.86.211.14 9 33 ms 20 ms 16 ms 12.118.114.9 10 76 ms 77 ms 78 ms tbr1-p012301.phlpa.ip.att.net [12.123.137.62] 11 95 ms 78 ms 80 ms tbr1-cl8.n54ny.ip.att.net [12.122.2.17] 12 94 ms 80 ms 78 ms tbr1-cl14.cgcil.ip.att.net [12.122.10.2] 13 94 ms 78 ms 80 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6] 14 92 ms 77 ms 75 ms gar4-p300.sffca.ip.att.net [12.123.13.174] 15 73 ms 76 ms 77 ms idf22-gsr12-1-pos-6-0.rwc1.attens.net [12.122.25 5.222] 16 79 ms 81 ms 82 ms rwcsbix11-1-4.attbi.com [63.241.85.234] 17 73 ms 77 ms 75 ms 192.168.64.65 18 96 ms 78 ms 76 ms www.comcast.net [204.127.195.15] -- "ONE team - ONE city - ONE dream!!" |
|
 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! |
|
 snookies
join:2005-08-11 Philadelphia, PA | 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... |
|
  freaked
@comcast.net | reply to JeepMatt Still Getting igh ping :; |
|