[Outages-discussion] [outages] Facebook web interface partial outage 2120 EDT 6/18

[Frank Bulk]

Since I don't also check their HTTPv4, I can't say if the issue was just
HTTPv6 or both.  This is where companies like Keynote and Pingdom do much
better than our anecdotal reports.

 

Frank

 

From: George Herbert [mailto:george.herbert at gmail.com] 
Sent: Tuesday, June 18, 2013 10:07 PM
To: Frank Bulk
Cc: Jay Ashworth; outages-discussion
Subject: Re: [Outages-discussion] [outages] Facebook web interface partial
outage 2120 EDT 6/18

 

Ah, interesting.  Data point:  I have desk-native dual stack IPv4 and IPv6
here and doing a ping I am connected to FB v6.  So presumably my troubles
were to the IPv6 service.

 

Should remember to check that for future reports.

 

On Tue, Jun 18, 2013 at 7:25 PM, Frank Bulk <frnkblk at iname.com
<mailto:frnkblk at iname.com> > wrote:

I saw HTTPv6 access to www.facebook.com <http://www.facebook.com>  have
issues between 7:55 and 8:29 pm Central, a mixture of socket timeouts, "503
No server is available for the request", "Connection refused", and  "No data
received from host".  

 

Frank

 

From: Outages-discussion [mailto:outages-discussion-bounces at outages.org
<mailto:outages-discussion-bounces at outages.org> ] On Behalf Of George
Herbert
Sent: Tuesday, June 18, 2013 9:00 PM
To: Jay Ashworth
Cc: outages-discussion
Subject: Re: [Outages-discussion] [outages] Facebook web interface partial
outage 2120 EDT 6/18

 

I can anecdotally report intermittent freezes and similar behavior from
inside 13445 in the SF Bay Area.  Going back longer than your report,
perhaps 5:00 PM Pacific time start of issues?

 

On Tue, Jun 18, 2013 at 6:31 PM, Jay Ashworth <jra at baylink.com
<mailto:jra at baylink.com> > wrote:

Some subset of FB appears to be down for some people from some places
for about the last 10 minutes; according to both my experience and reports
from a couple dozen people on twitter.

I'm on Sprint 4G in Tampa.  Got some error messages, and now no response
to homepage or internal links... in Chrome.   Clearing cookies and local
storage didn't help.

Fresh login on Firefox on the same machine *did* work; I suspect a load
balancer broke, and Chrome has the IP internally cached and won't drop it.

Win7 resolves www.facebook.com <http://www.facebook.com>  to 69.171.242.27,
star.c10r.facebook.com <http://star.c10r.facebook.com> 

Can't post an mtr; I'm on Windows.

Most of the things that appear to be outage reports are in other languages,
mostly South American, I think, Portuguese, Spanish...

... and see?  You write a detailed enough report, and it will come back
before
you're done.

Anyway, followups to -discuss, unless your email is @facebook.com
<http://facebook.com> , and you
*know* what was going on.  :-)

Cheers,
-- jra

--
Jay R. Ashworth                  Baylink
jra at baylink.com <mailto:jra at baylink.com> 
Designer                     The Things I Think                       RFC
2100
Ashworth & Associates     http://baylink.pitas.com         2000 Land Rover
DII
St Petersburg FL USA               #natog                      +1 727 647
1274 <tel:%2B1%20727%20647%201274> 
_______________________________________________
Outages mailing list
Outages at outages.org <mailto:Outages at outages.org> 
https://puck.nether.net/mailman/listinfo/outages





 

-- 
-george william herbert
george.herbert at gmail.com <mailto:george.herbert at gmail.com>  





 

-- 
-george william herbert
george.herbert at gmail.com <mailto:george.herbert at gmail.com>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages-discussion/attachments/20130618/1f85ec61/attachment.html>