<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Blackberry=Whackberry &#187; Outage</title>
	<atom:link href="http://www.whackberry.com/archives/tag/outage/feed" rel="self" type="application/rss+xml" />
	<link>http://www.whackberry.com</link>
	<description>BlackBerries are Whack....</description>
	<lastBuildDate>Thu, 10 Sep 2009 19:33:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>BlackBerry PIN/Service Book/Activation issues</title>
		<link>http://www.whackberry.com/archives/11</link>
		<comments>http://www.whackberry.com/archives/11#comments</comments>
		<pubDate>Fri, 24 Jul 2009 15:59:30 +0000</pubDate>
		<dc:creator>TCS</dc:creator>
				<category><![CDATA[BES]]></category>
		<category><![CDATA[BlackBerry Devices]]></category>
		<category><![CDATA[BES outage]]></category>
		<category><![CDATA[BlackBerry outage]]></category>
		<category><![CDATA[Outage]]></category>
		<category><![CDATA[Security Issues]]></category>
		<category><![CDATA[unplanned outage]]></category>

		<guid isPermaLink="false">http://www.whackberry.com/?p=11</guid>
		<description><![CDATA[
Incident for BlackBerry PIN to PIN service for subscribers of &#8220;The Americas
Network&#8221;
Impact: BlackBerry subscribers may experience delays in receiving PIN
messages and may receive an &#8220;x&#8221; when sending PIN messages.
Incident Window Start Date and Time: 23 July 2009 14:46:00 (EDT).
Duration: Ongoing
Seems like BlackBerry&#8217;s PIN messaging went down for a short while last night.  This would affect [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><img class="aligncenter size-full wp-image-12" title="BB-outage" src="http://www.whackberry.com/wp-content/uploads/2009/07/BB-outage.jpg" alt="BB-outage" width="263" height="304" /></p>
<blockquote><p>Incident for BlackBerry PIN to PIN service for subscribers of &#8220;The Americas</p>
<p>Network&#8221;</p>
<p>Impact: BlackBerry subscribers may experience delays in receiving PIN</p>
<p>messages and may receive an &#8220;x&#8221; when sending PIN messages.</p>
<p>Incident Window Start Date and Time: 23 July 2009 14:46:00 (EDT).</p>
<p>Duration: Ongoing</p></blockquote>
<p>Seems like BlackBerry&#8217;s PIN messaging went down for a short while last night.  This would affect all those users wishing to send super-secrect messages&#8230;  <span id="more-11"></span>Sorry guys, but it looks like you&#8217;ll have to learn how to use good ol email to communicate.  RIM still seems to be ironing out some kinks with their Network Operations.  Several system wide outages over the past few months could mean nothing or everything depending on how your organization uses their services.  It can be easy to get lured into the ease of deployment, the all-in-one solution, the ease of troubleshooting ect&#8230; But when you throw an outage here, an outage there&#8230; it quickly becomes an IT nightmare.  One unexpected outage can easily become 50-100 phone calls and emails.  As for other enterprise class wireless messaging solutions, I have yet to see the same sort of security issues.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.whackberry.com/archives/11/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
