5 / 7
Oct 2010
The datacenter facility where we colocate our primary servers that operate the E-junkie service and Web site has notified us of scheduled maintenance events which may result in a brief disruption in service in the wee hours (Midnite-3am MST/PDT) of October 20, 21, and/or 22, 2010:



As you know, we are committed to no downtime, and redundancy in our operations. Accordingly we will be upgrading our single-unit core to a two-unit core. The core will be upgraded to 8Gbps of connectivity, and a redundancy of both inside (core) and outside (edge) connections.



There will be outages of between 5-10 minutes for Tucson datacenter colocation customers and dedicated Internet access circuit customers.





In this case, "Tucson customers" would refer to E-junkie itself, along with their other clientele colocated at or connected through their Tucson facility. Our remote backup servers should take up the slack if the above maintenance/upgrade activity results in any connectivity outages at our Tucson servers' location, so any actual disruption to E-junkie services should be even briefer than the scheduled datacenter outages mentioned above.

  • created

    Oct '10
  • last reply

    Oct '10
  • 6

    replies

  • 1.4k

    views

  • 4

    users

I'm seeing extremely slow load times when entering your zip code in the cart, so long in fact that it appears to the customer that the checkout is not working. This is eventually followed by a Shipping amount of "-error-." Anything we need to know regarding this maintenance??

Furthermore, when attempting to actually check out, an alert pops up with: "Please select the Country, enter a valid ZIP/Postal Code, and press the UPDATE CART button." However, those have already been entered/selected. We are officially dead in the water until this is resolved. Please advise.

We've had a handful of reports about this issue, but we are not able to duplicate the error at all. I've tested your carts and shipping is coming up fine with no delays.



Whatever caused the problem was likely not related to the maintenance, since that happened in the wee hours of the morning rather than around 8 AM MST, but the problem is no longer occurring.

It is indeed coming up fine now. Something has changed. What was it?

We're still looking into that, but we don't expect to see the issue come up again.