http://twitter.com/#search?q=facebook -- 200 tweets / min describing a face-book outage. [it's kinda phunny] -- Wes http://claimid.com/wesyoung
Seems to be working for me, just exceptionally slow. -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Wes Young Sent: Saturday, February 20, 2010 9:27 AM To: outages@outages.org Subject: [outages] facebook issues http://twitter.com/#search?q=facebook -- 200 tweets / min describing a face-book outage. [it's kinda phunny] -- Wes http://claimid.com/wesyoung _______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
On 02/20/2010 09:26 AM, Wes Young wrote:
http://twitter.com/#search?q=facebook -- 200 tweets / min describing a face-book outage.
I don't tweet or use facebook, but.... Seeing DNS resolution failures from here (Denver on Cogent) for facebookmail.com - success on facebook.com: $ dig mx facebookmail.com +trace ; <<>> DiG 9.6.1-P3 <<>> mx facebookmail.com +trace ;; global options: +cmd . 151474 IN NS J.ROOT-SERVERS.NET. . 151474 IN NS C.ROOT-SERVERS.NET. . 151474 IN NS D.ROOT-SERVERS.NET. . 151474 IN NS B.ROOT-SERVERS.NET. . 151474 IN NS A.ROOT-SERVERS.NET. . 151474 IN NS I.ROOT-SERVERS.NET. . 151474 IN NS M.ROOT-SERVERS.NET. . 151474 IN NS E.ROOT-SERVERS.NET. . 151474 IN NS L.ROOT-SERVERS.NET. . 151474 IN NS H.ROOT-SERVERS.NET. . 151474 IN NS F.ROOT-SERVERS.NET. . 151474 IN NS K.ROOT-SERVERS.NET. . 151474 IN NS G.ROOT-SERVERS.NET. ;; Received 360 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms com. 172800 IN NS a.gtld-servers.net. com. 172800 IN NS b.gtld-servers.net. com. 172800 IN NS c.gtld-servers.net. com. 172800 IN NS d.gtld-servers.net. com. 172800 IN NS e.gtld-servers.net. com. 172800 IN NS f.gtld-servers.net. com. 172800 IN NS g.gtld-servers.net. com. 172800 IN NS h.gtld-servers.net. com. 172800 IN NS i.gtld-servers.net. com. 172800 IN NS j.gtld-servers.net. com. 172800 IN NS k.gtld-servers.net. com. 172800 IN NS l.gtld-servers.net. com. 172800 IN NS m.gtld-servers.net. ;; Received 497 bytes from 128.63.2.53#53(H.ROOT-SERVERS.NET) in 139 ms facebookmail.com. 172800 IN NS dns04.sf2p.tfbnw.net. facebookmail.com. 172800 IN NS dns05.sf2p.tfbnw.net. ;; Received 120 bytes from 192.35.51.30#53(f.gtld-servers.net) in 97 ms ;; connection timed out; no servers could be reached $ dig mx facebook.com +trace ; <<>> DiG 9.6.1-P3 <<>> mx facebook.com +trace ;; global options: +cmd . 151352 IN NS J.ROOT-SERVERS.NET. . 151352 IN NS B.ROOT-SERVERS.NET. . 151352 IN NS G.ROOT-SERVERS.NET. . 151352 IN NS C.ROOT-SERVERS.NET. . 151352 IN NS K.ROOT-SERVERS.NET. . 151352 IN NS M.ROOT-SERVERS.NET. . 151352 IN NS A.ROOT-SERVERS.NET. . 151352 IN NS L.ROOT-SERVERS.NET. . 151352 IN NS H.ROOT-SERVERS.NET. . 151352 IN NS D.ROOT-SERVERS.NET. . 151352 IN NS F.ROOT-SERVERS.NET. . 151352 IN NS I.ROOT-SERVERS.NET. . 151352 IN NS E.ROOT-SERVERS.NET. ;; Received 480 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms com. 172800 IN NS H.GTLD-SERVERS.NET. com. 172800 IN NS I.GTLD-SERVERS.NET. com. 172800 IN NS K.GTLD-SERVERS.NET. com. 172800 IN NS C.GTLD-SERVERS.NET. com. 172800 IN NS B.GTLD-SERVERS.NET. com. 172800 IN NS E.GTLD-SERVERS.NET. com. 172800 IN NS F.GTLD-SERVERS.NET. com. 172800 IN NS A.GTLD-SERVERS.NET. com. 172800 IN NS D.GTLD-SERVERS.NET. com. 172800 IN NS G.GTLD-SERVERS.NET. com. 172800 IN NS J.GTLD-SERVERS.NET. com. 172800 IN NS L.GTLD-SERVERS.NET. com. 172800 IN NS M.GTLD-SERVERS.NET. ;; Received 490 bytes from 192.112.36.4#53(G.ROOT-SERVERS.NET) in 137 ms facebook.com. 172800 IN NS dns04.sf2p.tfbnw.net. facebook.com. 172800 IN NS dns05.sf2p.tfbnw.net. facebook.com. 172800 IN NS ns1.facebook.com. facebook.com. 172800 IN NS ns2.facebook.com. ;; Received 184 bytes from 192.55.83.30#53(M.GTLD-SERVERS.NET) in 269 ms facebook.com. 1200 IN MX 10 mx.snc1.tfbnw.net. facebook.com. 1200 IN MX 10 mx.sf2p.tfbnw.net. facebook.com. 172800 IN NS ns2.facebook.com. facebook.com. 172800 IN NS dns05.sf2p.tfbnw.net. facebook.com. 172800 IN NS dns04.sf2p.tfbnw.net. facebook.com. 172800 IN NS ns1.facebook.com. ;; Received 195 bytes from 204.74.66.132#53(ns1.facebook.com) in 109 ms Trying to 'talk' to dns04.sf2p.tfbnw.net and dns05.sf2p.tfbnw.net fails with a timeout. Am able to resolve them OK 69.63.176.8 and 69.63.176.9 but traces to them and pings fail: HOST: csmdv.highmtnsoftware.com Loss% Snt Last Avg Best Wrst StDev 1. 10.10.100.254 0.0% 5 0.9 1.0 0.9 1.5 0.2 2. 192.168.0.1 20.0% 5 1.5 1.5 1.5 1.6 0.0 3. 38.116.136.1 0.0% 5 53.5 55.9 53.0 66.5 6.0 4. 38.112.6.145 0.0% 5 53.4 53.6 53.4 53.9 0.2 5. 66.250.10.217 0.0% 5 53.7 53.7 53.4 54.1 0.3 6. 154.54.24.82 0.0% 5 65.6 67.2 65.1 74.6 4.1 7. 154.54.5.217 0.0% 5 76.5 76.4 75.6 78.3 1.1 8. 154.54.6.94 0.0% 5 76.5 81.5 75.9 93.8 7.9 9. 154.54.12.138 40.0% 5 75.7 75.8 75.7 75.9 0.1 10. 129.250.2.173 0.0% 5 80.1 77.2 76.2 80.1 1.6 11. 129.250.4.25 20.0% 5 100.7 105.2 100.1 118.9 9.2 12. 129.250.5.55 20.0% 5 99.3 99.6 99.3 99.8 0.3 13. 128.241.219.126 0.0% 5 120.3 111.9 99.1 127.4 12.5 14. 74.119.76.21 0.0% 5 115.0 104.1 101.0 115.0 6.1 15. 74.119.76.26 0.0% 5 101.3 105.0 101.3 117.9 7.2 16. 204.15.23.253 0.0% 5 102.0 102.8 102.0 104.0 0.7 17. ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 Chris
I always laugh when I see Facebook and Twitter outages appear on this list! The first thought that comes to my mind is usually "who cares". No offense intended to anyone. I do realize that there are some companies that have legitimate uses for these services, I just come from the opposite end of the spectrum where we block them. - Chris
On 2/20/2010 2:36 PM, Chris Burwell wrote:
I always laugh when I see Facebook and Twitter outages appear on this list! The first thought that comes to my mind is usually "who cares".
No offense intended to anyone. I do realize that there are some companies that have legitimate uses for these services, I just come from the opposite end of the spectrum where we block them.
Some people have "customers" (write if you need help with the concept) who pay for the use of such things. -- "Government big enough to supply everything you need is big enough to take everything you have." Remember: The Ark was built by amateurs, the Titanic by professionals. Requiescas in pace o email Ex turpi causa non oritur actio Eppure si rinfresca ICBM Targeting Information: http://tinyurl.com/4sqczs http://tinyurl.com/7tp8ml
I agree. The only reason I like to see a notice on this type of thing is that as an ISP I want to know that an issue reported by a user isn't our fault. It's relevant on outages but certainly not worth lengthy discussion and debate. -Scott -- Sent from my Palm Pre Chris Burwell wrote: I always laugh when I see Facebook and Twitter outages appear on this list! The first thought that comes to my mind is usually "who cares". No offense intended to anyone. I do realize that there are some companies that have legitimate uses for these services, I just come from the opposite end of the spectrum where we block them. - Chris _______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
It is most certainly relevent when some of us get lit up by consumers (without whom we wouldn't be in business) who want to know why they can't use social networking products important to them. Sent from my Verizon Wireless BlackBerry -----Original Message----- From: "Scott Berkman" <scott@sberkman.net> Date: Sat, 20 Feb 2010 15:49:21 To: Chris Burwell<cburwell@gmail.com>; outages@outages.org<outages@outages.org> Subject: Re: [outages] facebook issues _______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
On Sat, Feb 20, 2010 at 2:36 PM, Chris Burwell <cburwell@gmail.com> wrote:
I always laugh when I see Facebook and Twitter outages appear on this list! The first thought that comes to my mind is usually "who cares". No offense intended to anyone. I do realize that there are some companies that have legitimate uses for these services, I just come from the opposite end of the spectrum where we block them.
According to Alexa rankings, facebook.com has a reach of 30% of the Internet users, Google web search has a reach of 40%. And yes, companies have legitimate uses for facebook and twitter, in terms of marketing their wares, and finding/communicating with vendors, it would be insane to ignore opportunities for free marketing and PR channels there. Facebook, Wikipedia, MSN, Myspace, Twitter, Youtube, Yahoo, Google _are_ the internet, as far as joe sixpack knows. Blocking any of those is almost unthinkable, but your network, your rules. An outage of any of these is still likely to result in a report of "issues" from end-users. If you are an ISP, people are buying your services so they can access these. It is good for you to know if the sites themselves are actually having issues, so you can prove their issues are not due to your network. -- -J
participants (8)
-
Blake Pfankuch -
Chris Burwell -
Chris Stone -
James Hess -
Jason L. Sparks -
Larry Sheldon -
Scott Berkman -
Wes Young