I Couldn't access Undeveloped.com

[Sinh]

I couldn't access Undeveloped.com, I don't know what happened. Anyone have the same issue now?

 

[End Game]

I'm going to bed. They will have it fixed by morning.

 

[usernamex]

Glad it's not just me.

Personally very happy with undeveloped so far, agree the support is stellar. Wealth of info in the main thread for anyone new to undeveloped
https://www.namepros.com/threads/undeveloped-com-experience.893201/

 

[elmoney]

Also not worked now

 

[Skyvisum]

If only they own a "domain"related brand name with "domain wodds in it.Would be awesome.Refused the offers I got there ,one low XXX offer for a name I listed within 24 hours,One bolted buyer after we agreed on payment .One installmental payment of $2k on going .Old lead from efty.Paying % commission.Just hope speeds they rebrand to a better name as they shift towards becoming a registrar as mentioned by them

 

[Finest]

The real problem is that landing pages are not working also

 

[Finest]

Working now. Just managed to access the site a minute ago.

 

[pavan kumar t]

undeveloped is working now

 

[Haroon Basha]

https://undeveloped.com/
working fine here now.

 

[Sinh]

It is working now.

 

[DAN.COM]

Hi All,

We’re back online since 8:05 (CEST). We had a unique and quite remarkable issue on our load balancer last night which took down Undeveloped.com.

Our server monitors didn’t catch up the issue, which is extremely strange and unacceptable. We're still investigating how it's possible that we weren't notified.

At night, at least two of our senior developers get notified on their phones when the site speed decreases or we go down. Last night, this failsafe never kicked in causing the issue to take longer than we're comfortable with.

We've identified the core cause now. As you know we're rolling out SSL on all parked domains with us and last night the certificate generator (which is connected to our load balancer since we are not allowed to generate certificates for non-active domains) all of sudden started sputtering and eventually took down the entire load balancer. This is absolutely not normal behavior so we're researching what the core cause has been and fixing it so we can continue completing generating the remaining certificates.

We have extensive safeguards in place for what happened last night, but the safeguards failed for some reason. We're looking into this as we speak and implementing a fix to prevent this situation from happening again.

Our sincere apologies for the inconvenience and thank you for your patience.

Kind regards,

Reza

 

[DAN.COM]

Quick follow-up update:

The initiator of the issue was our hosting provider AWS (Amazon). They had a problem with their EC2 VPC network which impacted our service and caused the strange issue at our load balancer hosted with them:

https://phd.aws.amazon.com/phd/home#/event-log?Start time=2018-07-18T10:05:45 to 2018-07-19T10:05:45&End time=2018-07-18T10:05:45 to 2018-07-19T10:05:45&Status=Closed / Completed&eventID=arn:aws:health:eu-central-1::event/AWS_EC2_VPC_NETWORK_HEALTH_INTRA_AZ_ISSUE_2018_07_19_00_43_00_3066&eventTab=details&layout=vertical

The issue began at Thu, 19 Jul 2018 00:43:00 GMT (exactly when our load balancer started showing issues).

Likely because Amazon has had their own server issues due to Prime Day, they couldn't fix the issue vigorously for their clients since our servers did go online again after their quick fix but our load balancer didn't.