Isn’t that because you set the cache duration of tweet rules to be so?
Negative. The cache rules were set at the default of 20 minutes.
Here is the action from the logs for a period of less than a minute:
[19/Feb/2014:09:28:55 -0800] 0 166.78.242.205 80 hotelguru.com 200 /wp-cron.php ?doing_wp_cron=1392830935.0833320617675781250000
[19/Feb/2014:09:28:58 -0800] 5254 31.41.218.144 80 hotelguru.com 200 /wp-login.php
[19/Feb/2014:09:28:56 -0800] 17624 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:28:58 -0800] 43315 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:01 -0800] 0 166.78.242.205 80 hotelguru.com 200 /wp-cron.php ?doing_wp_cron=1392830941.2539169788360595703125
[19/Feb/2014:09:29:02 -0800] 0 166.78.242.205 80 hotelguru.com 200 /wp-cron.php ?doing_wp_cron=1392830941.6662099361419677734375
[19/Feb/2014:09:29:00 -0800] 43315 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:00 -0800] 5254 31.41.218.144 80 hotelguru.com 200 /wp-login.php
[19/Feb/2014:09:28:59 -0800] 17624 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:00 -0800] 17624 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:01 -0800] 43316 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:02 -0800] 0 166.78.242.205 80 hotelguru.com 200 /wp-cron.php ?doing_wp_cron=1392830942.0365209579467773437500
[19/Feb/2014:09:29:03 -0800] 5254 31.41.218.144 80 hotelguru.com 200 /wp-login.php
[19/Feb/2014:09:29:04 -0800] 43315 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:03 -0800] 17624 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:06 -0800] 0 166.78.242.205 80 hotelguru.com 200 /wp-cron.php ?doing_wp_cron=1392830945.9725170135498046875000
[19/Feb/2014:09:29:05 -0800] 17624 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:07 -0800] 59 157.55.32.81 80 hotelguru.com 200 /robots.txt
[19/Feb/2014:09:29:05 -0800] 98 71.128.200.64 80 hotelguru.com 200 /wp-admin/admin-ajax.php
[19/Feb/2014:09:29:06 -0800] 43315 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:05 -0800] 17624 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:07 -0800] 0 166.78.242.205 80 hotelguru.com 200 /wp-cron.php ?doing_wp_cron=1392830946.8446938991546630859375
[19/Feb/2014:09:29:06 -0800] 43315 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:05 -0800] 5254 31.41.218.144 80 hotelguru.com 200 /wp-login.php
[19/Feb/2014:09:29:10 -0800] 5254 31.41.218.144 80 hotelguru.com 200 /wp-login.php
[19/Feb/2014:09:29:11 -0800] 5254 31.41.218.144 80 hotelguru.com 200 /wp-login.php
[19/Feb/2014:09:29:09 -0800] 0 166.78.242.205 80 hotelguru.com 200 /wp-cron.php ?doing_wp_cron=1392830948.6882119178771972656250
[19/Feb/2014:09:29:11 -0800] 5254 31.41.218.144 80 hotelguru.com 200 /wp-login.php
[19/Feb/2014:09:29:09 -0800] 43315 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:09 -0800] 17624 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:13 -0800] 0 166.78.242.205 80 hotelguru.com 200 /wp-cron.php ?doing_wp_cron=1392830952.9361839294433593750000
[19/Feb/2014:09:29:12 -0800] 17624 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:13 -0800] 0 166.78.242.205 80 hotelguru.com 200 /wp-cron.php ?doing_wp_cron=1392830953.6808989048004150390625
[19/Feb/2014:09:29:13 -0800] 43314 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:12 -0800] 5254 31.41.218.144 80 hotelguru.com 200 /wp-login.php
[19/Feb/2014:09:29:12 -0800] 17624 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:13 -0800] 43315 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:14 -0800] 0 166.78.242.205 80 hotelguru.com 200 /wp-cron.php ?doing_wp_cron=1392830954.6547310352325439453125
[19/Feb/2014:09:29:12 -0800] 17624 166.78.242.205 80 hotelguru.com 200 /index.php
[19/Feb/2014:09:29:14 -0800] 0 166.78.242.205 80 hotelguru.com 200 /wp-cron.php ?doing_wp_cron=1392830954.7244229316711425781250
As soon as I deactivated the plugin, that traffic stopped.
