dynadot How long has Dynadot been down?

[Focus]

Totally unacceptable, I don't care what happened..this is bullsh*t, there is no reasonable explanation why any company should have their major registrar website down for this long...I have NEVER had this issue with Godaddy, Moniker, or Enom. They even let you know when they plan on being down...it would appear to me that they have subpar equipment/management at Dynadot at this point.

 

[Rockefeller]

Agreed, I def thought they would be up this morning...

 

[domaingenius]

They lost my good will towards them when ,after I accidentally renewed hosting twice,
they refused to refund the extra year. At that point as I say all goodwill they might have
had disappeared. I asked nicely ,did'nt insist or anything but even that was not good
enough for them. They then failed to give any reason.

DG

 

[Focus]

You guys have to realize when companies do not make much if any profit on domain registrations they have less money to put into their support & infrastructure..I would rather pay $10 anyday to another registrar I know is always going to answer the phone and have a working website. You always get what you pay for. I hope they resolve this fast for their sake.

 

[tonyfloyd]

i agree.....but what's GoDaddy's problem then...with their SLOOOOOOW system???

 

[Focus]

It is slow as hell...I HATE the godaddy interface/control panel..total brain damage.

Moniker is imo the easiest to use, along with enom. Moniker nameservers never seem to go down ever...enom does sometimes...Godaddy never ever.

 

[FroggyStyle]

It is slow as hell...I HATE the godaddy interface/control panel..total brain damage.

Moniker is imo the easiest to use, along with enom. Moniker nameservers never seem to go down ever...enom does sometimes...Godaddy never ever.

First of all I have to say hello I registered just so I may post in this thread

I have to agree with the above as far as godaddy. I have about 15 domains with them and have been looking for something with a better UI. I decided to pick up one new domain through dynadot to use on a new site idea. So I purchased the domain Friday night with hopes to work on the site this weekend.

Imagine my disappointment when I couldn’t access the site to change the namesrevers or even transfer the domain else where.

 

[ohkus]

You don't know why they are having this downtime so don't be so quick to judge. I agree this downtime is pretty damn unacceptable because there has been no communication what so ever. But to say no one should ever have this much downtime at once is a pretty silly statement. Moniker is all based in one data center, with one power outage or natural disaster they are done for, same with dynadot, and same with a few others.

 

[Focus]

Auraka...you have personally toured all of these data centers you mention?

 

[ohkus]

Auraka...you have personally toured all of these data centers you mention?

What does touring a data center have to do with a company having all of their equipment in a single data center? Yes I have toured many data centers if you need to know and data centers do have power outages and what not. If a company like moniker has all of their equipment in a single data center then they can go down if that data center goes down, when fiber cuts happen, etc.

 

[Focus]

You just seemed to know alot of details about them..that's why I asked.

So defensive...whoaaa lol

So, you know for an absolute fact moniker has ALL their equipment in one single data center is what I'm asking here... ??

ps - many top data centers have back-up VERY LARGE battery power supplies & even on site generators to ensure up-time...just a thought. I have a feeling this dynadot issue has nothing to do with a power surge..imo

 

[nts]

So, you know for an absolute fact moniker has ALL their equipment in one single data center is what I'm asking here... ??

ps - many top data centers have back-up VERY LARGE battery power supplies & even on site generators to ensure up-time...just a thought. I have a feeling this dynadot issue has nothing to do with a power surge..imo

After some quick research, I see Dynadot is hosted in the Market Post Tower, San Jose. A very well-respected DC.

I don't want to speculate, it could be anything. It looks like it's isolated to Dynadot's equipment though, as I can't find any other issues being reported out of that DC.

 

[FroggyStyle]

After some quick research, I see Dynadot is hosted in the Market Post Tower, San Jose. A very well-respected DC.

I don't want to speculate, it could be anything. It looks like it's isolated to Dynadot's equipment though, as I can't find any other issues being reported out of that DC.

Any info on Moniker DC ?

 

[anmike]

I can't connect dynadot.com keep now.

 

[Focus]

This is really a long time..2 days? wtf hope it is'nt some corporate terrorism or something...a disgruntled employee pulled some important wires or something..

 

[FroggyStyle]

I can't connect dynadot.com keep now.

??

 

[anmike]

??

Dynadot still down.

 

[ohkus]

Focused,

I can say that Moniker has their website/domainservers/etc. in the same data center. Hopefully they have offsite backups but you can find this out with simple traceroutes. Now I'm not saying Dynadot's outage has to do with their datacenter at all, what I'm trying to tell people is that many other providers are setup in the same way where they have a single site for all their stuff. So if that one site goes down they'd experience the same issue. Even the best data centers have issues, 365 main has gone down more than once. So lets not judge until we get the full details of this outage, the lack of communication here is unforgivable though.

I like the rest of you have some of the most valuable names to me with them and after this I'm going to have to re-think that choice. I can live with downtime, what I can't live with is downtime with no communication and that makes me worry a lot.

[ross@avalon ~]$ tp www.moniker.com
1: avalon.skafari.com (69.65.40.67) 0.232ms pmtu 1500
1: 69.65.40.94 (69.65.40.94) 9.240ms
2: p101.csr1.Chi3.Servernap.net (66.252.0.133) 1.546ms
3: v998.csr2.Chi3.Servernap.net (69.39.239.177) asymm 2 2.460ms
4: xe-5-0-0.er1.Chi2.Servernap.net (66.252.0.70) 1.973ms
5: er1.Chi2-Telia.chieqxr1.Servernap.net (66.252.3.138) 2.148ms
6: level3-ic-122233-chi-bb1.telia.net (213.248.84.54) asymm 5 39.604ms
7: ae-31-55.ebr1.Chicago1.Level3.net (4.68.101.158) asymm 5 6.130ms
8: ae-6.ebr1.Chicago2.Level3.net (4.69.140.190) asymm 6 3.167ms
9: ae-3.ebr2.Denver1.Level3.net (4.69.132.61) asymm 7 38.838ms
10: ae-1-100.ebr1.Denver1.Level3.net (4.69.132.37) asymm 8 38.212ms
11: ae-3.ebr2.SanJose1.Level3.net (4.69.132.57) asymm 9 52.441ms
12: ae-82-82.csw3.SanJose1.Level3.net (4.69.134.218) asymm 10 56.295ms
13: ae-83-83.ebr3.SanJose1.Level3.net (4.69.134.233) asymm 11 53.055ms
14: ae-2.ebr3.LosAngeles1.Level3.net (4.69.132.10) asymm 12 68.271ms
15: ae-83-83.csw3.LosAngeles1.Level3.net (4.69.137.42) asymm 13 60.562ms
16: ae-34-89.car4.LosAngeles1.Level3.net (4.68.20.134) asymm 14 185.917ms
17: BANDCON.car4.LosAngeles1.Level3.net (4.71.128.74) asymm 16 61.079ms
18: 208.73.208.14 (208.73.208.14) asymm 16 60.736ms
19: 208.73.210.52 (208.73.210.52) asymm 18 60.897ms reached
Resume: pmtu 1500 hops 19 back 18
[ross@avalon ~]$ tp ns1.domainservice.com
1: avalon.skafari.com (69.65.40.67) 0.196ms pmtu 1500
1: 69.65.40.94 (69.65.40.94) 9.123ms
2: p101.csr1.Chi3.Servernap.net (66.252.0.133) 9.734ms
3: v998.csr2.Chi3.Servernap.net (69.39.239.177) asymm 2 9.701ms
4: xe-5-0-0.er1.Chi2.Servernap.net (66.252.0.70) 9.756ms
5: er1.Chi2-Telia.chieqxr1.Servernap.net (66.252.3.138) 2.186ms
6: level3-ic-122233-chi-bb1.telia.net (213.248.84.54) asymm 5 2.426ms
7: ae-32-52.ebr2.Chicago1.Level3.net (4.68.101.62) asymm 5 15.562ms
8: ae-5.ebr2.Chicago2.Level3.net (4.69.140.194) asymm 6 3.060ms
9: ae-1-100.ebr1.Chicago2.Level3.net (4.69.132.113) asymm 6 3.002ms
10: ae-3.ebr2.Denver1.Level3.net (4.69.132.61) asymm 7 26.471ms
11: ae-1-100.ebr1.Denver1.Level3.net (4.69.132.37) asymm 8 29.442ms
12: ae-3.ebr2.SanJose1.Level3.net (4.69.132.57) asymm 9 57.443ms
13: ae-92-92.csw4.SanJose1.Level3.net (4.69.134.222) asymm 10 52.569ms
14: ae-93-93.ebr3.SanJose1.Level3.net (4.69.134.237) asymm 11 52.704ms
15: ae-2.ebr3.LosAngeles1.Level3.net (4.69.132.10) asymm 12 70.134ms
16: ae-93-93.csw4.LosAngeles1.Level3.net (4.69.137.46) asymm 13 63.816ms
17: ae-44-99.car4.LosAngeles1.Level3.net (4.68.20.198) asymm 14 60.650ms
18: BANDCON.car4.LosAngeles1.Level3.net (4.71.128.74) asymm 16 60.940ms
19: 208.73.208.14 (208.73.208.14) asymm 16 60.732ms
20: ns1.domainservice.com (208.73.210.41) asymm 18 60.394ms reached
Resume: pmtu 1500 hops 20 back 18
[ross@avalon ~]$ tp ns2.domainservice.com
1: avalon.skafari.com (69.65.40.67) 0.193ms pmtu 1500
1: 69.65.40.94 (69.65.40.94) 0.532ms
2: p101.csr1.Chi3.Servernap.net (66.252.0.133) 0.500ms
3: v998.csr2.Chi3.Servernap.net (69.39.239.177) asymm 2 0.810ms
4: xe-5-0-0.er1.Chi2.Servernap.net (66.252.0.70) 2.199ms
5: er1.Chi2-Telia.chieqxr1.Servernap.net (66.252.3.138) 2.366ms
6: 4.68.127.137 (4.68.127.137) asymm 5 2.489ms
7: ae-31-53.ebr1.Chicago1.Level3.net (4.68.101.94) asymm 5 2.624ms
8: ae-6.ebr1.Chicago2.Level3.net (4.69.140.190) asymm 6 2.794ms
9: ae-3.ebr2.Denver1.Level3.net (4.69.132.61) asymm 7 26.638ms
10: ae-1-100.ebr1.Denver1.Level3.net (4.69.132.37) asymm 8 33.997ms
11: ae-3.ebr2.SanJose1.Level3.net (4.69.132.57) asymm 9 58.537ms
12: ae-62-62.csw1.SanJose1.Level3.net (4.69.134.210) asymm 10 52.278ms
13: ae-63-63.ebr3.SanJose1.Level3.net (4.69.134.225) asymm 11 53.546ms
14: ae-2.ebr3.LosAngeles1.Level3.net (4.69.132.10) asymm 12 70.955ms
15: ae-63-63.csw1.LosAngeles1.Level3.net (4.69.137.34) asymm 13 63.832ms
16: ae-14-69.car4.LosAngeles1.Level3.net (4.68.20.6) asymm 14 60.787ms
17: BANDCON.car4.LosAngeles1.Level3.net (4.71.128.74) asymm 16 60.500ms
18: 208.73.208.14 (208.73.208.14) asymm 16 60.422ms
19: ns2.domainservice.com (208.73.211.42) asymm 18 60.909ms reached
Resume: pmtu 1500 hops 19 back 18
[ross@avalon ~]$ tp ns3.domainservice.com
1: avalon.skafari.com (69.65.40.67) 0.103ms pmtu 1500
1: 69.65.40.94 (69.65.40.94) 0.434ms
2: p101.csr1.Chi3.Servernap.net (66.252.0.133) 0.481ms
3: v998.csr2.Chi3.Servernap.net (69.39.239.177) asymm 2 0.591ms
4: xe-5-0-0.er1.Chi2.Servernap.net (66.252.0.70) 1.962ms
5: er1.Chi2-Telia.chieqxr1.Servernap.net (66.252.3.138) 2.071ms
6: ge-6-6.car3.Chicago1.Level3.net (209.0.227.73) asymm 5 2.418ms
7: ae-32-52.ebr2.Chicago1.Level3.net (4.68.101.62) asymm 5 6.858ms
8: ae-5.ebr2.Chicago2.Level3.net (4.69.140.194) asymm 6 3.077ms
9: ae-1-100.ebr1.Chicago2.Level3.net (4.69.132.113) asymm 6 2.793ms
10: ae-3.ebr2.Denver1.Level3.net (4.69.132.61) asymm 7 26.536ms
11: ae-1-100.ebr1.Denver1.Level3.net (4.69.132.37) asymm 8 39.139ms
12: ae-3.ebr2.SanJose1.Level3.net (4.69.132.57) asymm 9 58.330ms
13: ae-72-72.csw2.SanJose1.Level3.net (4.69.134.214) asymm 10 64.822ms
14: ae-73-73.ebr3.SanJose1.Level3.net (4.69.134.229) asymm 11 55.918ms
15: ae-2.ebr3.LosAngeles1.Level3.net (4.69.132.10) asymm 12 60.093ms
16: ae-73-73.csw2.LosAngeles1.Level3.net (4.69.137.38) asymm 13 69.376ms
17: ae-34-89.car4.LosAngeles1.Level3.net (4.68.20.134) asymm 14 60.789ms
18: BANDCON.car4.LosAngeles1.Level3.net (4.71.128.74) asymm 16 60.057ms
19: 208.73.208.14 (208.73.208.14) asymm 16 61.070ms
20: ns3.domainservice.com (208.73.210.43) asymm 18 60.853ms reached
Resume: pmtu 1500 hops 20 back 18
[ross@avalon ~]$ tp ns4.domainservice.com
1: avalon.skafari.com (69.65.40.67) 0.188ms pmtu 1500
1: 69.65.40.94 (69.65.40.94) 0.544ms
2: p101.csr1.Chi3.Servernap.net (66.252.0.133) 0.547ms
3: v998.csr2.Chi3.Servernap.net (69.39.239.177) asymm 2 0.685ms
4: xe-5-0-0.er1.Chi2.Servernap.net (66.252.0.70) 1.998ms
5: er1.Chi2-Telia.chieqxr1.Servernap.net (66.252.3.138) 3.221ms
6: level3-ic-122233-chi-bb1.telia.net (213.248.84.54) asymm 5 8.582ms
7: ae-32-52.ebr2.Chicago1.Level3.net (4.68.101.62) asymm 5 15.636ms
8: ae-5.ebr2.Chicago2.Level3.net (4.69.140.194) asymm 6 2.624ms
9: ae-1-100.ebr1.Chicago2.Level3.net (4.69.132.113) asymm 6 2.711ms
10: ae-3.ebr2.Denver1.Level3.net (4.69.132.61) asymm 7 26.392ms
11: ae-1-100.ebr1.Denver1.Level3.net (4.69.132.37) asymm 8 27.327ms
12: ae-3.ebr2.SanJose1.Level3.net (4.69.132.57) asymm 9 53.091ms
13: ae-72-72.csw2.SanJose1.Level3.net (4.69.134.214) asymm 10 65.442ms
14: ae-73-73.ebr3.SanJose1.Level3.net (4.69.134.229) asymm 11 66.863ms
15: ae-2.ebr3.LosAngeles1.Level3.net (4.69.132.10) asymm 12 61.377ms
16: ae-73-73.csw2.LosAngeles1.Level3.net (4.69.137.38) asymm 13 70.060ms
17: ae-24-79.car4.LosAngeles1.Level3.net (4.68.20.70) asymm 14 60.609ms
18: BANDCON.car4.LosAngeles1.Level3.net (4.71.128.74) asymm 16 60.666ms
19: 208.73.208.14 (208.73.208.14) asymm 16 60.983ms
20: ns4.domainservice.com (208.73.211.44) asymm 18 60.743ms reached
Resume: pmtu 1500 hops 20 back 18
[ross@avalon ~]$

 

[GUA]

As much as I respect dynadot... this is crap. They should have emegency systems to be back up in hours not days.. They will lose a lot of business over this.

 

[south]

I doubt it's hardware. Possible, but more likely ddos attack or disgruntled employee. If it was hardware, they would have it on their home page.

The silence is deafening.