Paitient Zero Premium Format!?!?!?!?!?

[NIGHTCRAWLER]

the next grail will be the classic ironman with a repainted stealth look. you heard it here first.

Na, the next grail with be Namor holding his trident

 

[P1X4R]

If he's not doing anything to fix it, then YES.

If he needs help, then get the resource to do so. On the other hand, if the owner is not going to invest some money in improving the infrastructure, then there's nothing he can do.

So how many more years does the customer needs to experience the same thing over and over again?

i'm wondering if it's the network bandwidth/ISP (?) that they're using?

check out the partial traceroute

4 cr1.sffca.ip.att.net (12.122.137.2) 73.919 ms * 73.966 ms
5 cr1.cgcil.ip.att.net (12.122.4.122) 73.764 ms 74.054 ms 74.294 ms
6 cr2.cgcil.ip.att.net (12.122.2.54) 73.964 ms 73.627 ms 73.640 ms
7 cr1.n54ny.ip.att.net (12.122.1.1) 74.219 ms 73.675 ms 73.635 ms
8 tbr1.n54ny.ip.att.net (12.122.16.146) 73.973 ms 74.205 ms 73.930 ms
9 gar1.nwrnj.ip.att.net (12.122.84.41) 73.550 ms 73.361 ms 73.100 ms
10 corel.ewr.datapipe.net (12.119.140.22) 73.860 ms 73.620 ms 73.704 ms
11 vl12.dist1-1.ewr.datapipe.net (64.106.128.29) 73.936 ms 73.695 ms 73.741 ms

and look at the current ping times

ping www.sideshowtoy.com
PING www.sideshowtoy.com (64.27.100.78) 56(84) bytes of data.
64 bytes from 64.27.100.78: icmp_seq=1 ttl=116 time=73.9 ms
64 bytes from 64.27.100.78: icmp_seq=2 ttl=116 time=73.6 ms
64 bytes from 64.27.100.78: icmp_seq=3 ttl=116 time=73.6 ms
64 bytes from 64.27.100.78: icmp_seq=4 ttl=116 time=73.7 ms
64 bytes from 64.27.100.78: icmp_seq=5 ttl=116 time=74.2 ms
64 bytes from 64.27.100.78: icmp_seq=6 ttl=116 time=73.5 ms
64 bytes from 64.27.100.78: icmp_seq=7 ttl=116 time=73.7 ms

 

[The Mike]

the next grail will be the classic ironman with a repainted stealth look. you heard it here first.

Still wouldn't be accurate.

 

[ComputerFly]

Seems better from me, and I'm farther away:

 

[ComputerFly]

LOL!!! Sideshow's server is in New Jersey!!!

So actually, I'm closer than you Ed...

 

[Kratos]

the next grail will be the classic ironman with a repainted stealth look. you heard it here first.

Can't see it happening
But I could see the Patient Zero becoming a potential Grail

 

[P1X4R]

LOL Steve!

ok, you have me there! you've got about a 30+ millisecond advantage over us West Coasters but sometimes it's not about the precious connection time but how you get to the link the best possible way.

usually i avoid the newsletter. it wastes too much time by a few extra clicks hunting for it. obviously the best is to just go to the direct order link. that's fairly easy to find once the official sneak pics are posted from sideshow since that leads to the item number. another way is to refresh the pre-order page but i noticed a few times that the newest aren't always at the top of the page. this time though i ended up using the "search by" method. in this case "patient zero" which gave me the link when it finally went up. :chew

 

[daliman11]

that pf looks awesome can't wait to see it reviewed

 

[ComputerFly]

Ed, I wasn't saying "Nyah Nyah, I'm closer" I was saying maybe that's why my response times were lower than yours (because I'm closer to NJ). I originally figured mine would be worse than yours, figuring I had to get from here to Cali. Then I did an IP lookup on it, and discovered the server in NJ... The funny part was that the server was in NJ, not that my time was lower.


Those are great tips for getting in to the pre-order fast. Now, please stop informing the competition...

 

[P1X4R]

it's possible that internet bottlenecks aren't necessarily location driven.

glad you liked the tips.

 

[P1X4R]

ok, i'm going to throw out the ping times theory out the window. i just did a test from a few random servers.

Japan
ping www.sideshowtoy.com
PING www.sideshowtoy.com: (64.27.100.78): 56 data bytes
64 bytes from 64.27.100.78: icmp_seq=0 ttl=108 time=200 ms
64 bytes from 64.27.100.78: icmp_seq=1 ttl=108 time=191 ms
64 bytes from 64.27.100.78: icmp_seq=2 ttl=108 time=190 ms
64 bytes from 64.27.100.78: icmp_seq=3 ttl=108 time=191 ms
64 bytes from 64.27.100.78: icmp_seq=4 ttl=108 time=191 ms

Germany
PING www.sideshowtoy.com: 56 data bytes
64 bytes from 64.27.100.78: icmp_seq=0. time=107. ms
64 bytes from 64.27.100.78: icmp_seq=1. time=106. ms
64 bytes from 64.27.100.78: icmp_seq=2. time=107. ms
64 bytes from 64.27.100.78: icmp_seq=3. time=107. ms
64 bytes from 64.27.100.78: icmp_seq=4. time=109. ms

here's the killer. a server in Canada with ping times to yahoo and sideshow. you would think yahoo would be faster.

Canada
ping www.yahoo.com
PING www.yahoo-ht3.akadns.net (209.191.93.52) 56(84) bytes of data.
64 bytes from f1.www.vip.mud.yahoo.com (209.191.93.52): icmp_seq=0 ttl=45 time=88.6 ms
64 bytes from f1.www.vip.mud.yahoo.com (209.191.93.52): icmp_seq=1 ttl=45 time=85.7 ms
64 bytes from f1.www.vip.mud.yahoo.com (209.191.93.52): icmp_seq=2 ttl=45 time=86.0 ms
64 bytes from f1.www.vip.mud.yahoo.com (209.191.93.52): icmp_seq=3 ttl=45 time=85.4 ms

ping www.sideshowtoy.com
PING www.sideshowtoy.com (64.27.100.78) 56(84) bytes of data.
64 bytes from 64.27.100.78: icmp_seq=0 ttl=113 time=21.3 ms
64 bytes from 64.27.100.78: icmp_seq=1 ttl=113 time=17.8 ms
64 bytes from 64.27.100.78: icmp_seq=2 ttl=113 time=596 ms
64 bytes from 64.27.100.78: icmp_seq=3 ttl=113 time=17.7 ms
64 bytes from 64.27.100.78: icmp_seq=4 ttl=113 time=18.3 ms
64 bytes from 64.27.100.78: icmp_seq=5 ttl=113 time=18.1 ms

network analysis is too unpredictable. lol

 

[jbinny]

But what does it all mean, Basil??????

 

[ComputerFly]

Ed, doesn't what you did make sense?

If I understand what you did, you went to 3 servers and pinged Sideshow.

Japan, being the farthest away, had the longest response time. (6800 miles)

Germany, being the next distant, had the second longest. (3890 miles)

Canada, had the fastest of these 3, which makes perfect sense. (don't know where in Canada your server is, but if it were in Toronto it could be as little as 350 miles to the Sideshow server, which would explain the extremely fast ping times).

Summary, the farther you are away, the longer response times your going to have, just like I said above about my response time being shorter than yours.

Am I missing your point? You've been going on about the ping times..what is it your trying to show?

 

[lcummins]

Ping times really won't show us anything... there are so many issues involved that each connection would be unique and have different factors affecting the ping times.

 

[ComputerFly]

And that's what I'm saying. Why post them at all? All I'm saying is that distance is indeed a factor when attempting to ping a server. The more hops a packet has to travel through, the slower the response time. The farther away, the more hops (usually).

 

[NIGHTCRAWLER]

can't wait to see 360 view of that bad boy

 

[Darth_Pain]

LOL!!! Sideshow's server is in New Jersey!!!

So actually, I'm closer than you Ed...

No wonder why I can stroll through their site while others can't even get it to load.

 

[Kratos]

So uh whats the ES for the Reg likely to be?

 

[furystorm]

So uh whats the ES for the Reg likely to be?

1000 maybe, but I'm definately no expert. And if there are that many then the Exclusive number seems about right for a 1 in 10, not unlike the SSE Dioramas I am so enamored with. Still, I would like to see a smaller number of regulars to help keep the value of this exclusive up. 500? I always figured SS waited awhile to see how many were ordered, then determined what final edition size a regular run would have. Still, no expert.

 

[LOTRFan]

At least 1000 probably more like 1250.