<?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>Dotcom-Monitor Blog &#187; status</title>
	<atom:link href="http://www.dotcom-monitor.com/blog/index.php?tag=status&#038;feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://www.dotcom-monitor.com/blog</link>
	<description>Website Monitoring You Can Trust</description>
	<lastBuildDate>Fri, 24 May 2013 19:54:02 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Tracking DNS: The Network Solutions DNS errors</title>
		<link>http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/network-solutions-dns-errors/</link>
		<comments>http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/network-solutions-dns-errors/#comments</comments>
		<pubDate>Sat, 30 Mar 2013 16:02:32 +0000</pubDate>
		<dc:creator>Vadim Mazo</dc:creator>
				<category><![CDATA[Network Services Monitoring]]></category>
		<category><![CDATA[System Status]]></category>
		<category><![CDATA[DNS error]]></category>
		<category><![CDATA[DNS errors]]></category>
		<category><![CDATA[dns servers]]></category>
		<category><![CDATA[DNS time out]]></category>
		<category><![CDATA[DNS time out error]]></category>
		<category><![CDATA[Network Solutions DNS]]></category>
		<category><![CDATA[Network Solutions DNS servers]]></category>
		<category><![CDATA[status]]></category>
		<category><![CDATA[system status]]></category>

		<guid isPermaLink="false">http://www.dotcom-monitor.com/blog/?p=2327</guid>
		<description><![CDATA[<p>April 2, 2013 – Network Solutions DNS, a major provider of domain name server (DNS) services, experienced an issue over the Mar 30-31, 2013 weekend resulting in many websites, including websites owned by Dotcom-Monitor clients, having website DNS time out errors.  Intermittent Network Solution DNS issues were noted late afternoon and evening hours on March 29. Dotcom-Monitor then began tracking consistent DNS time out errors involving Network Solutions DNS servers early on Saturday morning, March 30, 2013. The Network Solutions DNS servers involved were NS22.WORLDNIC.COM (206.188.198.11) and NS21.WORLDNIC.COM (205.178.190.11).</p><p>The post <a href="http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/network-solutions-dns-errors/">Tracking DNS: The Network Solutions DNS errors</a> appeared first on <a href="http://www.dotcom-monitor.com/blog">Dotcom-Monitor Blog</a>.</p>]]></description>
		<wfw:commentRss>http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/network-solutions-dns-errors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>UltraDNS Outage &#124; Websites using UltraDNS experience short Downtime</title>
		<link>http://www.dotcom-monitor.com/blog/index.php/dotcom-monitor-news/ultradns-outage-dns-error-downtime/</link>
		<comments>http://www.dotcom-monitor.com/blog/index.php/dotcom-monitor-news/ultradns-outage-dns-error-downtime/#comments</comments>
		<pubDate>Tue, 29 Jan 2013 23:22:31 +0000</pubDate>
		<dc:creator>Dan Oksnevad</dc:creator>
				<category><![CDATA[Dotcom-Monitor News]]></category>
		<category><![CDATA[System Status]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[DNS error]]></category>
		<category><![CDATA[DNS issues]]></category>
		<category><![CDATA[DNS outage]]></category>
		<category><![CDATA[Neustar]]></category>
		<category><![CDATA[status]]></category>
		<category><![CDATA[system status]]></category>
		<category><![CDATA[UltraDNS Outage]]></category>

		<guid isPermaLink="false">http://www.dotcom-monitor.com/blog/?p=1879</guid>
		<description><![CDATA[<p>UltraDNS Outage: We are aware that some websites and reports may indicate an UltraDNS outage on January 28, 2013.  We have verified that UltraDNS did have a short DNS issue. We will continue to monitor the situation, although it now appears to be resolved.</p><p>The post <a href="http://www.dotcom-monitor.com/blog/index.php/dotcom-monitor-news/ultradns-outage-dns-error-downtime/">UltraDNS Outage | Websites using UltraDNS experience short Downtime</a> appeared first on <a href="http://www.dotcom-monitor.com/blog">Dotcom-Monitor Blog</a>.</p>]]></description>
		<wfw:commentRss>http://www.dotcom-monitor.com/blog/index.php/dotcom-monitor-news/ultradns-outage-dns-error-downtime/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>System Status Update: DNS Error Issue &#124; Zerigo DNS services</title>
		<link>http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/update-dns-error-issue/</link>
		<comments>http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/update-dns-error-issue/#comments</comments>
		<pubDate>Mon, 23 Jul 2012 19:57:13 +0000</pubDate>
		<dc:creator>Brad Canham</dc:creator>
				<category><![CDATA[Network Services Monitoring]]></category>
		<category><![CDATA[System Status]]></category>
		<category><![CDATA[DDoS]]></category>
		<category><![CDATA[DDoS DNS]]></category>
		<category><![CDATA[DNS errors]]></category>
		<category><![CDATA[status]]></category>
		<category><![CDATA[system status]]></category>
		<category><![CDATA[Zerigo DNS hosting]]></category>
		<category><![CDATA[Zerigo DNS services]]></category>

		<guid isPermaLink="false">http://www.dotcom-monitor.com/blog/?p=555</guid>
		<description><![CDATA[<p>Starting at around 06:00 AM CST, July 23, 2012 Dotcom-Monitor began to detect a higher than usual number of DNS-related errors. The errors were sporadic and happening in bursts every couple of hours.

We are still looking for a root cause, but we believe issue started with a DDoS on Zerigo DNS services. We have a large number of our clients using Zerigo for their DNS hosting. Zerigo took their servers down due to the DDoS DNS this morning.</p><p>The post <a href="http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/update-dns-error-issue/">System Status Update: DNS Error Issue | Zerigo DNS services</a> appeared first on <a href="http://www.dotcom-monitor.com/blog">Dotcom-Monitor Blog</a>.</p>]]></description>
		<wfw:commentRss>http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/update-dns-error-issue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Level3 Communications and AT&amp;T Ongoing Issues &#124; Outage Experienced</title>
		<link>http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/level3-and-att-ongoing-issues/</link>
		<comments>http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/level3-and-att-ongoing-issues/#comments</comments>
		<pubDate>Mon, 08 Aug 2011 19:27:54 +0000</pubDate>
		<dc:creator>Vadim Mazo</dc:creator>
				<category><![CDATA[Network Services Monitoring]]></category>
		<category><![CDATA[AT&T]]></category>
		<category><![CDATA[Level3]]></category>
		<category><![CDATA[Level3 communications]]></category>
		<category><![CDATA[outage]]></category>
		<category><![CDATA[status]]></category>

		<guid isPermaLink="false">http://www.dotcom-monitor.com/blog/?p=262</guid>
		<description><![CDATA[<p>Level3 Communications and AT&#038;T appear to be having ongoing issues over the last couple days resulting in experienced outages.</p><p>The post <a href="http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/level3-and-att-ongoing-issues/">Level3 Communications and AT&#038;T Ongoing Issues | Outage Experienced</a> appeared first on <a href="http://www.dotcom-monitor.com/blog">Dotcom-Monitor Blog</a>.</p>]]></description>
		<wfw:commentRss>http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/level3-and-att-ongoing-issues/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Level 3 Communications Backbone Connectivity Issue</title>
		<link>http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/aug-1-level3-communications-backbone-issue/</link>
		<comments>http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/aug-1-level3-communications-backbone-issue/#comments</comments>
		<pubDate>Mon, 01 Aug 2011 19:41:23 +0000</pubDate>
		<dc:creator>Brad Canham</dc:creator>
				<category><![CDATA[Network Services Monitoring]]></category>
		<category><![CDATA[System Status]]></category>
		<category><![CDATA[IP NOC]]></category>
		<category><![CDATA[Level 3 Communications]]></category>
		<category><![CDATA[OPS Engineers]]></category>
		<category><![CDATA[status]]></category>
		<category><![CDATA[system status]]></category>

		<guid isPermaLink="false">http://www.dotcom-monitor.com/blog/?p=255</guid>
		<description><![CDATA[<p>Aug 1, 2011 – Some Dotcom-Monitor clients  may have experienced alerts due to a Level 3 Communications connectivity issue. For details see the statement below from Level 3 Communications explaining the event and the resolution.

"Much of the internet connectivity in and to the Continental United States was degraded by an outage within the Level 3 Communications backbone that began at approximately 17:22 1 August 2011 UTC.  The impact of this event was felt not only on the Level3 backbone but also on other carriers as providers shifted large amounts of traffic that would have normally transited the Level3 network onto alternate network paths, causing increased latency and congestion and packet loss."</p><p>The post <a href="http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/aug-1-level3-communications-backbone-issue/">Level 3 Communications Backbone Connectivity Issue</a> appeared first on <a href="http://www.dotcom-monitor.com/blog">Dotcom-Monitor Blog</a>.</p>]]></description>
		<wfw:commentRss>http://www.dotcom-monitor.com/blog/index.php/network-services-monitoring/aug-1-level3-communications-backbone-issue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
