On 27 Apr 2009, at 04:24, Suresh Ramasubramanian wrote:
If your email and phone communications are down due to a connectivity
break, and your customers get connectivity from you [assume no backup
links, by default .. you'd be surprised at how many smaller customers
get by with a single link
On Sun, Apr 26, 2009 at 8:13 PM, char...@thewybles.com wrote:
Twitter URL is an rss feed as well.
That should work then, and a reasonable solution for not having to
sign up for a third party service.
--
Later, Joe
Suresh Ramasubramanian wrote:
If your email and phone communications are down due to a connectivity
break, and your customers get connectivity from you [assume no backup
links, by default .. you'd be surprised at how many smaller customers
get by with a single link and no backups at all. If
On Mon, Apr 27, 2009 at 11:31 AM, Mike Lewinski m...@rockynet.com wrote:
Suresh Ramasubramanian wrote:
If your email and phone communications are down due to a connectivity
break, and your customers get connectivity from you [assume no backup
links, by default .. you'd be surprised at how
William McCall wrote:
I should have clarified. Third party physical control isn't necessarily the
issue, but third party administration and delivery (in the context of
twitter) is.
Dedicated servers are cheap and you can maintain control of the content.
But useless if the customer's data
On Mon, Apr 27, 2009 at 12:13 PM, Mike Lewinski m...@rockynet.com wrote:
But useless if the customer's data connection is down and their local cell
phones are the only remaining method of communication.
If 25% of our users would check their twitter feed first and let their boss
know They
We're experimenting with Twitter as a means to communicate anytime there
are system-wide outages (in addition to regular maintenance
notifications). Adoption is slow but I foresee growth once we really get
the word out.
Being a data and VoIP provider, certain events can effect both email and
On Sun, Apr 26, 2009 at 7:40 PM, Mike Lewinski m...@rockynet.com wrote:
We're experimenting with Twitter as a means to communicate anytime there are
system-wide outages (in addition to regular maintenance notifications).
Adoption is slow but I foresee growth once we really get the word out.
Twitter URL is an rss feed as well.
--Original Message--
From: JoeSox
To: nanog@nanog.org
Subject: Re: OOB customer communications (Re: Looking for Support Contact at
Equifax)
Sent: Apr 26, 2009 8:08 PM
On Sun, Apr 26, 2009 at 7:40 PM, Mike Lewinski m...@rockynet.com wrote:
We're
If your email and phone communications are down due to a connectivity
break, and your customers get connectivity from you [assume no backup
links, by default .. you'd be surprised at how many smaller customers
get by with a single link and no backups at all. If their
connectivity is down too -
you've been affected.
A lot of places still work with an MO of secrecy. The service I support is
one of them. From a technical perspective, the idea is solid though.
--WJM IV
--Original Message--
From: JoeSox
To: nanog@nanog.org
Subject: Re: OOB customer communications (Re: Looking
William McCall wrote:
I could see someone complaining about the idea of letting a third party
carry outage info like that... at least in my environment.
How else do you propose getting outage information to your customers?
If the information provider is under your control (not a 3rd party),
On Sun, Apr 26, 2009 at 11:18 PM, JC Dill jcdill.li...@gmail.com wrote:
How else do you propose getting outage information to your customers?
I should have clarified. Third party physical control isn't necessarily the
issue, but third party administration and delivery (in the context of
13 matches
Mail list logo
