EAN-130001100001140   EAN-13 barcode 0001100001140
UPC-A001100001140   UPC-A barcode 001100001140
UPC-E00111410   UPC-E barcode 00111410
Product Name0001100001140
Amazon.com12-09-2018 7:44:48am
UPCChecker.com12-09-2018 7:44:49am
Upcdatabase.org12-09-2018 7:44:49am
Created02-28-2014 5:52:18pm
Modified12-09-2018 7:44:48am
MD54a54f077482dc8ed367f3a89763fa9fe
SHA256ecd036381c33b6a30a1ff7ff6e03b87d81675174f04983335e66921da07fe6ce
Search Googleby EAN or by Title
Query Time0.0011342

This product was recently detected and it could take some time for us to locate more information. You can check back later or you can contribute to the site by entering the additional information to this page.

We do our best to track down as much information as possible about each product but in the end, it takes people like you to help us out by looking at the products and adding information. After all, we can't get our hands on every product in the database.

We have web bots that go out into the wild and try to find additional data but they can only do so much. That is why we rely on the public and manufacturers to provide quality data.

Hopefully, what you are finding here is of value and you will continue to use the site and to help us by adding more data. We really appreciate every bit of help we get.


Article of interest

This is just a general comment to those that might be interested in some technical info about our site and how Google interacts with it.

Google is frigging amazing!

Their programmers are very curtious when it comes to their spiders and how they interact with various web sites. Apparently, they are sensative to the load that their spiders place on a web server and do a darn good job when it comes to not overloading a server.

Another major search engine is not quite so nice. If you don't tell them to leave you alone, they will hammer the heck out of your site and potentially bring you to your knees.

Over the past vew days, we have been doing a massive system backup to a couple new off-site backup servers. Normally, this process is pretty quick but because these were new servers they required fully syncronization. Well, I forgot to take into account the drain this could place on our server and I let more than one backup run at a time.

This caused our main server to experience a high load for several days. Google detected this load and backed off its crawling process which was very kind of them. The only bad thing is that when Google backed off, our monitoring process (mostly manual at this point) assumed everything was only slightly higher than normal.

Google may be awesome, but it can be frustrating some times too.

This cool and wonderful feature that Google has in place to prevent overloading a server had an unexpected side affect. Because Google thought our site was super busy (which it was) it reduced the number of people it was referring to the site too. DOH!

As we noticed the visitor count slowly drop we got very confused because the system load was still very high. And we noticed Google wasn't visiting as often as usual and then we saw it... The backup process had overloaded the system. Not to the extreme but enough to make Google think there was a problem. We still actually had plenty of bandwidth for real users just not as much for the bots that visit (which we limit when bandwidth is limited).

Anyway, it was a good learning experience and we are now seeing the referrals climb back up and the Google spider is picking up its pace again too.

We had to force a couple other bots (including that othe big search engine) to play nice because they were trying to take more than their share of our data.

All in all, Google is AWESOME and very powerful. So THANKS GOOGLE for playing nice with others!

Close

Search

Close

Share

Close

Dialog