Secure Dragon LLC. - Now in Atlanta! (and still in FL, CO, IL, and CA) Happy Birthday vpsBoard, enjo

[KuJoe]

The only browsers I can't get to work are IE10 and IE11.


See the other thread for working browsers I've tested.

 

[dave]

Just tried it again with Firefox and today it's working -- thanks.

 

[D. Strout]

Hey Joe, don't you think you're getting a little ahead of yourself with that signature?

+ Florida | Colorado | Illinois | California | Oregon | Georgia | New Jersey | Ohio | Arizona | Texas

 

[KuJoe]

Hey Joe, don't you think you're getting a little ahead of yourself with that signature?

Maybe. We didn't expect it to take over a month to rack a single server.

 

[D. Strout]

Maybe. We didn't expect it to take over a month to rack a single server.

Well it's not just the one server in New Jersey, you also mentioned Arizona, Illinois and Dallas. As I understand it, none of those locations are very close to being up and running. All good though, they'll be up soon enough I'm sure, and it will be pretty cool

 

[KuJoe]

All of the servers except Ohio are already at the data centers and all of the paperwork has been submitted and filled out, we're just waiting for them to unbox the servers and rack them which usually takes 2 weeks and another 2-3 weeks to get the network setup.

 

[Jack]

 we're just waiting for them to unbox the servers and rack them which usually takes 2 weeks and another 2-3 weeks to get the network setup.

this is Colo@ right?

 

[nunim]

I'm waiting for Portland even if it's all backhaul to SEA and LA, it will be nice to have a reliable provider in the SEA area aside from RamNode.

 

[peterw]

Florida | Colorado | Illinois | California | Oregon | Georgia | New Jersey | Ohio | Arizona | Texas

This is a huge invest with all the locations you want to offer. I created a map with google maps because I am not good in the geography of the USA. Wlanboy did this here before and it is a great idea to visualize offers with their locations.

I want to know which datacenters you plan to use for Ohio and New Jersey. I would buy from both locations if the datacenters are unique.

 

[KuJoe]

This is a huge invest with all the locations you want to offer. I created a map with google maps because I am not good in the geography of the USA. Wlanboy did this here before and it is a great idea to visualize offers with their locations.

I want to know which datacenters you plan to use for Ohio and New Jersey. I would buy from both locations if the datacenters are unique.

We've actually added a map to our website, here's what the map will look like once we're finished (the shields represent the actual city location):



Unfortunately our Ohio location is not set in stone yet so we're not releasing the data center publicly. Our New Jersey location will also be COLO@ like our others. Right now the only locations that do not have servers on-site are Portland and Ohio since they are not finalized yet. All of our other locations have servers on-site and IP blocks assigned to them (each datacenter has the paperwork submitted to announce a /24 of IPv4 and a /48 of IPv6).

 

[peterw]

We've actually added a map to our website, here's what the map will look like once we're finished (the shields represent the actual city location):

sd_map copy.png

Sorry, you don't have permission for that!You do not have permission to view this attachment.

I cannot access the map :mellow:

 

[KuJoe]

I cannot access the map :mellow:

@MannDude will need to look into that, I've uploaded it: http://n3rd.info/upl/sd_map_copy.png

 

[KuJoe]

Bah! Our Texas server is being shipped back to us now. Time to start the timer all over again.

 

[fixidixi]

"Update on IPv6 for Atlanta OpenVZ VPSs

Hy _FixiDixi_

You are receiving this e-mail because you currently have a VPS in our new Atlanta location. We are happy to inform you that our IPv6 announcement has been brought online and IPv6 connectivity now works properly for your Atlanta VPS. We apologize for the length of time it took to resolve this and hope you weren't inconvenienced too much.

Thank you for your patience in this matter.

-The Secure Dragon Staff-"

nice , ive enabled fuse and started setting up the vm..

//ive brought it offline after bought it as i tought im going to deal with it if it has ipv6 already : dont like to touch configurations more than i have to..

 

[KuJoe]

Apparently our tickets were going to a "blackhole" at COLO@ so that's why it took them almost a month to setup our network. Luckily I got in touch with Ryan on here via PM and things are moving right along.

New Jersey should be live tonight, I just like to see at least 2 days of uptime before I allow new orders on the node and it's already over the 1 day mark.

 

[peterw]

New Jersey should be live tonight, I just like to see at least 2 days of uptime before I allow new orders on the node and it's already over the 1 day mark.

Is the looking glass server online for New Jersey?

 

[KuJoe]

Is the looking glass server online for New Jersey?

I just finished setting it up.

I added the server to Drgn.biz or you can visit the just the look glass site for NJ here: nj1.securedragon.net

 

[D. Strout]

Any idea why traceroutes to 72.71.247.90 time out? Don't see why it would, the IP is up and accessible to me, and the traceroute does get most of the way there, down to the ISP level.

 

[fixidixi]

@D. Strout:

From IT(prometeus):


...
 3  ibgp-gw-core-a.cdlan.net (217.171.32.129)  0.336 ms  0.458 ms  0.535 ms
 4  te7-5.210.ccr01.mil01.atlas.cogentco.com (149.6.152.77)  0.434 ms  0.458 ms  0.485 ms
 5  te0-7-0-15.ccr21.mrs01.atlas.cogentco.com (154.54.61.205)  9.219 ms  9.259 ms te0-4-0-3.ccr21.mrs01.atlas.cogentco.com (130.117.3.97)  9.534 ms
 6  be2237.ccr22.par01.atlas.cogentco.com (154.54.58.137)  21.863 ms be2238.mpd21.par01.atlas.cogentco.com (154.54.58.141)  19.383 ms be2239.mpd22.par01.atlas.cogentco.com (154.54.60.197)  19.290 ms
 7  be2272.ccr22.lon13.atlas.cogentco.com (130.117.49.121)  26.922 ms be2273.mpd21.lon13.atlas.cogentco.com (130.117.50.93)  26.881 ms be2271.ccr21.lon13.atlas.cogentco.com (130.117.49.117)  26.893 ms
 8  be2391.ccr22.bos01.atlas.cogentco.com (154.54.44.237)  100.818 ms be2390.ccr21.bos01.atlas.cogentco.com (154.54.44.221)  99.158 ms be2388.ccr21.bos01.atlas.cogentco.com (154.54.44.177)  99.375 ms
 9  te0-3-0-5.ccr21.alb02.atlas.cogentco.com (154.54.30.17)  102.211 ms te0-0-0-5.ccr21.alb02.atlas.cogentco.com (154.54.43.10)  98.909 ms  98.975 ms
10  38.104.52.30 (38.104.52.30)  103.855 ms  103.879 ms 38.104.52.22 (38.104.52.22)  114.795 ms
11  burl-lnk-70-109-168-139.ngn.east.myfairpoint.net (70.109.168.139)  108.249 ms  108.159 ms  108.143 ms
12  64.222.166.163 (64.222.166.163)  139.063 ms  136.412 ms  136.775 ms
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
from germany:


2 static-ip-217-118-23-129.inaddr.ip-pool.com (217.118.23.129) 3.595 ms static-ip-217-118-23-130.inaddr.ip-pool.com (217.118.23.130) 0.344 ms 0.364 ms
3 te1-7.ccr01.sxb03.atlas.cogentco.com (149.11.26.17) 0.649 ms 149.14.12.49 (149.14.12.49) 0.581 ms te1-7.ccr01.sxb03.atlas.cogentco.com (149.11.26.17) 0.735 ms
4 te1-7.ccr01.sxb01.atlas.cogentco.com (154.54.62.193) 0.780 ms te4-7.ccr01.sxb01.atlas.cogentco.com (154.54.62.197) 0.779 ms te2-5.ccr01.sxb01.atlas.cogentco.com (154.54.74.229) 0.825 ms
5 te0-7-0-4.mpd21.par01.atlas.cogentco.com (154.54.62.221) 7.769 ms te0-0-0-5.ccr21.par01.atlas.cogentco.com (154.54.75.21) 7.961 ms 7.976 ms
6 be2271.ccr21.lon13.atlas.cogentco.com (130.117.49.117) 15.247 ms be2274.mpd22.lon13.atlas.cogentco.com (130.117.50.97) 15.303 ms be2272.ccr22.lon13.atlas.cogentco.com (130.117.49.121) 15.263 ms
7 be2390.ccr21.bos01.atlas.cogentco.com (154.54.44.221) 87.329 ms 87.502 ms 87.964 ms
8 te0-7-0-5.ccr21.alb02.atlas.cogentco.com (154.54.27.153) 90.543 ms te0-0-0-5.ccr21.alb02.atlas.cogentco.com (154.54.43.10) 90.392 ms te0-4-0-5.ccr21.alb02.atlas.cogentco.com (154.54.43.14) 87.288 ms
9 38.104.52.22 (38.104.52.22) 95.514 ms 38.104.52.78 (38.104.52.78) 95.748 ms 38.104.52.30 (38.104.52.30) 95.554 ms
10 burl-lnk-70-109-168-139.ngn.east.myfairpoint.net (70.109.168.139) 100.010 ms 99.938 ms 99.894 ms
11 fttp05-pos1-0.cncdnh.fast.myfairpoint.net (64.222.166.135) 129.889 ms 131.237 ms 130.564 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

from lv (buyvm):

 

[raindog308]

 

LowEndNuclearWarRedundancy.

This will make a great movie.  After the nuclear ruin, @KuJoe walks the Ruin, rebuilding SD.  Just a man, his gun, and the last Debian CD-R in the world.