Personally I’ve given up using the Twitter plugin due to the potential for lengthy page load delays when Twitter has problems. Instead I am polling the API with a hand-rolled cURL script and writing the output to a static HTML page that I can then include() in my templates.
require_once('curl.class.php');
$curl = new Curl();
$twitter = $curl->fetch_xml('http://twitter.com/statuses/user_timeline/matthewpennell.xml?count=1');
if ($twitter)
{
$output = '<div id="twitter">/i/twitterific.png<h2>Twittering</h2><blockquote><p>';<br />
$in = array(<br />
'/^(is\s)?[a-z]/',<br />
'/(https?:\/\/[A-Za-z0-9\.\-\_\/\?\=]+)/',<br />
'/@(\w+)/'<br />
);<br />
$out = array(<br />
'<span>$2</span>',<br />
'<a href="http://$1">[link]</a>',<br />
'<a href="http://www.twitter.com/$1">@$1</a>'<br />
);<br />
foreach ($twitter->status as $status)<br />
{<br />
$output .= preg_replace($in, $out, $status->text);<br />
}<br />
$output .= '</p>
</blockquote><p></div>';<br />
# Write the final information to a static HTML file<br />
$fh = fopen('twitter.html', 'w');<br />
fwrite($fh, $output);<br />
fclose($fh);<br />
echo "Twitter import completed successfully.\n\n";<br />
} <br />
else<br />
{<br />
echo "Twitter import failed - could not connect to API\n\n";<br />
}<br />
$curl->close();
It means that even when Twitter is down, you still have some content to display.