We are currently experiencing some problem with cogent network. It appears to be the node at San Francisco. Anyone experiencing similar problem?

There are no problems with our network as far as I know and we are in San Francisco and powered by Cogent.

You are calling this "no problem"?? ;)

traceroute to 321host-it.com (66.28.45.9), 30 hops max, 40 byte packets
1 so-4-1-0.mp2.SanFrancisco1.Level3.net (209.247.10.237) 1 ms 0 ms 0 ms
2 so-2-0-0.mp2.SanJose1.Level3.net (64.159.0.218) 1 ms 1 ms 1 ms
3 gigabitethernet5-2.core1.SanJose1.Level3.net (64.159.2.165) 2 ms 2 ms 1 ms
4 205.215.1.229 (205.215.1.229) 270 ms 264 ms 252 ms
5 205.215.12.1 (205.215.12.1) 283 ms 257 ms 262 ms
6 p13-0.core02.sfo01.atlas.cogentco.com (66.28.28.57) 268 ms 253 ms 240 ms
7 g50.ba01.b003070-1.sfo01.atlas.cogentco.com (66.28.5.182) 253 ms 293 ms 294 ms
8 66.28.45.9 (66.28.45.9) 268 ms 268 ms 263 ms


Looks like there's a serious congestion somewhere between Level3 and Cogent.

Yeah, looks like it's the peering point between Level3 and Cogent. Above.net seems to be fine:

traceroute to 321host-it.com (66.28.45.9), 30 hops max, 40 byte packets
1 main1-main2-eth.sjc1.above.net (207.126.96.189) 0.537 ms 0.552 ms 0.489 ms
2 core6-main1-oc12.sjc1.above.net (208.185.175.249) 0.515 ms 0.576 ms 0.480 ms
3 core3-sjc1-oc48.sjc2.above.net (208.184.102.206) 0.636 ms 0.709 ms 0.648 ms
4 core7-core3-oc48.sjc2.above.net (64.125.30.5) 0.617 ms 0.605 ms 0.532 ms
5 dfw2-sjc2-oc48 (208.184.232.81) 40.566 ms 40.538 ms 40.536 ms
6 core2-core3-oc48.dfw2.above.net (216.200.127.217) 40.739 ms 40.715 ms 40.701 ms
7 core2-dfw2-oc48.dfw3.above.net (208.184.232.114) 40.673 ms 40.736 ms 40.739 ms
8 64.124.51.171.cogentco.com (64.124.51.171) 46.637 ms 46.757 ms 46.596 ms
9 p5-0.core02.sfo01.atlas.cogentco.com (66.28.4.134) 46.811 ms 46.759 ms 48.338 ms
10 g50.ba01.b003070-1.sfo01.atlas.cogentco.com (66.28.5.182) 47.095 ms 47.602 ms 47.223 ms
11 66.28.45.9 (66.28.45.9) 46.998 ms 47.152 ms 47.153 ms

This is to be expected with Cogent at this point - they can't afford to buy transit from Level3, so they use what little available bandwidth they can through the old Netrail peering they acquired.

Oh well.. This is getting a very ugly. We are still unable to reach all our boxes after 24 hours. We decided and have switched everything over to Ssavvis.

I called the data centre, they blame it to cogent end at San Fancisco and I made a call to cogentco, they said there are not aware of any problem other than minor maintenace. Maybe someone can tell me what is going on. Here is the IP: 66.28.99.200.

TraceRoute to 66.28.99.200

Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 66.46.176.3 -
2 0 0 0 216.191.97.41 pos5-3.core1-mtl.bb.attcanada.ca
3 15 0 16 216.191.65.173 pos8-1.core2-tor.bb.attcanada.ca
4 0 15 0 216.191.65.243 srp2-0.gwy1-tor.bb.attcanada.ca
5 16 16 15 12.125.142.5 -
6 16 15 16 12.123.5.222 gbr6-p80.cgcil.ip.att.net
7 16 15 32 12.122.11.45 tbr1-p013601.cgcil.ip.att.net
8 94 109 109 12.122.10.6 tbr1-cl1.sffca.ip.att.net
9 62 63 62 12.122.11.218 ggr1-p340.sffca.ip.att.net
10 63 62 63 12.123.221.2 nr1-p350.paix.ip.att.net
11 63 62 63 205.215.1.169 -
12 62 63 62 205.215.12.1 gige2-1.tr1.sanfrancisco1.ca.us.netrail.net
13 Destination host unreachable Timed out Destination host unreachable -
14 Timed out Timed out Timed out

Everything beyond sanfrancisco1.ca.us.netrail.net is pretty much dead from all the place I can trace. But there is at least 5-7 hops before it reach our boxes.

As an ecommercediscovery user, I'm rooting for this to get resolved quickly. I run all my email through my account, and the 42 hours and counting of downtime have significantly affected that. My estimation is that I've lost at least 60 email... with only the hope that anything important will be re-sent.

I presume if you're switching carriers that that will require rerouting all the DNS? If so, then the downtime is going to extend at least another 24 hours, correct?

Here's hoping this gets over soon. I understand this is something generally out of your control, but I can only afford to be out of email for so long.

Good luck.

Originally posted by JoeCool
As an ecommercediscovery user, I'm rooting for this to get resolved quickly. I run all my email through my account, and the 42 hours and counting of downtime have significantly affected that. My estimation is that I've lost at least 60 email... with only the hope that anything important will be re-sent.


Joe

Ecommercediscovery has very stable servers in burst.net. They are a little expensive in comparison to cognet bandwidth but I think it worths it.

If you ask Josh I think he will be able to give you a small reseller account on his burst server for a suitable price. Then you can host your critical websites on it.

Mac

[i]
I presume if you're switching carriers that that will require rerouting all the DNS? If so, then the downtime is going to extend at least another 24 hours, correct?

Good luck. [/B]

You are correct. We have switched carrier and reconfigured our servers . Now you should have FTP and control panel access through the IP we emailed out 7-8 hours ago. Once the new dns ip is propagated, all email and domain will be readable. We appologize for the inconvenient. We are doing everything we can to sort this out. Anyway,if you need any other help. Contact me at josh@ecommercediscovery.com . I dont want turn WHT into a ECD support forum.

A traceroute to 66.28.99.200 from our network in SF shows the same results:

traceroute to 66.28.99.200 (66.28.99.200), 30 hops max, 38 byte packets
1 66.28.45.1 (66.28.45.1) 0.603 ms 0.546 ms 0.378 ms
2 g0-2.core01.sfo01.atlas.cogentco.com (66.28.5.177) 0.477 ms !H * 0.475 ms !H

So this is no problem with Cogent but with your provider or if the 66.28.99.0/24 block is yours, your problem :) Seems to me like there's a router downtime or the cross connect to Cogent has gone belly up or anything of that sort.