Looking for Support Contact at Equifax
Their site is down. Thanks.
Re: Looking for Support Contact at Equifax
Try this address or you could try calling: Administrative,Technical Contact: Equifax J42M Domain Admin P.O. Box 740006 Atlanta, GA 30374-0006 US Phone: +1.4048858000 Email: hostmas...@equifax.com HTH --bc On Apr 26, 2009, at 4:37 PM, John Martinez wrote: Their site is down. Thanks.
Re: Looking for Support Contact at Equifax
Thank you. Ben wrote: > Try this address or you could try calling: > > Administrative,Technical Contact: > Equifax J42M > Domain Admin > P.O. Box 740006 > Atlanta, GA 30374-0006 > US > Phone: +1.4048858000 > Email: hostmas...@equifax.com > > HTH > --bc > > On Apr 26, 2009, at 4:37 PM, John Martinez wrote: > >> Their site is down. >> Thanks. >> >
Equifax is experiencing a system wide outage tix #8015791
Ben wrote: > Try this address or you could try calling: > > Administrative,Technical Contact: > Equifax J42M > Domain Admin > P.O. Box 740006 > Atlanta, GA 30374-0006 > US > Phone: +1.4048858000 > Email: hostmas...@equifax.com > > HTH > --bc > > On Apr 26, 2009, at 4:37 PM, John Martinez wrote: > >> Their site is down. >> Thanks. >> >
OOB customer communications (Re: Looking for Support Contact at Equifax)
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 telephone communications, so having a truly OOB method of contact is potentially invaluable. It would be awesome if there was a service like twitter that wasn't down as often as it is. Anyone have a list of all xSPs using Twitter? Mike
Re: OOB customer communications (Re: Looking for Support Contact at Equifax)
On Sun, Apr 26, 2009 at 7:40 PM, Mike Lewinski 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 over RSS? I'd choose RSS. All I need is a url; not even a user agreement! -- Later, Joe
Re: OOB customer communications (Re: Looking for Support Contact at Equifax)
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 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 over RSS? I'd choose RSS. All I need is a url; not even a user agreement! -- Later, Joe Sent via BlackBerry from T-Mobile
Re: OOB customer communications (Re: Looking for Support Contact at Equifax)
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 - they just cant get to twitter right? And there's quite likely to be assorted HR policies that say "no goofing off on the internet at work, and that includes twitter, facebook etc" I'd suggest gather as much backup contact info as you can - cellphone + landline (presumably from another carrier, and wired instead of voip), mailing address etc. Use it in series. It is quite scriptable (and even the bulk postal mail part can be automated to some extent). --srs On Mon, Apr 27, 2009 at 8:10 AM, Mike Lewinski wrote: > Being a data and VoIP provider, certain events can effect both email and > telephone communications, so having a truly OOB method of contact is > potentially invaluable. > > It would be awesome if there was a service like twitter that wasn't down as > often as it is. > > Anyone have a list of all xSPs using Twitter?
Re: OOB customer communications (Re: Looking for Support Contact at Equifax)
I could see someone complaining about the idea of letting a third party carry outage info like that... at least in my environment. Really, it could be a blessing or a curse for your marketing team, but it does depend on how you handle it I suppose. Potential clients could use the information to see your ability to meet SLA targets before they sign on. If you're not the big dog in the arena, it can very easily work against you by enhancing the BS that competitors will provide. Or, of course, it can give them a warm fuzzy feeling knowing that they can readily see the issues and know how 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 for Support Contact > at Equifax) > Sent: Apr 26, 2009 8:08 PM > > On Sun, Apr 26, 2009 at 7:40 PM, Mike Lewinski 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. > > > > > >
Re: OOB customer communications (Re: Looking for Support Contact at Equifax)
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), then whatever took out your primary services (internet services, phone services) might also take out your access to the outage channel that is under your control (e.g. fat-fingered admin messes up an ACL). I *like it* when my service provider has an OOB network outage channel. My biggest complaint has been with networks that setup a channel like this but then get "too busy" during an outage to make use of it. If you are going to setup a channel like this, make sure you use it. Also, if you post a partial update, make sure you follow up with more information when you have it. Some of us read the archives to see if this information was posted and followed-up on in a timely fashion, to evaluate the outage reporting service record before signing up. 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 their connectivity is down too - they just cant get to twitter right? Um... what about text messages to these newfangled cell phone thingies? http://www.ehow.com/how_2075926_use-twitter-cell-phone.html Unless you are AT&T or Comcast (or similar) and your customers have U-Verse or Comcast Triple Play (or similar) it has to be a fairly widespread outage to take out your customer's landlines, internet, and cell phones too. If your network has that big of an outage, your customers can follow the outage news updates on the radio. jc
OOB customer communications (Re: Looking for Support Contact at Equifax)
On Sun, Apr 26, 2009 at 11:18 PM, JC Dill 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 twitter) is. Dedicated servers are cheap and you can maintain control of the content. Its not quite the same as using twitter or other third party SaaS that is similar (which can, invariably, control the content at its whim and is a nightmare to manage persons authorized to view such outage info, depending on the service) Or even a mailer that is outside of the scope of your service ops and permit only customers to subscribe. Again, its more about distribution in these environments. If I'm Company A, I really don't want to readily provide my competitor, Company B, with information on outages and a full history of it for them to use in some marketing device (which can't be compared because Company B does not publish their info, but instead provides some nice glossy-paper stats). Physical control certainly can't be the question.. or we'd have the same argument in circles, "If we have physical control, how can we ensure the outage doesn't affect this net too? Better question, why can't we fail over to the net that's working to send these notifications/updates for our down services if the net isn't affected?" That point is moot. My biggest complaint has been with networks that setup a channel like this > but then get "too busy" during an outage to make use of it. If you are > going to setup a channel like this, make sure you use it. Also, if you post > a partial update, make sure you follow up with more information when you > have it. Some of us read the archives to see if this information was posted > and followed-up on in a timely fashion, to evaluate the outage reporting > service record before signing up. > The way notifications should be distributed is in a proactive manner and followed up as a ticket or some other relevant mechanism. Implementing a process like this is trivial in many environments. Incident response should, in most cases, include a mechanism like this that has already been deployed today. Modifications (technically speaking) should not be a big issue. --WJM IV
