We have been trying to discover how a group of Rogers IPs are related to one another. Our results so far are illustrated by the ball-of-string to the right, where each strand represents a user who's IP can be seen shifting from one IP to another. We saw in
the last post, however, that one of them, 66.185.84.74, was a proxy server. It is listed as a proxy server in the logs of truehits.net from
April 19th, 2003, and December
23rd and
26th, 2004. And, by a lucky chance, it attracted the attention of John Walker of AutoCad (
here), who discussed how such a proxy might affect one's logs.
This raises the question whether there are other proxies among these IPs, and since we found this Rogers proxy at truehits.net, this is obviously the first place to look. These other Rogers IPs are listed as proxy servers in its logs on the following dates:
- 66.185.84.72: Dec. 8, 2004
- 66.185.84.74: April 19, 2003; Dec. 23 and 26, 2004 (see above)
- 66.185.84.76: Jan. 1, 2003; Jan. 5, 2003; Jan. 8, 2003; July 12, 2003; July 17, 2003, July 25, 2003; Nov. 1, 2003; Nov. 6, 2003; Nov. 11, 2003
- 66.185.84.77: Dec. 21, 2004
- 66.185.84.78: June 13 2003; June 14 2003
- 66.185.84.79: Jan. 2, 2005
- 66.185.84.80: Mar. 6, 2005
- 66.185.84.196: Aug., 2002
- 66.185.84.200: Mar. 24, 2002; Apr. 7, 2002
- 66.185.84.202: Feb. 9, 2003; April 7, 2003
- 66.185.84.204: Jan. 7, 2003; Feb. 2, 2003
This means that about half of the IPs that we have been considering are proxy servers. Adding this to our ball of string, with each confirmed proxy circled (the colour is according to year), produces the graphic at the left.