Talk:2006 Iditarod

Intro
Please re-arrange the intro so that it doesn't start by saying who won. It should start with the usual information, such as the length of the race, how many participated, etc. &mdash; 0918 BRIAN &bull; 2006-03-16 08:42

Changes
I reworked the beginning of the article so it doesn't immediately say who won. I am not very knowledgable about the race, so somebody else will need to work on the rest. Splamo 17:22, 16 March 2006 (UTC)
 * Hopefully better now. It's a hazard of current event articles that grow organically. :) 68.84.34.154 19:03, 16 March 2006 (UTC)

Dead link
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://www.adn.com/iditarod/race_2006/news/story/7540496p-7451994c.html
 * In 2006 Iditarod on 2011-05-26 02:04:56, 404 Not Found
 * In 2006 Iditarod on 2011-06-13 18:13:18, 404 Not Found

--JeffGBot (talk) 18:13, 13 June 2011 (UTC)

Dead link 2
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-10.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:13:28, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:13, 13 June 2011 (UTC)

Dead link 3
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-09_1.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:13:39, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:13, 13 June 2011 (UTC)

Dead link 4
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-11_2.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:13:48, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:14, 13 June 2011 (UTC)

Dead link 5
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-09_2.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:13:58, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:14, 13 June 2011 (UTC)

Dead link 6
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-12.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:14:09, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:14, 13 June 2011 (UTC)

Dead link 7
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-13.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:14:18, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:14, 13 June 2011 (UTC)

Dead link 8
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-13_1.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:14:28, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:14, 13 June 2011 (UTC)

Dead link 9
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-18.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:14:38, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:14, 13 June 2011 (UTC)

Dead link 10
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-06_1.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:14:58, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:15, 13 June 2011 (UTC)

Dead link 11
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-18_1.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:14:59, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:15, 13 June 2011 (UTC)

Dead link 12
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-06_2.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:15:10, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:15, 13 June 2011 (UTC)

Dead link 13
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-07.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:15:18, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:15, 13 June 2011 (UTC)

Dead link 14
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-08_1.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:15:28, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:15, 13 June 2011 (UTC)

Dead link 15
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-08.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:15:38, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:16, 13 June 2011 (UTC)

Dead link 16
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-09.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:15:48, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:16, 13 June 2011 (UTC)

Dead link 17
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-10_1.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:15:59, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:16, 13 June 2011 (UTC)

Dead link 18
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-10_3.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:16:09, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:16, 13 June 2011 (UTC)

Dead link 19
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-10_2.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:22, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:16:18, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:16, 13 June 2011 (UTC)

Dead link 20
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-10_5.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:22, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:16:28, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:16, 13 June 2011 (UTC)

Dead link 21
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-11_3.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:16:38, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:17, 13 June 2011 (UTC)

Dead link 22
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-11.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:16:49, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:17, 13 June 2011 (UTC)

Dead link 23
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-11_4.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:16:59, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:17, 13 June 2011 (UTC)

Dead link 24
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-12_2.pdf
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:17:08, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:17, 13 June 2011 (UTC)

Dead link 25
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-15.pdf
 * In Jeff King (mushing) on 2011-05-06 20:00:29, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-05-26 02:05:21, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
 * In 2006 Iditarod on 2011-06-13 18:17:18, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 18:17, 13 June 2011 (UTC)

Dead link 26
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://www.hurdal.com
 * In 2005 Iditarod on 2011-05-25 08:00:34, Socket Error: 'getaddrinfo failed'
 * In 2006 Iditarod on 2011-05-26 02:05:12, Socket Error: 'getaddrinfo failed'
 * In 2007 Iditarod on 2011-05-27 15:08:01, Socket Error: 'getaddrinfo failed'
 * In 2006 Iditarod on 2011-06-13 18:17:28, Socket Error: 'getaddrinfo failed'

--JeffGBot (talk) 18:17, 13 June 2011 (UTC)

Dead link 27
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!


 * http://www.gorachaelgo.;;slktrcom
 * In 2006 Iditarod on 2011-05-26 02:05:12, Socket Error: 'getaddrinfo failed'
 * In 2006 Iditarod on 2011-06-13 18:17:45, Socket Error: 'getaddrinfo failed'

--JeffGBot (talk) 18:18, 13 June 2011 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 3 external links on 2006 Iditarod. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20121009144602/http://dsc.discovery.com/news/2009/03/25/iditarod-dog-deaths.html to http://dsc.discovery.com/news/2009/03/25/iditarod-dog-deaths.html
 * Added tag to http://iditaweb-1.gci.net/pdffiles/media/pr2006-03-15.pdf
 * Added archive https://web.archive.org/web/20050307084917/http://shageluk.iasd.schoolaccess.net/ to http://shageluk.iasd.schoolaccess.net/
 * Added archive https://web.archive.org/web/20120418164648/http://www.buserdog.com/buserdog/ to http://www.buserdog.com/buserdog/

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 16:52, 17 June 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on 2006 Iditarod. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20060402193750/http://iditablog.com/ to http://www.iditablog.com/

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 10:20, 18 September 2017 (UTC)