1. A computer-based method for generating a demand estimate for a product, comprising:
removing from a set of auction data all but a highest bid from each unique bidder in the auction data;
determining the demand estimate by correcting a bias in the auction data caused by a set of characteristics of an auction from which the auction data is obtained using a computer-based mechanism such that the demand estimate provides an estimate of a likelihood that a consumer will purchase the product.
2. The method of claim 1, further comprising gathering the auction data.
3. The method of claim 2, wherein gathering the auction data includes searching an auction web site for the product.
4. The method of claim 2, wherein gathering the auction data includes obtaining the auction data from an auction web site.
5. The method of claim 1, wherein correcting the bias includes applying a statistical model to the auction data.
6. The method of claim 1, further comprising generating a graph of the demand estimate.
7. The method of claim 1, further comprising generating a table containing the demand estimate.
8. A system for generating a demand estimate for a product, comprising:
a set of auction data including a set of bids for the product;
price analyzer that determines an estimate of a likelihood that a consumer will purchase the product by removing from the auction data all but a highest bid from each unique bidder in the auction data and correcting a bias in the auction data caused by a set of characteristics of an auction from which the auction data is obtained.
9. The system of claim 8, further comprising means for gathering the auction data.
10. The system of claim 9, wherein the means for gathering the auction data includes means for searching an auction web site for the product.
11. The system of claim 9, wherein the means for gathering the auction data includes means for obtaining the auction data from an auction web site.
12. The system of claim 8, wherein the price analyzer corrects the bias by applying a statistical model to the auction data to obtain the demand estimate.
13. The system of claim 8, wherein the price analyzer generates a graph of the demand estimate.
14. The system of claim 8, wherein the price analyzer generates a table containing the demand estimate.
15. A method for generating a demand estimate for a product, comprising:
gathering a set of auction data that pertains to the product from an auction web site using a web client;
removing from the auction data all but a highest bid from each unique bidder in the auction data;
determining an estimate of a likelihood that a consumer will purchase the product by correcting a bias in the auction data caused by a set of characteristics of an auction corresponding to the auction data.
16. The method of claim 15, wherein determining an estimate comprises determining an estimate of a likelihood that a consumer will purchase the product at a set of possible prices for the product.
17. The method of claim 15, wherein gathering a set of auction data includes searching the auction web site for a product that is similar to the product.
18. The method of claim 15, wherein correcting a bias includes applying a statistical model to the auction data.
19. The method of claim 15, further comprising generating a graph of the demand estimate.
20. The method of claim 15, further comprising generating a table containing the demand estimate.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A method for determining a likelihood of a packet having a particular source address being received at a particular one of a plurality of proxy servers that are anycasted to a same IP address, wherein the proxy servers are part of a cloud-based proxy service and are situated between a plurality of client computing devices accessing network resources and a plurality of origin servers that serve network resources, the method comprising:
receiving, from each of the plurality of proxy servers, one or more messages that indicate source IP addresses of packets received at that proxy server that are directed to the same IP address, wherein the proxy servers receive traffic at the same IP address as a result of one or more domains resolving to the same IP address; and wherein a particular one of the proxy servers receives packets directed to the same IP address as a result of an anycast protocol implementation selecting that particular one of the proxy servers as the closest in terms of routing protocol metric used to route traffic to the proxy servers;
determining, based on the one or more messages from each of the plurality of proxy servers, a likelihood of a packet having a particular source IP address being legitimately received at each of the proxy servers;
transmitting, to each of the proxy servers, a message that indicates which source IP addresses of packets are not likely to be legitimately received at that proxy server.
2. The method of claim 1, wherein the message transmitted to each of the proxy servers includes a set of rules to rate limit packets received with source IP addresses that are not likely to be legitimately received by that proxy server.
3. The method of claim 1, wherein the message transmitted to each of the proxy servers includes a set of rules to block packets received with source IP addresses that are not likely to be legitimately received by that proxy server.
4. The method of claim 1, wherein the message transmitted to each of the proxy servers specifies the source IP addresses of packets that are likely to be legitimately received at that proxy server.
5. The method of claim 1, wherein the message transmitted to each of the proxy servers specifies the source IP addresses of packets that are not likely to be legitimately received at that proxy server.
6. The method of claim 1, wherein the step of receiving from each of the plurality of proxy servers the one or more messages that indicate source IP addresses of packets received at that proxy server that are directed to the same IP address, occurs only when the same IP address is not believed to be currently under a denial of service (DoS) attack.
7. The method of claim 1, wherein the one or more messages received from each of the plurality of proxy servers further indicates a number of packets of each source IP address received at that proxy server.
8. The method of claim 1, wherein the one or more messages are received as a result of a client-side script that is inserted by the proxy servers into web pages of domains that resolve to the same IP address, wherein the client-side script, when executed, causes a packet to be transmitted to the same IP address.
9. The method of claim 1, further comprising:
responsive to a network event that affects the likelihood of a packet having a particular source IP address being legitimately received at each of the proxy servers, transmitting a message to the proxy servers that indicates a suspension of any rate limits that have been installed as a result of transmitting the messages to the proxy servers that indicate which source IP addresses of packets are not likely to be legitimately received at the proxy servers.
10. An apparatus, comprising:
a plurality of proxy servers that are anycasted to a same IP address, wherein each of the plurality of proxy servers is configured to perform the following:
receive packets at the same IP address as a result of one or more domains resolving to the same IP address, wherein this proxy server receives the packets at the same IP address as a result of an anycast protocol implementation selecting this one of the plurality of proxy servers as the closest in terms of routing protocol metric used to route traffic to the plurality of proxy servers;
transmit one or more messages to a central server that indicate source IP addresses of the received packets; and
receive, from the central server, a message that indicate source IP addresses of packets that are not likely to be legitimately received at that proxy server; and
install, based on the received message, one or more rules to rate limit packets that are received having a source IP address that is not likely to be legitimately received at that proxy server; and
the central server coupled with the plurality of proxy servers, wherein the central server is configured to perform the following:
receive, from each of the plurality of proxy servers, the one or more messages that indicate source IP addresses of the received packets;
determine, based on the one or more messages received from the plurality of proxy servers, a likelihood of a packet having a particular source IP address being legitimately received at each of the proxy servers; and
transmit, to each of the proxy servers, the message that indicates which source IP addresses of packets are not likely to be legitimately received at that proxy server.
11. The apparatus of claim 10, wherein the message transmitted to each of the proxy servers includes a set of rules to rate limit packets received with source IP addresses that are not likely to be legitimately received by that proxy server.
12. The apparatus of claim 10, wherein the message transmitted to each of the proxy servers includes a set of rules to block packets received with source IP addresses that are not likely to be legitimately received by that proxy server.
13. The apparatus of claim 10, wherein the message transmitted to each of the proxy servers specifies the source IP addresses of packets that are likely to be legitimately received at that proxy server.
14. The apparatus of claim 10, wherein the message transmitted to each of the proxy servers specifies the source IP addresses of packets that are not likely to be legitimately received at that proxy server.
15. The apparatus of claim 10, wherein the proxy servers are configured to transmit the one or more messages to the central server that indicate source IP addresses of the received packets only when the destination IP address of those packets is not believed to be currently under a denial of service (DoS) attack.
16. The apparatus of claim 10, wherein the one or more messages to be transmitted by each of the proxy servers further indicates a number of packets of each source IP address received at that proxy server.
17. The apparatus of claim 10, wherein the one or more messages to be transmitted by each of the proxy servers are to be transmitted as a result of a client-side script that is inserted by the proxy servers into web pages of domains that resolve to the same IP address, wherein the client-side script, when executed, causes a packet to be transmitted to the same IP address.
18. The apparatus of claim 10, further comprising:
responsive to a network event that affects the likelihood of a packet having a particular source IP address being legitimately received at each of the proxy servers, transmitting a message to the proxy servers that indicates a suspension of any rate limits that have been installed as a result of transmitting the messages to the proxy servers that indicate which source IP addresses of packets are not likely to be legitimately received at the proxy servers.
19. A non-transitory computer-readable storage medium that provides instructions that, if executed by a processor, will cause said processor to perform operations for determining a likelihood of a packet having a particular source address being received at a particular one of a plurality of proxy servers that are anycasted to a same IP address, wherein the proxy servers are part of a cloud-based proxy service and are situated between a plurality of client computing devices accessing network resources and a plurality of origin servers that serve network resources, the operations comprising:
receiving, from each of the plurality of proxy servers, one or more messages that indicate source IP addresses of packets received at that proxy server that are directed to the same IP address, wherein the proxy servers receive traffic at the same IP address as a result of one or more domains resolving to the same IP address; and wherein a particular one of the proxy servers receives packets directed to the same IP address as a result of an anycast protocol implementation selecting that particular one of the proxy servers as the closest in terms of routing protocol metric used to route traffic to the proxy servers;
determining, based on the one or more messages from each of the plurality of proxy servers, a likelihood of a packet having a particular source IP address being legitimately received at each of the proxy servers;
transmitting, to each of the proxy servers, a message that indicates which source IP addresses of packets are not likely to be legitimately received at that proxy server.
20. The non-transitory computer-readable storage medium of claim 19, wherein the message transmitted to each of the proxy servers includes a set of rules to rate limit packets received with source IP addresses that are not likely to be legitimately received by that proxy server.
21. The non-transitory computer-readable storage medium of claim 19, wherein the message transmitted to each of the proxy servers includes a set of rules to block packets received with source IP addresses that are not likely to be legitimately received by that proxy server.
22. The non-transitory computer-readable storage medium of claim 19, wherein the message transmitted to each of the proxy servers specifies the source IP addresses of packets that are likely to be legitimately received at that proxy server.
23. The non-transitory computer-readable storage medium of claim 19, wherein the message transmitted to each of the proxy servers specifies the source IP addresses of packets that are not likely to be legitimately received at that proxy server.
24. The non-transitory computer-readable storage medium of claim 19, wherein the step of receiving from each of the plurality of proxy servers the one or more messages that indicate source IP addresses of packets received at that proxy server that are directed to the same IP address, occurs only when the same IP address is not believed to be currently under a denial of service (DoS) attack.
25. The non-transitory computer-readable storage medium of claim 19, wherein the one or more messages received from each of the plurality of proxy servers further indicates a number of packets of each source IP address received at that proxy server.
26. The non-transitory computer-readable storage medium of claim 19, wherein the one or more messages are received as a result of a client-side script that is inserted by the proxy servers into web pages of domains that resolve to the same IP address, wherein the client-side script, when executed, causes a packet to be transmitted to the same IP address.
27. The non-transitory computer-readable storage medium of claim 19, wherein the operations further comprise:
responsive to a network event that affects the likelihood of a packet having a particular source IP address being legitimately received at each of the proxy servers, transmitting a message to the proxy servers that indicates a suspension of any rate limits that have been installed as a result of transmitting the messages to the proxy servers that indicate which source IP addresses of packets are not likely to be legitimately received at the proxy servers.