Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 512

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 527

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 534

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 570

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/33/d214989360/htdocs/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/33/d214989360/htdocs/wp-includes/cache.php on line 431

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-includes/query.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-includes/theme.php on line 1109

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/33/d214989360/htdocs/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/33/d214989360/htdocs/wp-includes/http.php on line 61

Strict Standards: Non-static method K2::init() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/functions.php on line 31

Strict Standards: Non-static method K2::register_scripts() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 51

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Options::init() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 339

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::init() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 339

Strict Standards: Non-static method K2Header::get_header_width() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/header.php on line 8

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2::filter_post_comments() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 166

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458
Category Archive for ‘PA-Pres’ at Campaign Diaries
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::output_header_css() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 339

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Archive for the 'PA-Pres' Category


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Final poll watch: No late movement

Still to come today: An election night cheat sheet, anything else that events warrant and a liveblog, of course. (And the prediction thread is still alive!)

A final round of polling released over the past 12 hours includes interviews conducted on Monday, allowing us to check whether McCain benefited from any last minute movement.

The verdict: McCain does not  gain as a result of Monday polling. In fact, Obama gains in Zogby and IBD/TIPP’s national poll and holds firm in a Marist poll entirely conducted on Monday. At the state level, SUSA’s Pennsylvania poll shows Obama improving his position over the past few days and seizing a 9% lead, while Zogby’s 8 polls from battleground states have trendlines going in both directions - but no significant movement.

This means that no pollster has detected any sort of McCain improvement over the past few days. Firms that have been trying to allocate undecided have suggested that they are not likely to break heavily towards the Republican nominee. (Not to mention that in many state the impact of a late-breaking surge would be limited: at least 64% of all active registered voters cast their ballot before Election Day in Colorado.)

If McCain somehow pulls a comeback, almost no pollster will be able to bask in the glory, as even outlets that have shown a tighter race fell in line (IBD/TIPP, Zogby). The only exception is the “Battleground poll” (whose result I never included in my polling watch because they arbitrarily imposed wide swings in their weighing), whose GOP half (Tarrance) is projecting the tightest margin among all pollsters (50% to 48%). Mason-Dixon could also be somewhat vindicated: though their last batch of state polls pointed to an Obama victory, McCain was not in as dismal a situation as we’ve seen elsewhere.

In other words: for McCain to prevail, all polls (even Mason-Dixon) would have to be dead wrong. That’s happened before, but the New Hampshire primary was a highly volatile 4-day campaign - and that means that there were a lot of reasons to explain the polling fiasco. We simply do not know what would possibly explain a similar debacle today (though I tried to outline some possible scenarios here). With all of this in mind, here are the last polls of the 2008 cycle:

  • Obama leads 48% to 42% in the final IBD/TIPP tracking poll; IBD/TIPP allocates undecideds to reach a 52% to 44% Obama margin.
  • The Battleground tracking comes out with two different projections: Its Republican half (Tarrance) has Obama leading 50% to 48% while its Democratic half (Lake) has him ahead 52% to 47%. Note that this is not a trend towards McCain at all; Battleground has always shown a tighter race than other pollsters.
  • Obama leads 51% to 46% in Research 2000’s final tracking poll. That means that R2000 has the tightest final margin of all trackings - a fascinating result given that it is funded by Kos, RCP inexplicably refuses to include it in its averages and Obama had some of his largest leads through September and October in R2000.
  • Pennsylvania: Obama leads 52% to 43% in a SUSA poll conducted Friday through Monday; that’s an increase from a 7% lead Obama enjoyed in a poll released on Sunday. Obama leads 51% to 41% in a Zogby tracking poll conducted Friday through Monday (Thursday’s sample has been left out, Monday’s has been included; Obama led by 14% yesterday).
  • Virginia: Obama leads 51% to 47% in an ARG poll conducted Friday through Monday. Obama leads 52% to 45% in a Zogby tracking poll conducted Friday through Monday (Thursday’s sample has been left out, Monday’s has been included; Obama led by 6% yesterday).
  • Nevada: Obama leads 53% to 42% in a Zogby tracking poll conducted Friday through Monday (Thursday’s sample has been left out, Monday’s has been included; Obama led by 8% yesterday).
  • Ohio: Obama leads 49% to 47% in a Zogby tracking poll conducted Friday through Monday (Thursday’s sample has been left out, Monday’s has been included; Obama led by 6% yesterday).
  • Florida: Obama leads 58% to 40% in a SUSA poll conducted Friday through Monday; he leads by 18% among those who have already voted (58% of the sample). McCain leads 49% to 48% in a Datamar poll conducted Saturday and Sunday; the candidates were tied at 47% a few days ago and Obama led by 5% earlier. Obama leads 49% to 48% in a Zogby tracking poll conducted Friday through Monday (Thursday’s sample has been left out, Monday’s has been included; Obama led by 2% yesterday).
  • North Carolina: Obama leads 49% to 48% in an ARG poll conducted Friday through Monday; African-Americans make up a relatively large 24% of respondents. McCain leads 50% to 49% in a Zogby tracking poll conducted Friday through Monday (Thursday’s sample has been left out, Monday’s has been included; McCain led by 1% yesterday).
  • Missouri is tied at 49% a Zogby tracking poll conducted Friday through Monday (Thursday’s sample has been left out, Monday’s has been included; Obama led by 1% yesterday).
  • Indiana: McCain leads 50% to 45% in a Zogby tracking poll conducted Friday through Monday (Thursday’s sample has been left out, Monday’s has been included; McCain led by 5% yesterday).
  • Washington: Obama leads 56% to 40% in a SUSA poll.
  • West Virginia: McCain leads 53% to 42% in an ARG poll taken Friday through Monday.

Meanwhile, in our final down the ballot numbers:

  • Christine Gregoire pulls ahead 52% to 46% in SUSA poll of Washington’s gubernatorial race. This breaks a series of 8 SUSA polls that had the race within the MoE.

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Presidential polling: Obama closes campaign in strong position

As is fitting on the last day before an election, we were treated to a deluge of polling today, as at least 52 presidential surveys were released over the past 24 hours! (I for once devoted a separate post to congressional polls.)

Given the sheer volume of data, we could have expected to see wide discrepancies between different pollsters. Instead, there appears to be a large consensus between different outlets, both at the state level and in national polls (where most surveys gravitate towards the same mean). If the polls turn out to be wrong, absolutely all pollsters will be implicated, suggesting that there is something structural that was missed. (Mark Blumenthal takes a look at what that might be.)

Not only are polls convergent, they have also been consistent over time: Individuals polls have fluctuated a bit over the past few months, but both candidates have oscillated within the same margins since the beginning of October, with very little indication that either candidate has gained or lost ground in that time.

Today’s national polls look familiar: Obama is at or above 50% in 11 of 12 national polls (at 48% in the 12th) and he tops 51% in 10 out of 12. McCain, meanwhile, remains between 42% and 46% in all these polls. There is also no uniform trendline in these final days but the tendency of most polls to move towards high single-digit territory.

At the state level, there was a lot of polling out today, as many outlets (Rasmussen, PPP, Strategic Vision, Zogby, Quinnipiac) released their final waves of surveys. Overall, the results are strong for the Illinois Senator, who first and foremost retains his advantage in Pennsylvania: Five polls find him leading anywhere between 6% and 14%, a range we have been seeing in most surveys from the Keystone State this past week. More importantly, the trendline does not appear to be clearly heading in McCain’s direction. It will take an extraordinary amount of GOTV, big gains among undecided voters and a significant overstatement of Obama’s support for McCain to pull off these 21 electoral votes.

As for the red states, the same classification we have been using lately applies: Colorado, Virginia and Nevada are the most likely to fall in Obama’s hands, though his lead in the day’s one Colorado poll is smaller than he would like (the fact that Colorado has been so under-polled this cycle is a disgrace, as the state’s role in this year’s electoral college is in many ways more important than, say, Missouri or Ohio). Any one of these states combined to Pennsylvania would get Obama at 269; all three would offset a Pennsylvania loss.

Ohio and Florida lean Obama by the tightest of margins (Obama leads in four out of five FL poll, but all within the MoE and he leads in five out of seven OH polls, some by large margins, with one survey tied and one having McCain ahead by 2%). And that leaves as the ultimate toss-ups of the election states that should never have been competitive in the first place: North Carolina, Missouri, Indiana, Montana. The Missouri polling is especially fascinating, as three out of the day’s four polls have the contest tied.

One possible area of concern for Obama: There is evidence in some of these polls that undecided voters are closing in for McCain. That is especially the case in PPP’s polls: compared to the group’s previous polls from the same state’s, Obama’s support has remained stable while McCain has gained and the number of undecided has decreased. This could suggest some trouble for Obama (and it is one of the factors that I outlined yesterday in my post rehashing the scenarios in which McCain could surprise us). Other polls, however, other pollsters do not find similar results: Ipsos/McClatchy and Gallup both model their undecided to break evenly, and CBS News’s profile of undecided voters suggests that they are more Democratic than Republican.

One area of concern for McCain: SUSA’s polls of Georgia and North Carolina show that they predict that black turnout will be sensibly the same as it was in 2004. Given that African-Americans make up a disproportionate share of early voters, it would mean that they are significantly under-represented among tomorrow’s voters. This raises the possibility that Obama’s support remains under-represented in some of these polls.

Let’s go on to the full roundup of the day’s polls, which I have broken down for convenience given the volume of data released today. First, twelve national polls have Obama leading anywhere from 5% to 11% (5%, 5%, 6%, 6%, 7%, 7%, 7%, 8%, 9%, 9%, 9%, 11%):

  • Obama leads 51% to 43% in the final NBC/WSJ national poll conducted Saturday and Sunday.
  • Obama leads 53% to 44% in the final Marist national poll conducted entirely yesterday; Palin’s favorability rating has really dropped over the past few months.
  • Obama leads 50% to 42% in Ipsos/McClatchy’s final national poll. With all undecideds allocated, Obama leads 53% to 46%.
  • Obama leads 50% to 43% in a Fox News national poll, up form from a 3% lead late last week.
  • Trackings: Obama gains 3% in IBD/TIPP (48% to 43%), 2% in Zogby (51% to 44%), 2% in Gallup (53% to 42%, the same margin in both LV models) and 1% in Rasmussen (52% to 46%). The race was stable in Hotline (50% to 45%). He lost 1% in Research 2000 (51% to 45%), 2% in Washington Post/ABC (53% to 44%) and 4% in CBS News (51% to 42%).

Second, 5 polls from Pennsylvania:

  • Obama leads 53% to 45% in a PPP poll taken Friday through Sunday. Both candidates enjoy roughly the same party loyalty, with Obama winning big among independents.
  • Obama leads 52% to 46% in Morning Call’s tracking poll; Obama has been holding steady while McCain has been steadily gaining as independents break his way.
  • Obama leads 54% to 40% in a Zogby poll conducted Thursday though Saturday.
  • Obama leads 51% to 44% in Strategic Vision (up from a 5% lead).
  • Obama leads 50% to 40% in a Quinnipiac poll taken through last week; he led by 12% the week before.
  • SUSA has a poll of the presidential race in PA-10 only, finding Obama leading 53% to 43% in a district Kerry won by 6%.

Third, (only) five polls from the three red states that are most likely to go for Obama:

  • Colorado: Obama leads 51% to 47% in a Rasmussen poll taken Sunday; he led by 4% last week.
  • Virginia: Obama leads 52% to 46% in a PPP poll taken Friday through Sunday; the previous PPP poll conducted three weeks ago had Obama leading 51% to 43%. Obama leads 51% to 45% in a Zogby poll conducted Thursday though Saturday; he led by 7% last week. Obama leads 51% to 47% in a Rasmussen poll taken Sunday; he led by the same margin last week.
  • Nevada: Obama leads 51% to 43% in a Zogby poll conducted Thursday though Saturday; he led by 4% last week. Obama leads 51% to 47% in a PPP poll, but the poll suggests that the die has been cast: 71% of respondents say they have already voted (a proportion that sounds right given the hard data we have) and they favor Obama by 14%.

Fourth, we were treated with a deluge of Ohio polls:

  • Obama leads 48% to 46% in a SUSA poll conducted Friday and Saturday; that’s down from a 4% lead last week, but Obama leads by a stunning 24% among the third of voters who have already cast their ballot.
  • Obama leads 52% to 46% in the final University of Cincinnati poll conducted Wednesday through Sunday.
  • Obama leads 50% to 48% in a PPP poll conducted Friday through Sunday; he led 51% to 44% in a poll taken two weeks ago. McCain is gaining among whites (he has increased his lead from 49-46 to 55-43) and independents (he trailed 48-36, now 49-46, suggesting that undecideds are breaking for the Republican).
  • Obama leads 50% to 44% in a Zogby poll conducted Thursday though Saturday; Obama led by 5% last week.
  • The candidates are tied at 49% in a Rasmussen poll taken Sunday; Obama led by 4% last week.
  • Obama leads 50% to 43% in a Quinnipiac poll taken through last week; he led by 5% the week before.
  • McCain leads 48% to 46% in a Strategic Vision poll; McCain led by 3% two weeks ago.

Fifth, here are the day’s five new poll from Florida:

  • Obama leads 50% to 48% in a PPP poll conducted Friday through Sunday (the good news for Obama: half of likely voters have already cast their ballot and they favor Obama by 13%).
  • Obama leads 48% to 46% in a Zogby poll conducted Thursday though Saturday; he led by 4% last week.
  • McCain leads 50% to 49% in a Rasmussen poll taken Sunday; Obama led by 4% last week.
  • Obama leads 47% to 45% in a Quinnipiac poll taken through last week; the margin was the week before.
  • Obama leads 49% to 47% in a Strategic Vision poll; McCain led by 2% two weeks ago.

Sixth, we got a number of polls from red states that are rated toss-ups in my latest ratings:

  • Missouri: The candidates are tied at 49% in PPP’s poll conducted Friday through Sunday. Obama leads 48% to 47% in a Zogby poll conducted Thursday though Saturday. The candidates are tied at 48% in a SUSA poll; this is the same margin as last week. The candidates are tied at 49% in a Rasmussen poll taken Sunday; Obama led by 1% last week.
  • North Carolina: Obama leads 50% to 49% in a PPP poll conducted Friday through Sunday; there is no change since last week. Obama leads by 10% among those who have already voted and McCain leads by 14% among those planning to vote on Tuesday. McCain leads 49% to 48% in a Zogby poll conducted Thursday though Saturday. McCain leads leads 50% to 49% in a Rasmussen poll taken Sunday; he led by 1% last week as well. McCain leads 49% to 48% in a SUSA poll that puts the black vote at 20%; the candidates were tied two weeks ago.
  • Indiana: Obama leads 49% to 48% in a PPP poll conducted Friday through Sunday. McCain leads 49% to 44% in a Zogby poll conducted Thursday though Saturday.
  • Georgia: McCain leads 50% to 48% in a PPP poll conducted Friday through Sunday; Obama leads by 5% among early voters (57% of the sample). McCain leads 52% to 45% in a SUSA poll conducted Friday and Saturday; SUSA predicts that the black vote will compose 26% of the electorate, which seems a very low estimate (2004 was 25%, early voting is 35%). McCain leads 50% to 46% in a Strategic Vision poll.
  • Montana: Obama leads 48% to 47% in a PPP poll conducted Friday through Sunday; Ron Paul gets 4%.

Finally, a look at blue states that are rated likely or safe Obama and where the final polling suggests Obama has little to worry about:

  • Minnesota: Obama leads 49% to 46% in a SUSA poll conducted Friday and Saturday; Obama led by 6% two weeks ago.
  • New Hampshire: Obama leads 53% to 42% in UNH’s final poll conducted Friday through Sunday.

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

13th presidential ratings: One last attempt at finding McCain’s path to victory

We have been talking so much about Missouri, Indiana and North Carolina that it would also seem that Barack Obama’s electoral fortunes depend on these highly competitive states. If that were true, we would be in for quite an unpredictable Election Day indeed.

Unfortunately for McCain, a sweep of those states - even if we add Florida, Ohio, Georgia to his column - would get him no closer to the fundamental challenge he faces if he wants to reach 270 electoral votes: closing the gap in Pennsylvania, Colorado, Nevada and Virginia.

As it is looking increasingly unlikely that McCain can save Colorado given the huge share of the electorate that has already voted, all Obama needs is to hold on to Pennsylvania. The battle of Pennsylvania is sometimes portrayed as a sign McCain is still on the offensive, but this is the ultimate defensive move dictated by the need to survive.

Even if McCain can tap into the discontent of culturally conservative Democratic voters and somehow prove all Pennsylvania polls wrong, he would still face an uphill climb as he would also have to win one of Colorado, Nevada and Virginia - all states that are currently rated likely Obama. This is certainly not an easy proposal, especially in the two Southwestern states in which Obama has already locked in big majorities in early voting. And a McCain comeback in Pennsylvania would not necessarily mean that he has closed the gap in Virginia since the electoral coalitions Obama needs to assemble to win both states are different enough.

All of this suggests that Pennsylvania and Virginia are the states to watch tomorrow night, as it is difficult to imagine - though still technically possible - that Obama loses the election if he wins either of those states.

None of this is to underestimate the importance of Florida and Ohio: Both states lean ever so slightly towards the Democratic nominee, and a win in either state would surely guarantee him an electoral college majority. (The same is true in any of the other competitive red states, and the Obama organization is so dominant in some of them that for him to win there but not in other states would not surprise me.) But saying that the election’s fate is in the hands of Florida, Ohio or in states other than Pennsylvania, Virginia, Colorado and Nevada would be overstating McCain’s chances of survival.

Since the first presidential ratings I posted on June 4th, there has been an unmistakable shift towards Obama. Of the nine states that were then rated toss-ups (CO, MI, NV, NH, NM, OH, PA, VA and WI), eight are now in the likely Obama column and one in the lean Obama column; all states that were rated lean McCain are now toss-ups, and all states that were rated lean Obama are now likely Obama. And the GOP base has significantly eroded: Of the eight states that were listed as likely McCain, four are now toss-ups - as would Alaska have been had McCain not picked Sarah Palin as his running-mate.

Without further delay, here are the thirteenth presidential ratings (states whose ratings have been changed towards Obama are colored blue, those whose ratings have been changed towards McCain are colored red):

  • Safe McCain: Alabama, Alaska, Idaho, Kansas, Kentucky, Mississippi, Nebraska (at large + 3rd congressional district), Oklahoma, Utah, Tennessee, Texas, Wyoming (99 EVs)
  • Likely McCain: Arkansas, Louisiana, Nebraska’s 1st district, South Carolina, South Dakota, West Virginia (29 EVs)
  • Lean McCain: Arizona, Nebraska’s 2nd district (11 EVs)
  • Toss-up: Florida, Georgia, Indiana, Missouri, Montana, North Carolina, North Dakota (85 EV)
  • Lean Obama: Ohio (20 EVs)
  • Likely Obama: Colorado, Iowa, Maine (at-large + 1st district + 2nd district), Michigan, Minnesota, Nevada, New Hampshire, New Mexico, Pennsylvania, Virginia, Wisconsin (96 EVs)
  • Safe Obama: California, Connecticut, DC, Delaware, Hawaii, Illinois, Maryland, Massachusetts, New Jersey, New York, Oregon, Rhode Island, Vermont, Washington (185 EVs)

This gives us the following map and totals:

  • Safe + Likely Obama: 286 electoral votes
  • Safe + Likely + Lean Obama: 311
  • Toss-up: 85
  • Safe + Likely + Lean McCain: 142
  • Safe + Likely McCain: 128

I will naturally not attempt to provide an explanation for every single one of these ratings and will concentrate instead on those that have shifted over the past week:

Arizona, likely McCain to lean McCain: This seemingly last-minute development was a long time coming: Arizona polls have shown a surprisingly tight race for months, and McCain’s first signs of vulnerability came when he failed to break 50% in the state’s primary on Super Tuesday. But no one really believed that McCain’s home state could possibly be that competitive and, despite some occasional noise about an optimistic state Democratic Party, the Obama campaign did not make a move. Until this week, that is, when a big wave of polls showing McCain’s lead within the margin of error forced Obama into action; his campaign bought air time in Arizona and mobilized state volunteers.

It’s hard to think of a scenario in which Arizona is the decisive state, but at the very least, Arizona’s yearning to be a battleground state is a very good sign for Democrats in future presidential elections, and it will pay dividends at the House level, where Democrats are poised to pick up one to two seats after the two they won over in 2006.

Georgia, lean McCain to toss-up: It’s hard to believe that we are thinking of Georgia as a battleground state - let alone as a toss-up - but until Republicans prove that they are enthusiastic enough to actually vote, they are facing a catastrophe in the state: More than half of the electorate cast an early ballot, and African-Americans make up 35% of those voters - up from the 25% they represented in 2004. If strong Republican and white turnout on Tuesday does not push that number south to 30-31%, Barack Obama will be ideally placed for a (somewhat unexpected) pick-up. His campaign had invested in the state throughout the summer but went dark in mid-September, in the aftermath of the GOP convention; they are now back, airing at least one of ad tying McCain to President Bush.

Louisiana, safe McCain to likely McCain: Merely mentioning this state in the context of presidential politics would have been unthinkable just a month ago, but in the current climate an upset cannot be ruled out in any states that have a history of voting Democratic. Of course, Louisiana’s situation is complicated by the post-Katrina migrations, and no one truly knows whether the African-American population is large enough for a Democrat to pull off victory in a competitive race here. Mary Landrieu’s fate is, of course, far more dependent on this question than Obama’s.

Nevada, toss-up to likely Obama: Different forces have conspired to make Nevada look like a likely Obama pick-up. For one, he dominates among Hispanics by margins that Al Gore and John Kerry would be jealous of, as well as among the West’s independent voters, who have always been one of his strongest constituencies. Polls released over the past 10 days by CNN/Time, Suffolk, Research 2000 show Obama has jumped to a commanding lead that rivals his advantage in Colorado. As if this was not enough, early voting is looking very promising for Obama. In Clark County and Washoe County, which together account for 87% of registered voters, the gap between Democratic and Republican early voters is far larger than that of the electorate at large; if conservatives do not vote at a far higher pace, the GOP could not only lose the state at the presidential level but also one or both of its House seats.

New Hampshire, lean Obama to likely Obama: I am weary of underestimating McCain in this state, but all polls have shown a very clear trend towards the Democrat over the past few weeks, who now leads by double-digits in most polls. The UNH/WMUR, surely the most trusted poll in the state, just released its final survey showing Obama leading by 11% and holding a big lead among independents. Who knew New Hampshire independents would prove McCain’s undoing?

New Jersey, likely Obama to safe Obama: Once upon a time, Republicans believed that the September 11th effect would swing the Garden State their way, and Bush made a lot of progress in this state between 2000 and 2004. How times have changed, as Obama has now seized a dominant lead in nearly all of the state’s polling. New Jersey typically flirts with Republicans for a while before giving itself to a Democrat reluctantly, but even that pattern hasn’t really held true this year, as McCain only came close to making the state competitive in the immediate aftermath of the Republican convention.

South Carolina, safe McCain to likely McCain: Just as in Louisiana, an Obama victory in South Carolina would mean that the Democratic nominee is on his way to an electoral college landslide of well above 400 EVs. But if Obama clinches a 10% win in the popular vote, it’s not inconceivable that states like South Carolina would fall in his column. A recent Mason-Dixon poll showed McCain leading by only 6% in a state Bush carried by 17%. The boost in African-American turnout that we have been seeing in other states’ early voting could help Obama close the gap by a few more points.

Washington, likely Obama to safe Obama: Just as he believed he could put the Northeast in play, John McCain once had ambitions in the Pacific Northwest. But Barack Obama’s uncommon strength among the region’s independents (evidenced by the fact that this was the one region in which Obama ran consistently ahead of Hillary Clinton in general election polls) undercut McCain’s potential; also helping Obama is the fact that blue-collar voters in the West are less resistant, making it easier for him to unify the Democratic base. The result is an impressive lead that would have made Al Gore jealous. The main question in this state is whether Obama’s margin of victory is big enough to guarantee that Gregoire survives.

West Virginia, lean McCain to likely McCain: The site of Hillary Clinton’s greatest triumph was the most unlikely of states for Barack Obama to score an upset; the state is filled with blue-collar white Democrats who have not voted for a Democratic presidential candidate for more than a decade. But a wave of polls in late September and early October showed a highly competitive contest, and Obama (presumably not sure of what to do with the millions he had in the bank) decided to invest in the state’s airwaves. However, Obama has been unable to make more progress over the past few weeks, and most polls that have been released over the past three weeks have McCain solidifying his position and holding a lead that hovers around the 10% mark. Obama was not even able to force McCain to spend time playing defense here. That said, that the state even got on the list of potential battleground states is a testament to how much the economic crisis transformed the presidential race.

History of Campaign Diaries’ electoral ratings:


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: McCain tightens national race and PA but remains far behind; McConnell pulls ahead

Update: Two new national polls should help Obama supporters sleep tonight. First, it appears that CBS News is now also conducting a tracking poll, as they just released their second national poll in two days. The margin remains the same, 54% to 41% for Obama among likely voters. Second, the final Gallup/USA Today poll just came out and finds Obama leading 53% to 42% among likely voters; this poll was conducted Friday through today, and carries a huge sample of more than 2400 respondents. Obama led by 7% three weeks ago in this poll, meaning that there is no consistent evidence that the race has tightened. [To make things clear: It appears that this latter poll is Gallup's tracking poll released half-a-day early.]

Original post: McCain has made gains nationally, and there are some signs undecided voters appear to be breaking towards the Republican more than towards his opponent (all polls do not agree on this). He has made gains in Pennsylvania. But 48 hours from polls closing, he is still in a deep hole at the national level and in a number of states that have become must-wins, starting with the Keystone State.

Three new Pennsylvania polls conducted over the past three days have Obama leading by 6% and 7%, certainly a smaller margin than Obama enjoyed just 10 days ago (he has lost 6% in Morning Call in four days and 5% in SUSA in a week) but still a substantial advantage. Unless something dramatic happens tomorrow, it is hard to imagine how McCain can reverse a deficit that all polls agree is at least in the mid-single digits. (Furthermore, Rasmussen’s poll conducted yesterday has him gaining 2% for a 6% lead; since we have to assume that polls are dramatically understating McCain’s support in Pennsylvania if we want to seriously look at the possibility of his comeback bid seriously, which makes trendlines very important.)

Pennsylvania is not a state in which Democrats are likely to be caught by surprise; it is a state in which they have a strong operation and a machine that allowed Al Gore and John Kerry to eke out narrow victories in the past two presidential elections. It is also a state in which they have made gains over the past four years (just read today’s “one year ago today” excerpt in the sidebar). On the other hand, it is a state in which racial factors could disrupt the results if there is indeed such a thing as a Bradley effect; it is also a state in which there is no early voting, meaning that Obama has not locked in any state. In other words, it is as good a state as any for McCain to make his last stand.

At the national level, the bottom line remains the same: Pew and CNN released their final polls, and, while the latter shows McCain gaining a massive 9% in one week as undecideds heavily break towards him, both show Obama retaining a comfortable lead. Similarly, the tracking polls are going in both directions, suggesting most of the movement is statistical noise, and all but IBD/TIPP find a solid lead for the Illinois Senator. Overall, Obama is at or above 50% in eight of the nine national polls released today; McCain’s support ranges from 43% to 46%.

Despite what we are hearing left and right, this suggests that there isn’t that much discrepancy between national polls. And even if a number of surveys suggests that undecided voters are moving towards the Republican nominee, he will have to grab the lion share of undecideds while also pulling away support from Obama. That’s a tall order three days from the election, especially because a fair amount of remaining undecideds are disgruntled Republicans unhappy with Bush. Getting them home is a necessary condition for McCain to mount a comeback, but it is not sufficient.

What is perhaps most worrisome for McCain is that Pennsylvania might not even matter if Obama loses the Keystone State but sweeps Colorado, Nevada and Virginia - which new polls suggests he very well might, despite some tightening in polls from the Old Dominion.

However, here is what gives Republicans some hope: For one, the movement among undecideds. Second, the belief that nearly all pollsters are using a false turnout model. Today’s seven Mason-Dixon polls force us to take that possibility seriously, as Mason-Dixon is a very serious polling outfit that has had great success in past cycles. Like seemingly every other poll they have released this cycle, Mason-Dixon’s polls are more favorable to McCain than other pollsters, suggesting that if Mason-Dixon had a national tracking poll they would find a somewhat tighter race than other firms. The early voting data suggests that turnout will be favorable to Democrats, but such disputes are of course why elections are not decided by polls but by voters… (Note, also, that Mason-Dixon’s polls were conducted Tuesday and Wednesday, making them somewhat outdated.)

  • Obama leads 53% to 46% in CNN’s final national poll conducted Friday and Saturday. Obama has a 8% lead in a four-way race. He led by 5% in a poll conducted two weeks ago.
  • Obama leads 52% to 46% among likely voters in Pew’s final national poll, conducted Thursday through Saturday. This is quite a drop from Pew’s poll conducted the previous week in which Obama led by 15% among likely voters (53% to 38%, implying that undecided voters have heavily broken towards the Republican). Obama leads by 11% among registered voters. 47% are sure they will not vote for McCain, while only 38% say the same about Obama.
  • Trackings: Obama gains 2% in Washington Post/ABC (54% to 43%), 1% in Zogby (50% to 44%). The margin is stable in Rasmussen (51% to 46%), in CBS News (54% to 41%) and Research 2000 (51% to 44%). Obama loses 1% in Gallup (52% to 43%, though he loses 2% in the LVT model for an 8% lead), 2% in Hotline (50% to 45%) and in IBD/TIPP (47% to 45%). Obama’s leads are thus: 2%, 5%, 5%, 6%, 7%, 9%, 11%, 13%.
  • Pennsylvania: Obama stops the bleeding in a Rasmussen poll taken Saturday, leading 52% to 46%; that’s up from the 4% he enjoyed in a Thursday poll but 1% down from a poll taken on Monday. Obama leads 52% to 45% in Morning Call’s tracking poll, his smallest lead since October 1st. Obama lead 51% to 44% in a SUSA poll conducted Thursday and Friday (he led by 12% two weeks ago).
  • Virginia: Obama leads 50% to 46% in a SUSA poll conducted Thursday and Friday, the tightest margin since mid-September. Obama led between 6% and 10% in the past four SUSA polls, though most of the change in this poll can be attributed to a much tighter partisan breakdown. Obama leads 47% to 44% in a Mason Dixon poll conducted Wednesday and Thursday. Of the 9% who are undecided, 75% live outside of Northern Virginia and more than 90% are white. Obama led by 2% ten days ago.
  • Colorado: Obama leads 49% to 44% in a Mason Dixon poll conducted Tuesday and Wednesday. Obama leads among independents by an impressive 25%.
  • Nevada: Obama leads 47% to 43% in a Mason Dixon poll conducted Tuesday and Wednesday. That margin is just within the MoE.
  • Ohio: McCain leads 47% to 45% in a Mason Dixon poll conducted Tuesday and Wednesday. He led by 1% two weeks ago. Obama leads 52% to 46% in a Columbus Dispatch poll that was conducted by mail and that should thus be taken with a huge grain of salt; it widely overstated Democratic support in 2006 though it has also had successes
  • North Carolina: McCain leads 49% to 46% in a Mason Dixon poll conducted Tuesday and Wednesday; the candidates were tied two weeks ago.
  • Missouri: McCain 47% to 46% in a Mason Dixon poll conducted Tuesday and Wednesday; McCain also led by 1% two weeks ago
  • Iowa: Obama leads 54% to 37% in Selzer & Co’s very reliable Des Moines Register poll conducted Tuesday through Thursday.
  • Minnesota: Obama leads 53% to 42% in a Star Tribune poll. He led by the same margin two weeks ago.
  • New Mexico: Obama leads 52% to 45% in a SUSA poll; Obama leads by 19% among the 60% of voters who say they have already voted.

Meanwhile, in down the ballot polls:

  • Kentucky, Senate race: The two pollsters that had found a dead heat in mid-October now find McConnell pulling ahead. SUSA, which had a tie at 48%, now shows McConnell leading 53% to 45%. Mason Dixon has McConnell gaining four points to grab a 5% lead, 47% to 42%.
  • Colorado, Senate race: Mark Udall leads 47% to 43% in a Mason Dixon poll of Colorado’s Senate race, though independents vote for Udall by a large 19%.
  • Minnesota, Senate race: Al Franken leads 42% to 38% in a Star Tribune poll, with 15% going to Barkley. Two weeks ago, Franken led 39% to 36% with 18% for Barkley.
  • In NM-01, an Albuquerque Journal poll conducted this week has Democratic candidate Martin Heinrich leading 47% to 43%.

Mason-Dixon’s Colorado’s poll is further confirmation of the pollster’s GOP lean, as all other pollsters have found a wide Udall lead over the past two weeks; I am not saying that having a GOP lean disqualifies Mason-Dixon (we won’t know whose turnout model is most appropriate until Tuesday), but this one particular margin is not supported by any recent poll. Their poll from Kentucky, however, finds the same findings as SUSA and Rasmussen have this week: Senator McConnell appears to have pulled away. Lunsford is well within striking distance, but with 2 days to go the trendlines favor the incumbent.

In New Mexico, both open races remain highly competitive. (NM-01 is rated lean Democratic in my latest ratings while NM-02 is a toss-up.) The high number of undecided voters in NM-02 leaves hope to Republicans, as that is a conservative district where Republicans could come home.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: Obama maintains wide lead nationally, PA tightens a bit, Merkley might already have won

Update: A new national CBS News poll brings Democrats great news, as Barack Obama now leads 54% to 41% in a poll conducted Tuesday through Friday - up from the 11% lead Obama had in the previous CBS News poll (that one had been conducted from the 25th to the 28th). Once again, Obama is above 50%, McCain is in the low 40s. (I apologize for being repetitive, but the race has been remarkably stable for weeks).

In what is perhaps the GOP’s worst internal number of the poll, 48% say that McCain will raise their taxes versus only 47% who think Obama will do so - a sign that McCain’s tax offensive has failed to destabilize Obama. Furthermore, Obama leads by 19% among those who have already cast their ballot (about 20% of the sample), a margin that corresponds to other polls we have been seeing.

Original post: Three days from the election, Barack Obama retains a commanding lead that has barely budged over the past few weeks. There is no evidence of a last minute McCain push: the margin widens in four of the day’s seven tracking polls and it remains stable in two others. While there is some day-to-day variation, both candidates have been oscillating within the same range for weeks: Obama is at or above 51% in five of the seven tracking polls, while McCain is still in the low 40s (42% to 44%, with a high at 46% in Rasmussen).

Worse still for McCain, Obama is ahead in tracking polls that have a wide partisan gap (Washington Post/ABC, for instance) as well as those that hypothesize a far tighter breakdown (Zogby and IBD/TIPP, for instance). While the size of his lead varies according to the turnout model pollsters use, there is no disagreement on whether he is ahead.

In fact, the best news for Obama today might be that we are starting to get an answer on which turnout model best predicts this year’s election. Today marks the very first time that there is no difference between Gallup’s two likely voter models (the traditional and the expanded); Obama is usually further ahead in the expanded model. Gallup attributes this partly to the fact that 27% of respondents say they have already cast a ballot, locking them in the likely voter model no matter what their prior voting history. This suggests that sporadic voters are making a greater share of the electorate than the “traditional” LV format hypothesizes.

Then there is Zogby, of course, whose three-day average has a 5% lead for Obama but who warns that the tide might be turning. Last night, the Drudge Report treated its readers with a shock headline, proclaiming that McCain had seized a 1% lead in the Friday sample of Zogby’s tracking poll. Beyond the fact that one night samples are not meant to be treated as a full survey - which is the whole point of a tracking poll - this once again raises questions about Zogby’s theatrics and about his professionalism; it is silly to treat any movement as an earth-shattering change of momentum, and so is leaking your results to Drudge hours before posting them on your website. Furthermore, none of the six other tracking polls have found a similar Friday tightening - quite the contrary.

All of this said, Republicans can take some comfort in the latest Pennsylvania polls - and remember that there is no early voting so no one’s vote has been cast in stone just yet. The five most recent surveys - Rasmussen, Strategic Vision, Mason Dixon, Morning Call and Rasmussen again - have all found McCain gaining ground, and ARG’s first poll since mid-September has a 6% margin. Rasmussen and Strategic Vision have the exact same trend line (Obama up double-digit three weeks ago, up high single-digits last week and now up by 4% and 5%), while today marks the first time that Obama’s margin is down to single digits in Morning Call’s tracking poll.

That said, 4% to 8% gap might have made Democrats anxious three weeks ago, but we are now three days from the election and Obama remains ahead outside of the margin of error in all polls from the state. There is very little time for McCain to finish closing that gap, and it is important to note that Obama remains above 50% in both Rasmussen and Morning Call. Finally, Republicans are concentrating their efforts in the Keystone State (First Read reports that  push-polling is underway in the state) while Obama has no plan to visit the state until Tuesday, making some tightening inevitable.

The bottom-line remains: Pennsylvania has become a must-win for McCain, and even an upset in the Keystone State would need to be accompanied by a sweep of nearly all competitive red states (Obama is ahead in two new Florida polls and tied in a third, underscoring the magnitude of the challenge).

  • Trackings: Obama gains 1% in Rasmussen (51% to 46%), in Research 2000 (51% to 44%), in Gallup (52% to 42%, the same margin as in the LVT model in which Obama gains 2%; he leads by 11% among RVs) and 1% in IBD/TIPP (48% to 43%). The margin remains stable in Hotline but Obama crosses 50% (51% to 44%) and in Washington Post/ABC (53% to 44%, though independents split equally). Obama loses 2% in Zogby (49% to 44%). Obama’s leads are thus: 5%, 5%, 5%, 7%, 7%, 9%, 10%.
  • Gallup finds that 27% of likely voters have already cast a ballot and that they skew more towards Obama than other voters, a development that might explain why the two LV models now coincide.
  • Pennsylvania: Obama leads 51% to 47% in a Rasmussen poll conducted on Thursday, down from an 7% lead last week and a 13% lead three weeks ago; this is primarily due to Obama’s decline among registered Democrats, among which he receives 75% of the vote. Obama leads 52% to 44% in the Morning Call tracking poll, the first time since October 2nd the margin has been down to single-digits. Obama leads 51% to 45% in an ARG poll conducted Wednesday and Thursday. (For what it’s worth, PPP is saying that they are currently in the field in Pennsylvania and see very little for Obama to worry about.)
  • Florida: Two pollsters release their second poll in as many week - and find contrasting trends. Obama leads 49% to 47% in a Mason Dixon poll conducted Wednesday and Thursday; McCain trailed by 2% last week. The candidates are tied in a Datamar poll conducted Wednesday and Thursday (Obama led by 5% 4 days before). Finally, Obama leads 50% to 46% in an ARG poll conducted Wednesday and Thursday.
  • Iowa: Obama leads 53% to 39% in a Research 2000 poll conducted Monday through Wednesday; he led by 16% at the end of September.
  • Indiana: The candidates are tied in an ARG poll conducted Wednesday and Thursday.
  • Minnesota: Obama leads 53% to 38% in a Research 2000 poll conducted Monday through Wednesday.
  • South Dakota: McCain leads 53% to 44% in a Rasmussen poll, a margin that has tightened over the past month.
  • Safe(r) states: Obama leads 57% to 38% in a SUSA poll and 55% to 39% in a Research 2000 poll of Oregon. Obama leads 60% to 36% in a SUSA poll of California (he leads by 19% among the 42% of respondents who have already voted). McCain leads 51% to 44% in an ARG poll of Arkansas.

Meanwhile, in down the ballot polls:

  • Proposition 8 remains very close, though SUSA has the “no” gaining. Down 6% a month ago and 3% two weeks ago, the “no” is now narrowly ahead 50% to 47%. That is primarily due to movement among Democrats and African-Americans. Early voters (42% of the sample) split 50% “no” to 48% “yes.” It could still go either way, but it looks like the “no” has at least stopped the bleeding.
  • The “no” is also gaining in Proposition 4 (abortion), which now trails 46% to 40% and leads by 8% among early voters.
  • Oregon, Senate race: Jeff Merkley leads 49% to 42% in a SUSA poll conducted over the past two days. More than 70% of respondents say they have already voted, and Merkley leads by 10% among those voters. Merkley leads 48% to 42% in a Research 2000 poll conducted Monday through Wednesday; Merkley leads by 40% among those who say they have already cast a ballot.
  • Kentucky, Senate race: Mitch McConnell leads 47% to 44% in a Research 2000 poll conducted Monday through Wednesday.
  • Minnesota, Senate race: Norm Coleman leads 43% to 40% with 15% going to Barkley in a Research 2000 poll conducted Monday through Wednesday.
  • In WY-AL, GOP candidate Cynthia Lummis takes a 49% to 45% lead in a Research 2000 poll. Gary Trauner led by 1% two weeks ago.
  • In NV-03, the candidates are tied at 44% in a Mason Dixon poll; GOP Rep. Porter led by 3% three weeks ago.
  • In NV-02, GOP Rep. Heller leads 50% to 37% in a Mason Dixon poll; he led by the same margin 3% ago.

With the vast majority of Oregon ballots already cast (ballots have to have arrived by Tuesday, meaning that many voters have already mailed them in), it looks like Jeff Merkley will be the next Senator from Oregon as SUSA’s poll (as well as PPP’s yesterday) are now measuring the way the electorate has arleady voted rather than how it is going to vote). The Kentucky and Minnesota Senate races, however, are still toss-ups, particularly the latter in which the Barkley factor is too unpredictable to venture any guess as to who will come out on top. Democrats will likely have to win at least one of these two seats if they want to rise to 60 seats.

At the House level, Research 2000’s poll of WY-AL finds that the race is still within the margin of error but the trendline is worrisome for Democrat Gary Trauner: We knew that most of the undecided were Republican and that Lummis had to get those voters to come home, and this poll suggests that this might be happening. Note that this is a very important race for Democrats: Getting people like Trauner elected would give them a bench from which to potentially contest Senate races in a few cycles.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: Obama dominates CO, ties AZ, ND and IN; Wicker and Merkley solid, Franken alive, Stevens drowns

As is expected the Friday before an election, we were treated with a deluge of polls at the presidential and Senate level today, making this quite a large edition of poll watch.

It is hard to make sense of 44 presidential polls from 19 different states at once, though the fact that seven of them come from New Hampshire and find a similar result makes things far easier. These polls are also important to go over, as they were almost all conducted entirely this week (many of the state surveys that we had been considering over the past few days, whether CNN/Time, AP/GfK or Quinnipiac were taken over the week-end).

Taken together, these polls detect no sign of tightening, whether nationally (Obama is at or above 50% in five out of eight national polls and McCain is above 45% in only survey) or at the state level. In fact, it is McCain’s base that keeps eroding rather than Obama’s: We have now gotten used to seeing Missouri, Indiana and North Carolina dead-locked - if not slightly leaning in Obama’s direction - but it is stunning to see that McCain can no longer muster a lead outside of the margin of error in Arizona, Montana or North Dakota. That’s right, we have now bee treated to half-a-dozen polls this week alone that have shown McCain collapsing in his home state - with Research 2000 showing him leading by only 1%.

Obama continues to dominate in polls from the Big Three states. No new survey from Virginia was released today, but two polls from Colorado suggest that McCain might already have lost the state given that nearly half of all registered voters have already cast their ballot and Obama is leading by 7% and 10% overall in those two surveys. Obama’s huge lead among independents in almost all recent Colorado polls confirm that Western independents are likely to vote Obama; that should also help him in Nevada and in the Mountain West.

However, there might be some signs of Obama’s weakening in Pennsylvania. He remains in a dominant position, but not as clearly as he did just two weeks ago. After Mason Dixon’s 4% margin yesterday, Strategic Vision has Obama ahead by 5% today after showing him leading by 14% three weeks ago and 9% last week; and while Obama is ahead by 10% in Morning Call’s tracking, it is the first time in a more than a month that McCain has reached 43%. Because there is no early voting in Pennsylvania, it remains conceivable that McCain can pull it off - but it is obviously extremely difficult to close such a gap in the final three days.

The problem for McCain, of course, is that Obama would only have to sweep Nevada, Colorado and Virginia and Pennsylvania would not matter. Or, for that matter, could he ensure victory by picking up just one of the many other vulnerable red states: Out of six polls of Missouri, North Carolina and Indiana today, McCain leads only in one - and that’s within the margin of error and based on Obama’s low 65% among blacks. And there really is no other blue state McCain can hope to pick up. He trails widely in seven New Hampshire polls today, as well as by double digits in Minnesota, Wisconsin and Michigan:

  • Obama leads 50% to 43% in a Marist national poll conducted entirely on Tuesday. Marist had not conducted a national survey since the end of September, when Obama led by 5%.
  • Trackings: Obama gains 2% in Gallup (52% to 43%; he gains 3% in the RV and LVT models to seize an 11% and 8% lead, respectively), 1% in Hotline (48% to 41%), Washington Post/ABC (53% to 44%) and Research 2000 (51% to 45%). The race is stable in IBD/TIPP (47% to 43%) and in Zogby (50% to 43%). Obama loses 1% in Rasmussen (51% to 47%). Obama’s leads thus are: 4%, 4%, 6%, 7%, 7%, 9%, 9%.
  • Colorado: Obama leads 54% to 44% in a PPP poll conducted Tuesday through Thursday. (Early voters make up 65% of respondents (!), and they go for Obama by 17% - meaning that all he needs is 35% of remaining voters. Obama leads 60% to 36% among independents.) Obama leads 52% to 45% in an ARG poll conducted over the same period; he leads by 13% among independents. (McCain had a 3% lead five weeks ago.)
  • Pennsylvania: Obama leads 49% to 44% in a Strategic Vision poll conducted Monday through Wednesday (he led by 7% last week and by 14% three weeks ago). Obama leads 53% to 43% in the Morning Call tracking poll.
  • North Carolina: Obama leads 47% to 45% in a Research 2000 poll conducted Tuesday through Thursday. The candidates are tied at 48% in an Insider Advantage poll conducted Tuesday. Obama leads 47% to 46% in the final Civitas poll taken Monday through Wednesday (down from a 3% lead).
  • Missouri: McCain leads 50% to 47% in an Insider Advantage poll conducted yesterday. The candidates are tied at 47% in an ARG poll taken from Tuesday through Thursday.
  • Indiana: The candidates are tied at 47% in a SUSA poll, though Obama leads by 32% among early voters. Obama led by 4% last week.
  • New Mexico: Obama leads 58% to 41% in a PPP poll conducted Tuesday through Thursday.
  • Minnesota: Obama leads 57% to 41% in a PPP poll conducted Tuesday through Thursday.
  • Georgia: McCain leads 52% to 47% in a Rasmussen poll conducted yesterday (the same margin as last week). He leads 47% to 44% in a Research 2000 poll conducted Tuesday through Thursday; he led by 6% two weeks ago. He trails by 15% among early voters.
  • Montana: McCain leads 48% to 44% in a Research 2000 poll. He led by 4% also two weeks ago. Ron Paul was not included. McCain leads 49% to 46% in an ARG poll taken over the same period.
  • North Dakota: McCain leads 47% to 46% in a Research 2000 poll. The candidates were tied two weeks ago.
  • Arizona: McCain leads 48% to 47% in a Research 2000 poll conducted from Tuesday through Thursday. Obama leads by 12% among early voters. McCain leads 50% to 46% in an ARG poll conducted over the same period.
  • Michigan: Obama leads 55% to 42% in a PPP poll conducted Tuesday through Thursday. Obama leads 50% to 38% in an EPIC-MRA poll conducted from Sunday through Tuesday (Obama led by 14% the week before). Obama leads 54% to 41% in a Strategic Vision poll.
  • West Virginia: McCain leads 55% to 42% in a PPP poll. That’s a 5% expansion over a poll released two weeks ago.
  • Oregon: Obama leads 57% to 42% in a PPP poll conducted Tuesday through Thursday.
  • Mississippi: McCain leads 53% to 40% in Research 2000. Obama receives 13% of the white vote.

Meanwhile, in down the ballot surveys, where we got a staggering number of surveys today:

  • The Field poll of California has Proposition 8 losing 49% to 44% - that’s a slight narrowing from the September survey, and the vote certainly remains close.
  • Georgia, Senate race: GOP Senator Chambliss leads 47% to 46% in a Research 2000 poll, with 5% going to Buckley. Among early voters, Jim Martin leads by 17%, however. (The poll has a problem, however: Only 12% of the sample is made up of early voters even though more than a third of registered voters have already cast their ballot.) Chambliss leads 48% to 43% in a Rasmussen poll, an improvement over his 2% lead last week; Allen Buckley gets 7%.
  • An older CNN/Time poll, however, has Chambliss leading by 9% (53-44) among likely voters and by 1% (48-47) among registered voters. The CNN poll is worthless, as it is ridiculous not to include a third-party candidate when a candidate has to cross 50% to win.
  • North Carolina, Senate race: Kay Hagan leads 50% to 45% in a Research 2000 poll; she led by 4% two weeks ago. 45% to 43% in the final Civitas poll. Hagan leads 53% to 44% in a CNN poll taken earlier (from the 23rd to the 28th).
  • Mississippi, Senate race: GOP Senator Roger Wicker takes a 51% to 44% lead in a Research 2000 poll. He led by only 1% two weeks ago.
  • Minnesota, Senate race: Al Franken leads 45% to 40%, with 14% for Barkley in a PPP poll. In this poll (contrary to those that were released yesterday), Barkley draws about equally from both parties. Al Franken also leads 41% to 37% in a new MPR poll.
  • Oregon, Senate race: Jeff Merkley leads 51% to 43% in a PPP poll, with 4% going to Dave Brownlow. 59% of respondents say they have already voted, and Merkley leads by 22% among them… Merkley leads 49% to 46% in a Rasmussen poll.
  • Alaska, Senate race: Mark Begich leads 58% to 36% in a Research 2000 poll conducted after Stevens’ conviction.
  • Colorado, Senate race: Mark Udall leads 56% to 41% in a PPP poll; he leads 60% to 38% among those who have already voted. Udall leads 53% to 43% in a CNN poll.
  • Safe(r) seats: Tom Udall leads 58% to 39% in a PPP poll of New Mexico. Frank Lautenberg leads 52% to 37% in a SUSA poll of New Jersey.
  • In AK-AL, Democratic challenger Ethan Berkowitz leads 53% to 44% in a Research 2000 poll. He led by 6% two weeks ago.

In this avalanche of Senate news from a number of competitive races, most of the good news goes to Democrats. The two Udalls confirm their domination, and Jeanne Shaheen is poised to pick up the New Hampshire Senate seat as she posts leads ranging from 7% to 13% in six separate surveys. Mark Begich could join them and put Alaska in the easy pick-up column according to this second post-conviction poll, though I would still warn against underestimating Stevens.

In Oregon, Jeff Merkley appears to be closing the deal. Oregon’s mail-in voting system means more than half of the state’s voters have already sent in their ballot and Gordon Smith might already have lost his seat. Elizabeth Dole’s situation might be a bit better, and she has a few more days to recapture momentum. But early voting turnout is huge in North Carolina, leaving her with a reduced pool of voters who could still change their vote. Today’s polls (as with most surveys that have been released over the past few weeks) leave little doubt that Hagan is favored - albeit only narrowly.

That leaves us with Mississippi, Georgia, and Minnesota, three highly competitive seats where the situation still looks very confusing. In Mississippi, Research 2000’s survey is the second poll this week to find Roger Wicker opening up a large lead, suggesting that this seat is slipping away from Democrats. Sure, Musgrove could benefit from increased black turnout, but this poll already pegs it at 37%; it’s hard to see it rise far above that. Furthermore, Musgrove’s problems come from his decline among white voters (he only gets 20%).

Democratic hopes of a 60-seat majority would then rest on KY, GA and MN. In Georgia, Buckley is getting a large enough share of the vote that it is becoming difficult to conceive either Chambliss or Martin crossing the 50% threshold. Whatever result comes out of this election will clearly depend on final turnout rates; in few states as much as this one are the LV and RV models finding such disparate results. In Minnesota, meanwhile, the situation is just as confused: Who are Barkley voters? Yesterday, two polls suggested that Barkley was disproportionately drawing from Democrats; today, two new surveys have him pulling equally from both sides. If the former happens, Coleman is in a great position; if the latter, Franken is still very much in the game.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: Dems still far from 60, and is NV in the same tier as CO and VA?

The presidential race remained remarkably stable. If the tracking polls showed McCain gaining slightly yesterday, they have Obama regaining some breathing room today; he is at 50% or above in 6 of the 9 national polls. McCain is once again stuck in the low 40s, with a margin ranging from 41% to 46%. Sure, the New York Times and Fox News national polls came out with differing results, but at least there is no mystery behind the discrepancy: the partisan breakdown has narrowed in the Fox poll.

McCain got one of his most promising polling results in days today as Mason Dixon found him trailing by only 4% in Pennsylvania - the tightest the state has been since a mid-September poll. We should not dismiss this poll, even though surveys taken over the same period show a larger advantage for Obama. Mason Dixon has been consistently releasing results that are better than average for McCain. The Republican nominee led in Virginia when other surveys found him trailing, and trailed only narrowly when other surveys found a large gap; the same was true in Florida and now Pennsylvania. The consistency of these narrower results suggests that it is due to Mason Dixon’s methodology and turnout models, which means that we should not throw these out as outliers: There is a turnout model out there employed by a respected pollster like Mason Dixon that yields results that are better for Republicans, and we won’t know until Tuesday whose assumptions were flawed.

All of this said, there is no discussion to be had that Obama retains an extremely strong position in the electoral college. For one, he remains ahead in the Big Three sates: 3 polls of Pennsylvania show him in the lead (though Mason Dixon has a 4% race), and he is also ahead in Colorado and Virginia. While two polls of Virginia show him with narrower leads than we have seen of late, both surveys were taken over the same period as the CNN and SUSA polls that had him leading by 9% - so these new polls are not picking any new tightening.

To make matters worse for McCain, we might now be getting a third competitive red state where an Obama pick-up appears increasingly likely: Nevada. After posting two double-digit leads earlier this week, Obama leads outside of the margin of error in two new surveys (Suffolk and CNN/Time). This is a very important development: Even if McCain were to save Virginia and Colorado, Obama would become president by winning Nevada alone; if McCain can somehow snatch Pennsylvania, an (not at all improbable) Obama sweep of Virginia, Colorado and Nevada would offset the loss of the Keystone State.

As if this was not enough, Ohio and North Carolina are slowly moving in Obama’s column as the Democrat is accumulating good results in both. Today, he leads in all five polls from these two states, and four of them have him ahead outside of the MoE. Given that a huge number of North Carolina voters have already voted, it is starting to get late for McCain to turn the tide. And while Obama is showing no sign of trembling in blue states (he has huge leads in Wisconsin and Minnesota), McCain is now locked in highly competitive races in a number of staunchly red states - including his home state of Arizona, South Dakota and Montana.

  • Obama leads 52% to 41% in a New York Times/CBS News poll, a very small tightening from Obama’s 13% lead last week. 51% say Obama is ready to be president, and McCain’s favorability has collapsed to 41% (!). So has voters’ estimate of whether Palin is able to deal the job (only 35% say so). Obama leads among men and women, and has a 17% advantage among independents.
  • Obama leads 47% to 44% in a Fox News national poll conducted over the past two days. Obama led by 9% last week, so the race has substantially tightened. The partisan ID has tightened from a 6% gap to a 2% gap (though this does not seem to be an arbitrary imposition like Zogby’s).
  • Tracking polls: Obama gains 2% in Zogby (50% to 43%) and in Rasmussen (51% to 46%). He gains 1% in IBD/TIPP (48% to 44%). The race is stable in Washington Post/ABC (52% to 44%), Gallup (51% to 44%, though Obama gains 2% in the LVT model, 50% to 45%). Obama loses 1% in Hotline (48% to 42%) and in Research 2000 (50% to 45%). Obama’s leads are thus: 4%, 5%, 5%, 6%, 7%, 7%, 8%.
  • Pennsylvania: Obama leads 47% to 43% in a Mason Dixon poll conducted Sunday and Monday. Obama leads 54% to 41% in Morning Call’s tracking, the highest percentage Obama has ever received in this poll. Obama leads 55% to 43% in a CNN/Time poll conducted Thursday through Tuesday (Obama leads by 15% among registered voters!).
  • Colorado: Obama leads 51% to 45% in a Marist poll (52% to 43% among registered voters) conducted Sunday and Monday; his lead comes entirely among the 44% of registered voters who say they have already voted. Obama leads by 23% among independents and has strongest party loyalty (leading me to question why he is only ahead by 6%). Obama leads 48% to 44% in a National Journal poll of registered voters with a small sample and a large MoE conducted Thursday through Monday; Obama leads by 22% among independents.
  • Virginia: Obama leads 51% to 47% in a Marist poll (by 6% among registered voters) conducted Sunday and Monday; McCain takes a 12% lead among independents. Obama leads 48% to 44% in a National Journal poll of registered voters with a small sample and a large MoE conducted Thursday through Monday. Both polls were taken over the same period as SUSA, Rasmussen and CNN poll showing larger Obama leads.
  • Nevada: Obama leads 50% to 45% in a RGJ/Research 2000 poll (he led by 7% earlier in October); McCain leads by 3% in crucial Washoe County, though the RGJ points out that (unreleased) private polls for both parties have Obama leading that county. Obama leads 52% to 45% in a CNN/Time poll conducted Thursday through Tuesday, an improvement over his 5% lead last week (he leads by 11% among registered voters!).
  • Ohio: Obama leads 48% to 41% in a National Journal poll of registered voters with a small sample and a large MoE conducted Thursday through Monday; Obama’s lead is outside of the MoE. Obama leads 51% to 47% in a CNN/Time poll conducted Thursday through Tuesday (Obama leads by 10% among registered voters!).
  • Florida: Obama leads 45% to 44% in a National Journal poll of registered voters with a small sample and a large MoE conducted Thursday through Monday.
  • North Carolina: Obama leads 50% to 48% in a Rasmussen poll taken yesterday (McCain led by 2% on Sunday). Obama leads 47% to 43% in a National Journal poll of registered voters with a small sample and a large MoE conducted Thursday through Monday. Obama leads 52% to 46% in a CNN/Time poll conducted Thursday through Tuesday (Obama led by 4% last week, he is ahead by 3% among registered voters).
  • Indiana: McCain leads 49% to 46% in a Rasmussen poll taken yesterday (he led by 7% three weeks ago). Obama leads 46% to 45% in a Selzer & Co poll conducted Sunday through Tuesday; he is ahead 2:1 among early voters and gets “only” 82% of African-Americans (remember Tuesday’s polling memo released by the McCain campaign?). The candidates are tied at 47% in a Research 2000 poll taken from Friday through Tuesday.
  • Wisconsin: Obama takes a giant 55% to 39% lead in a SUSA poll taken Tuesday and Wednesday, up from 8%. Obama leads by 28% among early voters.
  • Iowa: Obama leads 55% to 40% in a SUSA poll taken Tuesday and Wednesday.
  • South Dakota: McCain only leads 45% to 40% in an internal poll for Democratic Senator Johnson’s campaign.
  • Montana: McCain leads 50% to 46% in a Rasmussen poll. He led by four weeks ago.
  • Safe(r) states: McCain leads 61% to 36% in a SUSA poll of Alabama. McCain leads 58% to 37% in a SUSA poll of Kansas. Obama leads 56% to 39% in a SUSA poll of Massachusetts. Obama leads 55% to 33% in a Field poll of California. Obama leads 54% to 38% in a Research 2000 poll of New Jersey. McCain leads 53% to 42% in a NBC News poll and 52% to 44% in a SUSA poll of South Carolina (but only by 6% among registered voters). McCain leads 55% to 43% in a Rasmussen poll of Kentucky.

Meanwhile, in down the ballot polls:

  • Louisiana: Two polls have differing results. An internal poll for the Kennedy campaign has Mary Landrieu up 45% to 44%, while a Loyola University poll has Landrieu ahead 49% to 34%; the latter poll does not seem very reliable, however, as it only shows McCain leading by 3% and implying an oversampling of Democrats.
  • Mitch McConnell leads 51% to 44% in a Rasmussen poll of Kentucky’s Senate race. (McConnell led by the same margin last month.) A Lunsford internal has McConnell leading 47% to 45%, however.
  • Norm Coleman leads 42% to 36% in a Mason Dixon poll of Minnesota. Barkley is now at 12%, and he is hurting Franken: He draws 17% of Democrats and only 4% of Republicans - a hugely consequential disparity.
  • Safer seats: Tom Udall leads 56% to 41% in a Rasmussen poll of New Mexico. GOP Senator Pat Roberts leads 60% to 33% in a new SUSA poll of Kansas. Democratic Senator Lautenberg leads 56% to 39% in a Research 2000 poll of New Jersey. Sen. Cornyn leads 45% to 36% in a University of Texas poll, with 5% going to Libertarian candidate Adams-Schick. GOP candidate Jim Risch leads 45% to 33% in a Harstad poll of Idaho.
  • In MO-06, perhaps the most disappointing House race for Democrats, GOP Rep. Graves leads 54% to 36% in a SUSA poll. He led by 11% last month.
  • In KY-02, GOP candidate Brett Guthrie leads 53% to 43% in a new SUSA poll. Guthrie led by 9% last month but trailed over the summer.
  • In OR-05, Democratic candidate Kurt Schrader leads 55% to 33% in a SUSA poll.
  • In NY-26, Republican candidate Chris Lee has a large 48% to 34% lead against Alice Kryzan in a SUSA poll. He led by 11% last month.
  • In ID-01, Democratic challenger leads 48% to 41% in a Harstad poll, though the poll has a large MoE of 6%.
  • In PA-12, Rep. Murtha only leads 46% to 44% in a GOP poll conducted by Dane & Associates.
  • In Massachusetts’s question 1 to repeal the state income tax, the “no” is far ahead, 64% to 29% in a SUSA poll.

Democrats have their share of very good news in these wave of surveys - especially the two North Carolina polls showing a Hagan lead and the NV-02 survey confirming that Rep. Heller is in real danger - Republicans got uncommly positive numbers over the past 24 hours. In the Senate, Republicans appear to be solidifying their hold on the four Senate seats that are not yet leaning Democratic - KY, MN, MS and also GA because a runoff should help Chambliss. McConnell has not slipped further after his race fell into a competitive race in early October, and Coleman has improved his situation over the past three weeks.

Minnesota should be particularly worrisome to Democrats because Franken’s slippage is due to the fact that Barkley is starting to draw disproportionately from Franken’s base. If that is confirmed by other polls, it is hard to see Franken pull this off. This is a reminder that, however much progress Democrats have made over the past few weeks, the path to 60 still requires picking-up two out of these 4 seats - and that remains a tall order.

The latest House polls should also be a reminder that Democrats will certainly not win everything on Tuesday, and that a fair number of Republicans appear to be making progress in this hostile environment. The latest poll of MO-06 has to be crushing to Democrats as former Kansas City Mayor Barnes was once one of their top recruits. And while the DCCC is still investing in NY-26, the polls have not been very promising ever since Kryzan won the Democratic nomination.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

As Obama outspends him in battlegrounds, McCain faces electoral map dilemmas

Nielsen’s handy tracker of the number of ads Obama and McCain have been airing every day over the past month gives us a better idea of where the candidates are investing. There are two noticeable trends across these states. First, McCain continues to be significantly outspent in most of these battleground states (especially in Florida).

Second, Obama has slightly decreased the volume of ads compared to the first two weeks of October. This suggests that the Illinois Senator saturated the airwaves over that period (which is confirmed by his campaign filings that indicated that he spent more than $100 million in that period), which helps explain that he inched ahead in many of these battleground states.

In Missouri, not much has changed throughout October, though Obama looks like he has had to decrease the number of his ads a bit. In Georgia, it looked like Obama was back in the state as of mid-October but neither candidate is now investing significant amounts. In Virginia, Obama continues to dominate McCain on the airwaves - but he is airing less spots than he once was.

In Pennsylvania, both campaigns are investing less than they were the first two weeks of October - remarkably so given how crucial Pennsylvania has become to McCain’s electoral hopes. The same is true in Ohio: the spending disparity is remarkable, but so is the drop in number of aired ads (especially on the part of the Obama campaign):

Even more dramatic than Ohio’s financial disparity is Florida’s. McCain is running more ads than he used to while Obama is airing slightly less than earlier in October, but just a glance at this graph illustrates how much Obama has dominated the state’s airwaves and how he has manged to take a lead in most recent Florida polls:

In Colorado, meanwhile, Nielsen’s tracking confirms last week’s reports that the McCain campaign has dramatically scaled back its expenditures in a state that is a must-win for the Republican unless he can somehow pick-up Pennsylvania. McCain has been largely absent from the state’s airwaves for days:

So with the campaign now entering its last days, the electoral map is getting clearer: The McCain campaign is truly scaling back its efforts in Colorado… while the RNC is being forced to pay attention attention to staunchly red states like West Virginia and Montana.

Take this as further evidence that the GOP is in such a precarious position that they can no longer finda  coherent strategy to reach 270 electoral votes and are left praying for an electoral college miracle.

Last week, Republicans realized that they could no longer afford playing in all the competitive states - nor in all the states they need to win to get McCain an electoral college majority. The GOP concluded that it needed to pick a few states in which to make a stand, and then hope that a shift of momentum put McCain in a position to capture states like Pennsylvania that right now appear out of reach.

This makes it somewhat puzzling that the GOP has chosen to make such an effort this late in the game in states like North Carolina, Indiana and Missouri - states Obama does not need to win the presidency.

McCain needs to prevail in at least one state in which Obama now enjoys a sizable lead (PA, CO and VA), and he will not be in a position to score such an upset unless he can first change the national mood (increased spending in Colorado could help him rise one or two points, not close a high single-digit gap). In other words, a necessary but not sufficient condition for a McCain victory in states he needs to wins is a tightening in national polls.

But if a meaningful change in the national environment were to occur, McCain has to assume that he would regain his footing in conservative-leaning states like North Carolina, Indiana and Missouri - meaning that the same phenomenon he desperately needs to achieve victory in Pennsylvania, Virginia or Colorado should help him protect his endangered base states.

In those conditions, was it a good decision for the McCain campaign to scale back expenditures in Colorado and use that money to shore up defenses elsewhere? Given that Colorado’s 9 electoral votes are so crucial to McCain’s survivals it seems incredible for Republicans to bank that a comeback would allow them to suddenly put Pennsylvania into play without similarly tightening Colorado, Wisconsin or Minnesota and without allowing McCain to gain an edge in staunchly red states.

Of course, that McCain is facing such painful dilemmas at all is a reflection of the Obama campaign’s brilliant map expansion strategy. Reading current campaign coverage, one might get the impression that all these states just suddenly appeared on our radar screen after the economic crisis struck; in fact, we had been talking about Indiana and North Carolina for months, as the Obama campaign has aired ads in them throughout the summer - so much so that we had been discussing Obama’s strategy at length ever since the wrapped up the Democratic nomination. Here is why I wrote, for instance, on July 21st:

It is probable, then, that Obama’s red state strategy will turn into a win-win scenario: Either they organize and advertise without a response and have a chance at pulling upsets or they force the GOP to defend states that should be on no one’s radar screen.

In fact, Obama’s red state strategy worked even better than that, and Democrats got the better of both worlds: They forced the GOP to play defense and Obama still has an excellent shot to pull off these upsets. And the reason for this is that Republicans woke up too late: Had they invested significant amounts in Indiana and North Carolina over the summer, they might have appealed to the electorate’s conservative instincts and crushed Obama’s growth before it was too late. This will no doubt be remembered as one of the main strategic mistakes of the McCain campaign.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: Trackings tighten (a bit), but Obama dominates in VA, CO, PA, OH, FL and NV; Wicker opens wide lead

We start, as will now be customary, with the three states that we should be watching over this closing week: Colorado, Virginia and Pennsylvania. New polls were released today in each and they find Obama in command: He extends his lead by 3% in the latest Insider Advantage poll of Colorado, leads by 9% in Virginia and has a sizable edge in three Pennsylvania surveys (7% to 12%). That said, both Insider Advantage and Rasmussen suggest that there might be some tightening in the Keystone State, and Obama is no longer enjoying consistent double-digit leads.

It is a testament to just how huge a lead he had seized that he remains so firmly in command of Pennsylvania despite shedding nearly half of his lead in Rasmussen’s survey. And it is also a testament to Obama’s remarkably strong electoral map that he has so many other options even if McCain somehow manages to pull off one of the three states listed above.

If Obama were to lose Pennsylvania, for instance, Nevada would suffice to compensate - and two new polls out today show Obama leading outside of the margin of error and by as much as 10%. Keep in mind that the demographics of Pennsylvania, Virginia, Colorado and Nevada are very similar, so a comeback in the former wouldn’t mean that McCain is coming back in the three latter ones. McCain trails outside of the MoE in two new polls of Ohio (4% and 9%) and two new polls of Florida (5% and 7%). McCain still has a lot of work to do in all of these states.

As has been the case over the past few days, the tightest contests are taking place in states that Obama does not need: Indiana, North Carolina, Montana, Georgia and… Arizona are all within the margin of error in new polls. Losing any of these would be a catastrophe for the GOP.

McCain supporters can at least take comfort in the composite of the tracking polls, as McCain continues to close the gap after already tightening the race somewhat yesterday. But he continues to trail, and a Pew national poll taken over the same period finds disastrous numbers for McCain (I don’t believe McCain had ever trailed by 16% in a poll before). On to the full roundup of the day’s polls:

  • Obama leads 53% to 38% in a national Pew poll conducted Thursday through Monday; the margin is 16% with registered voters. 74% of Obama’s supporters describe themselves as “strong” supporters, versus 56% of McCain’s. Obama leads among men, women, every age group, independents and by 19% among early voters.
  • Obama leads 50% to 45% in an ARG national poll thanks to 83% of Democrats and a 12% lead among independents.
  • McCain makes some progress in the latest tracking polls: He gains 3% in Gallup (51-44, and only 49-47 in the LVT model), 1% in Research 2000 (50-43), 1% in Zogby (49-45). The race is stable in Hotline (50-42), Washington Post/ABC (52-45) and Rasmussen (51-46). Obama gains 1% in IBD/TIPP (48-44). That means that Obama’s leads are: 4%, 4%, 5%, 7%, 7%, 7%, 8%.
  • Colorado: Obama leads 53% to 45% in a new Insider Advantage poll, based on his staggering 81% among Hispanics. Obama led by 5% last week. The poll was conducted on Sunday.
  • Pennsylvania: Obama leads 51% to 42% in an Insider Advantage poll of Pennsylvania; a separate IA poll of suburban Bucks County finds Obama leading by 3% (the same as Kerry), a 3% decline since a poll two weeks ago. This poll was conducted on Sunday. Obama leads 53% to 46% in a Rasmussen poll; that’s a drop from Obama’s 13% margin three weeks ago. No movement in the Morning Call tracking poll, however, where Obama leads 53% to 41%.
  • Virginia: Obama leads 48% to 39% in a Roanoke College poll. The poll was conducted over eight days, however, from the 19th through yesterday.
  • Ohio: Obama leads 49% to 40% in a new LAT/Bloomberg poll conducted Saturday through yesterday. (A fascinating internal: Obama wins white, working class voters 52% to 38%). Obama leads 49% to 45% in a SUSA poll conducted on Sunday and Monday. Obama led by 5% two weeks ago. He leads by 17% among the 22% of respondents who say they have already voted.
  • Nevada: Obama leads 50% to 40% in a Suffolk poll conducted from the 23rd through the 27th, with 2% for Barr and 1% each for McKinney and Nader. Obama leads 50% to 46% in a Rasmussen poll in which he led by 5% two weeks ago.
  • North Carolina: The candidates are tied at 47% in a week-end Mason Dixon/NBC poll. In a PPP poll of the 8th district, Obama leads by 6% which is a 14% swing since 2004, about what Obama needs statewide to win the state.
  • Indiana: Three polls in Indiana show a highly competitive race. Obama leads 48% to 47% in a Research 2000 poll (the candidates were tied three weeks ago.) McCain leads 47% to 45% in a Howey/Gauge poll. In a separate Research 2000 poll of IN-03, McCain leads 53% to 38% - which is great news for Obama since Bush won the district 68% to 31% (that’s a 22% swing towards Obama, essentially what he needs statewide to carry the state).
  • Montana: McCain leads 48% to 44% in a week-end Mason Dixon/NBC poll (I am not sure whether Ron Paul’s name was included).

Meanwhile, in down the ballot surveys:

  • Roger Wicker jumps to a big 54% to 43% lead in a Rasmussen poll of Mississippi’s Senate race. He only led by 2% in September.
  • Saxby Chambliss leads 46% to 44,5% in an Insider Advantage poll of Georgia’s Senate race, with 2% going to other (it looks like Buckley’s name was not included).
  • Jeff Merkley leads 45% to 40% in a Hibbits poll of Oregon’s Senate race conducted from the 22nd to the 25th. No mention of early voting, unfortunately.
  • Bev Perdue leads McCrory 47% to 44% in a PPP poll of North Carolina’s gubernatorial race.
  • In IN-03, GOP Rep. Souder leads 45% to 40% in a Research 2000 poll, with 4% going to Libertarian candidate Bill Larsen. In a Howey Gauge poll of the district, however, it is Democratic challenger Montagano who leads 44% to 41% (this latter poll has a large 6% MoE).
  • In NC-08, Larry Kissell leads GOP Rep. Hayes 51% to 46% in a PPP poll.
  • In OH-15, Democratic candidate Mary Jo Kilroy leads 47% to 41% in a SUSA poll, with 6% going to conservative independent candidate Don Eckart. 37% of respondents say they have already voted, and Kilroy leads by 16%.
  • In GA-08, Democratic Rep. Marshall leads 49% to 45% in a SUSA poll. Marshall immediately released an internal poll showing him leading 48% to 31%.
  • In KS-03, Democratic Rep. Moore leads 53% to 42% in a SUSA poll.

The most important of the day’s congressional poll undoubtedly comes from Mississippi, where Republican Senator Roger Wicker jumps to a commanding lead - suggesting that Democrats might not be as close to a Senate sweep after all (Mississippi’s Senate race is currently ranked 9th in my Senate rankings). The Insider Advantage poll from Georgia, meanwhile, is further evidence that we might not get a resolution on November 4th, as both candidate are far from the 50% mark - especially since the Libertarian candidate was not even included as an option in this survey.

At the House level, Democratic taek-over opportunities in NC-08 and OH-15 (both rated lean Democratic in my latest ratings) continue to look good for Democratic, and the IN-03 numbers are outstanding: this is a massively Republican district that voted for Bush by 37% in 2004! It was on no one’s radar screen as of the end of September, and has now become a highly vulnerable district. If Rep. Souder falls, IN-03 will be remembered as one of the great upsets of the 2008 cycle.

SUSA’s GA-08 poll, however, is a reminder that there are a number of Democratic seats at risk as well. Marshall barely survived the 2006 cycle (in fact, he looked gone for much of the cycle), and it looks like this race might keep us late yet again.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: Obama dominates VA, gains edge in OH, Merkley in strong position, Lampson drowns

In my latest presidential ratings this morning, I identified the three states to watch in the election’s final stretch: Virginia, Pennsylvania and Colorado. Eight days from the election, Obama holds strong in those crucial states: A grand total of five new Virginia polls were released today, finding a consistent Obama advantage. Only Rasmussen found Obama holding a lead smaller than 7%, the four others having Obama’s lead go as high as 11%. Only one poll each from Colorado and Pennsylvania were released: Obama was leading comfortably in Pennsylvania, though his margin in Colorado is smaller than Democrats are hoping to see (4%).

That said, there is some movement in McCain’s favor in the tracking polls, and I feel compelled to point that out because of what I said in yesterday’s poll watch, when remarking on McCain’s inability to break out of the low 40s: “The day McCain manages to inch above 45%, we can think about whether the race is tightening.” Today, McCain gets to 46% in one national poll and is at 45% in three more. But Obama remains in a dominant position, as he is at 50% or above in six of the seven tracking polls; only IBD/TIPP has him at a weaker position, and that tracking’s internals are rather strange (Obama enjoys stronger party loyalty and leads among independents but only leads by 3%).

In other states, Obama’s strong position is confirmed: New polls in Ohio and Florida find Obama holding an advantage, especially in the former state. In fact, Rasmussen’s polls from these two states should put to rest talk of a tightening since Obama gains 5% and 6% in the two surveys over those released last Monday.

McCain’s two best trendlines today come from PPP’s North Carolina survey (that had Obama up 7% last week, up 1% today) and SUSA and Rasmussen’s Missouri polls (Obama led by 8% and 5%, he now ties and is ahead by 1%), but the size of Obama’s lead in all three of these surveys was not confirmed by other polls, making this week’s surveys expected regressions to the mean. In fact, it is great for Obama is that the true toss-ups are not the states he needs to win but rather places like North Carolina or Missouri: six new polls in those two states find tight races. Even Arizona polls are now showing a competitive race!

  • Obama remains ahead in the day’s tracking polls, though there is some movement: Obama loses a significant three points in Research 2000 (50% to 42%, with a 5% lead in the Sunday sample) and Rasmussen (51% to 46%); he also loses 1% in IBD/TIPP (47% to 44%). Three trackings are stable: Washington Post/ABC (52% to 45%), Hotline (50% to 42%) and Zogby (50% to 45%). Obama inches up one point in Gallup (53% to 43%, the same margin as RVs and double his lead in the LVT model). That means that Obama’s leads are: 3%, 5%, 5%, 7%, 8%, 8% and 10%.
  • Virginia: Five new polls have Obama in the lead by margins ranging from 4% to 11%. The two most recent are Rasmussen and SUSA: Obama leads 52% to 43% in a SUSA poll, including a huge lead among early voters. His lead in Rasmussen is smaller: 51% to 47%, down from a 10% lead last week.
  • Obama leads 52% to 45% in a Zogby poll conducted over the week-end. Obama leads 52% to 44% in a Washington Post poll. (He led by 3% last month. This time, 50% of respondents say they have been personally contacted by the Obama campaign. The enthusiasm gap is huge, with 70% of Obama supporters describing themselves as enthusiastic.) Obama leads 51% to 40% in a VCU poll.
  • Ohio: Obama leads 50% to 45% in a Zogby poll, in which he has a 16% edge among independents. Obama leads 49% to 45% in Rasmussen, a 6% swing from last week.
  • Colorado: Obama leads 50% to 46% in Rasmussen, a 1% gain for McCain over last week.
  • Florida: The candidates are tied at 47% in a Zogby poll, though Obama has a strangely large 62-25 lead among independents. Obama leads 49% to 44% in a Suffolk poll of the state (up from 4%). Obama leads 51% to 47% in a Rasmussen poll, a 5% swing in his favor since last week.
  • Pennsylvania: Obama leads 50% to 41% in a Temple University poll. The survey was conducted over an entire week (from the 20th to the 26th), however.
  • Nevada: Obama leads 48% to 44% in a Zogby poll, barely outside of the margin of error.
  • North Carolina: Obama leads 50% to 46% in a Zogby poll. Obama leads 49% to 48% in a PPP poll, though he led by 7% last week. There are far less undecided voters this week. However, among early voters (about a third of the sample), Obama leads 63% to 36% (”looking at it another way, 49% of blacks in our survey said they had already voted. Only 29% of white voters said the same”). McCain leads 49% to 48% in Rasmussen, a 1% gain for Obama since late last week.
  • Iowa: Obama leads 52% to 42% in a Marist poll, the same margin he enjoyed last month.
  • New Hampshire: Obama leads 50% to 45% in a Marist poll, a one point decline since September.
  • Indiana: McCain leads 50% to 44% in a Zogby poll.
  • West Virginia: McCain leads 50% to 40% in a Zogby poll, thanks in part to 28% of Democratic voters.
  • Oregon: Obama leads 57% to 38% in a SUSA poll. Half of the electorate has already voted (remember that all of Oregon votes by mail), and Obama leads by 28% among those voters.
  • Arizona: The third poll in two days finds McCain in trouble in his home state. He leads 51% to 46% in a Rasmussen poll.

Meanwhile, in down-the-ballot polls:

  • Jeff Merkley leads 49% to 42% in a SUSA poll of Oregon’s Senate race. Half of the electorate has already voted, and Merkley leads by 10% among those voters.
  • Kay Hagan leads 48% to 45% in a PPP poll of North Carolina’s Senate race. She led by 8% last week.
  • Jay Nixon leads 55% to 38% in a SUSA poll of Missouri’s gubernatorial race.
  • In TX-22, Republican challenger Pete Olson leads Democratic Rep. Nick Lampson 53% to 36% in a new Zogby poll.
  • In FL-25, GOP Rep. Diaz-Balart leads 45% to 42% in a Research 2000 poll. Among early voters, Garcia leads 52% to 46%.
  • In SC-01, GOP Rep. Harry Brown leads 50% to 45% in a new SUSA poll.
  • In TX-07, GOP Rep. Culberson leads 47% to 40% in a Zogby poll.

Jeff Merkley’s numbers are the most important of this group, as this is the Oregon Democrat’s largest lead yet against Gordon Smith, who continues to be stuck in the low 40s. More importantly, SUSA’s polls confirms what was one of the main reasons I changed the ratings of the race to lean Democratic two days ago: Because of Oregon’s mail-in voting system, Election Day is happening right now in Oregon, giving Smith no time to catch up. While remaining ahead, Kay Hagan does not look to be as favored as her Oregon colleague.

A number of fascinating indepenent House polls were released as well, the most noteworthy of which is Zogby’s survey from TX-22: This was long seen as an extremely highly endangered Democatic seat, but the DCCC’s decision to dump hundreds of thousands of dollars suggested they saw Lampson with a chance at surviving. Zogby’s poll indicates that the conventional wisdom was right and that Lampson is an underdog in what is one of the most Republican seats represented by a Democrat. That said, the DCCC has just debuted a very hard-hitting ad on Pete Olsen, accusing him of voter fraud. We will see whether that moves any numbers.

As for CA-04, SC-01 and TX-07, all three are heavily Republican districts and for independent polls to find the Republican under 50% in each and the Democrat leading in one is obviously major news, and confirms that Democrats can expect to prevail in a few heavily conservative seats on November 4th.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: Opposite trends in OH and FL, Bachmann in trouble, GA Senate heading to runoff

Today’s polling roundup is certainly not as favorable to Barack Obama as yesterday’s, but there is still no sign that the tide is turning - with only 10 days of campaigning left before Election Day. The national polls, for one, remain where they have been for most of the past two weeks: Obama is above 50% in six of the seven tracking polls (a remarkable showing that confirms McCain has to do more than appeal to the undecided) while McCain is, once again, stuck in the low 40s (from 41% to 45%).

The one state in which McCain has not only stopped the bleeding but appears to be making up ground, however, is Florida. Over the past week, new surveys from Politico, Mason Dixon, Quinnipiac, PPP, Rasmussen, SUSA and Research 2000 all showed some movement (between 10% and 1%) towards the Republican nominee. That said, Obama remains ahead in a number of these surveys, and the best McCain can muster remains within the margin of error. The day’s second good news for McCain is a Rasmussen survey from North Carolina in which he is narrowly in the lead; this survey breaks a stunning series of 16 North Carolina polls without a McCain lead.

The overall picture that comes out of the day’s polling has little to suggest that McCain’s position in the electoral college is any less precarious than it was yesterday. That grabbing a 2% lead in North Carolina amounts to good news for McCain tell us all we need to know about the current dynamics and where the electoral battle is being waged. Besides North Carolina, the tightest states in this polling roundup are Indiana (where two polls find mirroring results) and… Georgia, where Obama grabs his first lead ever!

All three of these states were won by Bush by double-digits in 2004 - and they are the ones that look highly competitive today! The states that were expected to be tight continue to tilt towards Obama - and that is starting to include Ohio. Yes, McCain posts a 3% lead in a Strategic Vision poll, but Insider Advantage gives Obama a 10% lead which is very significant: No poll taken since the general election started had found Obama up by double-digits… until yesterday. Insider Advantage’s poll is the third poll in two days to have Obama leading by such a margin. On to the full polling roundup:

  • The tracking polls once again seem to converge towards the 7% mark, a margin that appears to be the epicenter of the race. Obama gains 3% in IBD/TIPP (46% to 42%), 2% in Research 2000 (52% to 40%) and Hotline (50% to 43%), 1% in Gallup (51% to 44%). Rasmussen remains stable, 52% to 45%. He loses 2% in Zogby (51% to 41%) and in Washington Post/ABC (53% to 44%). Thus, Obama’s leads today are: 4%, 7%, 7%, 7%, 9%, 10%, 12%
  • Ohio: Contrasting results and a wide gap in two polls: Obama leads by 10% in an Insider Advantage poll, his third double-digit lead in two days (there have been no others since he wrapped up the nomination), and he led by 5% in IA two weeks ago. However he trails 48% to 45% in a Strategic Vision poll of Ohio (he led by 2% two weeks ago).
  • North Carolina: McCain captures his first lead in a Rasmussen poll since September 18th, 50% to 48%. The poll was conducted last night, and it is a five point shift towards the Republican over a poll conducted on Saturday. This poll breaks a stunning series of 16 NC polls in which McCain had not led a single time.
  • Indiana: Contrasting results from two good pollsters: Obama leads 49% to 45% in a SUSA poll. McCain led by 3% three weeks ago. McCain leads 48% to 43% in a Mason Dixon poll.
  • New Hampshire: Obama leads 50% to 46% in a Rasmussen poll taken yesterday. He led by 10% three weeks ago, however, so there is some tightening.
  • Georgia: Obama leads 48% to 47% in a stunning Insider Advantage poll (this is the fourth IA poll in a row to find Obama gaining since McCain’s 18% lead in early September). McCain leads 50% to 44% in Strategic Vision.
  • Iowa: Obama leads 52% to 44% in a Rasmussen poll, maintaining his 8% lead from late September.
  • Michigan: Obama leads 54% to 40% in an EPIC-MRA poll (up from 10%).
  • Winthrop/ETV released three Southern polls today, all taken over an inexplicably long period of time: September 29th through October 19th! This means that these polls have very little value, but here they are nonetheless: Obama leads by 1% in Virginia and North Carolina and McCain leads by 20% in South Carolina.

Meanwhile, in down-the-ballot polls:

  • Georgia Senate race: Three polls show a tight race, all with GOP Sen. Chambliss leading within the MoE. He is ahead 44% to 42% in Insider Advantage (there was a 45% tie two weeks ago). Chambliss is also ahead 46% to 44% in a Strategic Vision poll, with 5% for Libertarian candidate Buckley.
  • North Carolina gubernatorial race: Pat McCrory leads 51% to 47% in a Rasmussen poll. He led by the same margin two weeks ago.
  • In MN-06, Elwin Tinklenberg leads GOP Rep. Michelle Bachmann 47% to 44% in a SUSA poll. He also leads 45% to 43% in a University of Minnesota poll, in which 40% of respondents say Bachmann’s rants makes them less likely to vote for her.
  • In IL-10, Dan Seals leads 49% to 44% against GOP Rep. Kirk in a Research 2000 poll. He trailed by 6% two weeks ago.
  • In KY-03, Rep. Yarmuth (D) leads 57% to 41% in a SUSA poll.
  • In FL-08, Alan Grayson leads 52% to 41% against GOP Rep. Keller in a DCCC internal. The Keller campaign responded by releasing an internal poll of their own taken over the same period and showing the incumbent ahead 47% to 43%.

The Georgia Senate race is in a category of its own at this point. Not only is it highly competitive (and the DSCC has already poured in more than $1 million), but the candidacy of Libertarian candidate Buckley could guarantee that the race goes in the runoff because of Georgia’s two-round of voting system. We can discuss another time who a runoff would help (and in my opinion it would clearly boost Chambliss), but for now an important metric is to look at how distant those candidates are from 50%.

In House races, meanwhile, the 5 independent polls all bring good news for Democrats - particularly the two from MN-06 that confirm that Bachmann’s comments have endangered her hold on the district. The polls were taken before the DCCC and Tinklenberg’s heavily funded ads had any chance to make an impact, so things could get worse for Bachmann.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

McCain takes us back to experience, warns of all-blue DC and remains obsessed with Iowa

With its back against the wall, the McCain campaign is still not invoking Wright - but it is leaving behind all nuance in its latest ad. The stop uses Joe Biden’s recent comments on a coming international crisis to bring the conversation back to national security and experience:

Whenever a campaign uses footage of Chavez, Ahmadinejad, of men marching with rifle and of cataclysmic international circumstances, there is great risk that it could fall in Rudy Giuliani territory and give fodder to critics that charge that Republicans are using fear tactics. But beyond those questions of appropriateness, the biggest problem of McCain’s latest offensive is - and I have said this many times already, but I cannot emphasize this enough - consistency.

It might not be McCain’s fault that national security hasn’t been a dominant issue in the fall campaign. But they are solely responsible for having abandoned the experience argument. On September 6th, I wrote a puzzled post about McCain’s “revolutionary departure from what we expected the GOP’s general election argument to be.” The campaign’s primary argument no longer concerned readiness to lead - the theme of McCain’s summer attacks. Forget experience, forget familiarity, forget patriotism, the GOP started to say: Even if voters just think about who represents true change, they should settle on McCain.

Seven weeks later, McCain’s has made no progress in his efforts to claim the change mantle, and the main weapon he had to voice that argument (Sarah Palin) is now far more of a liability than an asset with swing voters. The change argument has failed, the McCain campaign is trailing by double-digits in a number of polls - and now we go back to the experience argument?

What is particularly tragic for Republicans is that McCain’s attacks on Obama’s readiness were resonating during the summer: the race tightened considerably between the launch of the celebrity ads and the Democratic convention, and Hillary voters were drifting away from Obama. But by picking Sarah Palin and abandoning the experience argument, the GOP gave Obama nearly two months to reassure voters and make himself familiar to them. He was steady at the debates and throughout the financial meltdown. As a result, recent national polls show that the public now trusts Obama more than McCain to handle a major crisis.

Not only did McCain’s abandoning the experience argument prevent him from landing solid blows for weeks, it also let Obama’s readiness go unchallenged for weeks, making it far more difficult for Republicans to suddenly pick up where they left off at the end of August.

McCain’s second closing argument is a warning that an Obama election would mean undivided Democratic government. “The answer to a slowing economic is not higher taxes,” said McCain today. “But that’s exactly what’s going to happen when the Democrats have total control of Washington. We can’t let that happen.” McCain went on to attack Barney Frank, in an obvious attempt to link Obama to congressional Democrats and play on the GOP’s new talking points of running against what they call the Obama-Pelosi-Reid “triumvirate.”

There are a two problems with this strategy, however. First, we have seen over the past few months that voters are currently looking at Washington as a Republican stronghold and are not taking into account the Democratic majorities in Congress. There is no evidence that 2008 will be an anti-incumbent year targeting Democratic and Republican representatives alike; there is every evidence that it will be an anti-Republican year, making McCain’s argument warning against the perils of giving more power to congressional Democrats harder for voters to accept.

Second, voters think of the presidential election as the primary one, and it is not likely that many will decide on their presidential choice based on who is controlling Congress. The process usually works the other way around! And congressional Republicans fully intend to take advantage of that, as some candidates are now starting to run on the assumption of an Obama presidency to warn voters to not give him too large congressional powers. As I noted yesterday, a new NRSC ad in NC tells voters that a Hagan victory would mean Democratic control of all levels of government. Even Democratic-leaning papers are being swayed by this argument; the Oregonian, for instance, endorsed Gordon Smith because of its concerns that a 60-seat Democratic majority would lead to excesses.

It won’t be easy for McCain to make an argument against undivided government if congressional Republicans continue voicing their own version of that warning.

But the most incredible of McCain’s strategic decisions has to be his obsession with Iowa. Sarah Palin will hold two of her three rallies tomorrow in Iowa, while McCain will be campaigning in New Mexico, another state that is a likely Obama pick-up. Then, McCain will be holding an event in Iowa himself on Sunday before traveling to Ohio. I understand that Iowa is in between New Mexico and Ohio, but so is Missouri, a far more competitive state in all recent polls.

It is one thing for the McCain campaign to pin a lot of its hopes on Pennsylvania despite most polls suggesting that Obama has a double-digit lead; after all, McCain needs to make a stand somewhere, Pennsylvania doesn’t have early voting and it is unclear whether McCain has any hope of winning without picking it up.But McCain’s commitment to regularly traveling to the Hawkeye State is incomprehensible.



If you like the website...

... Support Campaign Diaries


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2::filter_post_comments() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 166

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Recent Posts


    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • All good things must come to an end

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • What remains on the table

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Confusion in Connecticut (Updated)

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Results thread, part 2: Dems suffer staggering losses in House and legislatives races, limit damage in statewide races

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Election Night results thread: Rep. Boucher’s fall first surprise of the night

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Election night cheat sheet

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Final ratings: Democrats brace for historic losses

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • What to watch for down-ballot

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Archives