| Posted by jwr, 08-21-2004, 02:22 AM | |
I noticed a server at ThePlanet (servermatrix actually) running a little bizzare. Checked from a few locations and it seems like they're being molested.
ICMP traffic is fine from Los Angeles but neither their main site, nor customer sites will load. Sites will load from Chicago and Seattle, no ssh/ftp/etc traffic will make it thru. HTTP seems to be spotty. ICMP traffic is at about 50% - anybody know what the story is?
|
| Posted by Justin Reel, 08-21-2004, 02:27 AM | |
Same here...
I found this on their forum a few minutes ago: http://forums.servermatrix.com/viewtopic.php?t=9848.
|
| Posted by jwr, 08-21-2004, 02:30 AM | |
All customers will have received that via email - however, today is not the 22nd
|
| Posted by Justin Reel, 08-21-2004, 02:36 AM | |
doh... My problems started right about the time that post stated so I guess I just assumed it was today. Maybe they also thought today was the 22nd and started early?
|
| Posted by thebestdeal, 08-21-2004, 03:19 AM | |
45 minutes, 10 of my servers have been mostly inaccessible. There have been brief moments, 1 or 2 minutes, of them being up but so slow its just as good as being down. Surprise there are not more posts. It is probably just me being routed through some broke upstream network since no very many people seem to be having the problems I have. Any official word on what's up. Servermatrix forums aren't working for me right at this moment.
Down:
5 26 ms 25 ms 27 ms bb2-p5-0-0.kntpin.ameritech.net [151.164.191.170
6 37 ms 37 ms 37 ms bb2-p3-7.emhril.ameritech.net [151.164.190.34]
7 39 ms 39 ms 39 ms ex2-p6-2.eqchil.sbcglobal.net [151.164.40.82]
8 36 ms 37 ms 39 ms 151.164.249.90
9 36 ms 41 ms 39 ms ge-2-1-0.a1.chcg.broadwing.net [216.140.15.17]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
etc...
Up but slow:
5 26 ms 25 ms 30 ms bb2-p5-0-0.kntpin.ameritech.net [151.164.191.170]
6 40 ms 39 ms 38 ms bb2-p3-7.emhril.ameritech.net [151.164.190.34]
7 39 ms 39 ms 37 ms ex1-p6-0.eqchil.sbcglobal.net [151.164.240.146]
8 54 ms 39 ms 39 ms 151.164.249.90
9 38 ms 39 ms 41 ms ge-1-2-0.a1.chcg.broadwing.net [216.140.14.161]
10 40 ms * 52 ms 216.140.15.9
11 * 57 ms * p0-3-0.c1.ftwo.broadwing.net [216.140.4.213]
12 59 ms 56 ms * a1-2-dllstx02.broadwing.net [216.140.4.70]
13 66 ms 72 ms * 67.99.43.234
14 * * * Request timed out.
15 myserverhere.com.....
|
| Posted by jwr, 08-21-2004, 03:40 AM | |
Well from watching traffic data change over the last while, they're fiddling with things as we speak, you'll notice routes flipping about and connectivity to various locations improving or taking a downhill plunge. You could always try the support number to get some feedback from a lower level tech as I'm sure they've been given some info, tho I doubt you'll really gather more than "we're working on it" at this point
(214) 782-7802
(800) 854-7679
|
| Posted by A|J, 08-21-2004, 04:24 AM | |
From what i am seeing, it seems to be affecting those who connect via Broadwing.
From Toronto:
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.2.1
2 2 ms 2 ms 3 ms 192.168.102.1
3 8 ms 7 ms 9 ms 10.45.88.1
4 52 ms 12 ms 31 ms gw03-vlan201.wlfdle.phub.net.cable.rogers.com [6
6.185.90.161]
5 8 ms 7 ms 7 ms gw01-vlan961.wlfdle.phub.net.cable.rogers.com [6
6.185.93.65]
6 9 ms 9 ms 7 ms gw02.wlfdle.phub.net.cable.rogers.com [66.185.80
.130]
7 9 ms 11 ms 9 ms gw02.bloor.phub.net.cable.rogers.com [66.185.80.
13]
8 21 ms 17 ms 11 ms gw02.ym.phub.net.cable.rogers.com [66.185.83.137
]
9 51 ms 49 ms 49 ms igw01.chcrmk.phub.net.cable.rogers.com [66.185.8
1.190]
10 49 ms 49 ms 49 ms sp0-5-CHCGILCA.broadwing.com [206.223.119.72]
11 51 ms 49 ms 50 ms ge-2-1-0.a1.chcg.broadwing.net [216.140.15.17]
12 53 ms 54 ms * 216.140.15.9
13 * 76 ms * P6-2.c0.ftwo.broadwing.net [216.140.16.37]
14 79 ms 72 ms * a1-2-dllstx02.broadwing.net [216.140.4.70]
15 73 ms * * 67.99.43.234
16 74 ms * 74 ms dsr2-2-v1.dllstx4.theplanet.com [12.96.160.8]
17 74 ms * * gig1-0-2.tp-car9-2.dllstx4.theplanet.com [67.18.
116.86]
From centralops.net
1 0 0 0 216.46.228.229 port-216-3073253-es128.devices.datareturn.com
2 0 0 0 64.29.192.145 port-64-1949841-zzt0prespect.devices.datareturn.com
3 0 0 0 64.29.192.226 daa.g921.ispb.datareturn.com
4 0 0 0 168.215.241.133 hagg-01-ae0-1001.dlfw.twtelecom.net
5 0 0 0 168.215.241.150
6 1 0 0 12.96.160.39 dsr2-1-v2.dllstx4.theplanet.com
7 1 1 0 67.18.116.85 gig1-0-2.tp-car9-1.dllstx4.theplanet.com
|
| Posted by A|J, 08-21-2004, 04:28 AM | |
Contacted The Planet, and yes, it appears to only affect those who are connecting through broadwing. The problem lies with Broadwing and there is nothing they could do.
|
| Posted by jwr, 08-21-2004, 02:17 PM | |
The only problem I have with that is that three machines in three locations that I traced from are on different networks that ThePlanet is meant to have gige+ uplinks to. If it were only broadwing, at least two locations would have traced thru without issue. O'well, at least it's ok now.
|
|
 Add to Favourites
 Print this Article
|
