<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/unified-communications/gotomeeting-outage.asp" />
  <link rel="self" type="application/atom+xml" href="http://blog.tmcnet.com/blog/tom-keating/atom.xml" />
  <id>tag:blog.tmcnet.com,2013:/blog/tom-keating//4/tag:blog.tmcnet.com,2010:/blog/tom-keating//4.43354-</id>
  <updated></updated>
  <title>Comments for GoToMeeting Outage</title>
  <subtitle>VoIP &amp; Gadgets blog - Latest news in VoIP &amp; gadgets, wireless, mobile phones, reviews, &amp; opinions</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.38</generator>
  <entry>
    <id>tag:blog.tmcnet.com,2010:/blog/tom-keating//4.43354</id>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/unified-communications/gotomeeting-outage.asp" />
    <link rel="service.edit" type="application/atom+xml" href="http://blog.tmcnet.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=43354" title="GoToMeeting Outage" />
    <published>2010-02-17T16:12:35Z</published>
    <updated>2010-02-17T16:14:25Z</updated>
    <title>GoToMeeting Outage</title>
    <summary>Noticed a problem with GoToMeeting yesterday and learned via Twitter they indeed had a service outage. GoToMeeting is used by thousands of businesses and probably millions of users to give sales demos, online training, and more. I live in GoToMeeting...</summary>
    <author>
      <name>Tom Keating</name>
      <uri>http://blog.tmcnet.com/blog/tom-keating/</uri>
    </author>
    
    <category term="TMCnet" />
    
    <category term="Unified Communications" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.tmcnet.com/blog/tom-keating/">
      <![CDATA[<span style="display: inline;" class="mt-enclosure mt-enclosure-image"><img width="202" height="46" style="float: right; margin: 0pt 0pt 20px 20px;" class="mt-image-right" src="http://blog.tmcnet.com/blog/tom-keating/images/gotomeeting-logo.gif" alt="gotomeeting-logo.gif" /></span>Noticed a problem with GoToMeeting yesterday and <a href="http://twitter.com/GoToMeeting/status/9192110328">learned via Twitter</a> they indeed had a service outage. GoToMeeting is used by thousands of businesses and probably millions of users to give sales demos, online training, and more. I <i>live </i>in GoToMeeting and WebEx due to all my press briefings with  vendors showing me their latest wares.<br /><br />I have never encountered any service issue problems with GoToMeeting in the years I have used it. Yesterday was the first time. I guess I can't be too hard on them, since even companies like Google and Microsoft have had service disruptions to their websites. Even more critical than website uptime is your voice service -- and even major VoIP service providers <a href="http://blog.tmcnet.com/blog/tom-keating/vonage/vonage-outage.asp">Vonage</a> and <a href="http://blog.tmcnet.com/blog/tom-keating/packet8/packet8-service-down.asp">Packet8</a> have had outages.<br /><br />I certainly have to give props to GoToMeeting for proactively using Twitter to fully disclose the outage and <a href="http://twitter.com/GoToMeeting/status/9192246601">respond to users</a> <a href="http://twitter.com/GoToMeeting/status/9191875849">complaining</a> on Twitter about the outage. Being proactive to customers via Twitter more than makes up for the brief outage. We don't need another <a href="http://news.cnet.com/8301-13577_3-10454328-36.html">Kevin Smith PR disaster incident</a> on our hands.<br />]]>
      
    </content>
  </entry>

</feed>
