Earlier quoted context omitted.
Seems like the perfect time to launch isisitdowndownrightnow.com.
Seems like it should be isisitdownrightnowdownrightnow.com
Facebook-owned sites were down
831–840 of 1001 posts
Re: Facebook-owned sites were down
#832Re: Facebook-owned sites were down
#833Re: Facebook-owned sites were down
#834Now Twitter is starting to have problems with overload.
Re: Facebook-owned sites were down
#835Earlier quoted context omitted.
I don’t know how true it is but a few reports claim employees can’t get into the building with their badges.
I remember my first time having a meeting at Facebook and observing none of the doors had keyholes and thinking "hope their badge system never goes down"
...the doors are glass right?
Re: Facebook-owned sites were down
#836Re: Facebook-owned sites were down
#837Earlier quoted context omitted.
My suspicion is that since a lot of internal comms runs through the FB domain and since everyone is still WFH, then its probably a massive issue just to get people talking to each other to solve the problem.
I don’t know how true it is but a few reports claim employees can’t get into the building with their badges.
Re: Facebook-owned sites were down
#838Does anyone have a reasonable guess on how much money they have already lost?
Re: Facebook-owned sites were down
#839Anyone wanna estimate the cost of total downtime for facebook and instagram, as far as lost ad revenue goes - per minute?
Edit: the counter just jumped from 10B to 60M, so I doubt it's any reliable :)
Re: Facebook-owned sites were down
#840There's still no connectivity to Facebook's DNS servers: > traceroute a.ns.facebook.com traceroute to a.ns.facebook.com (129.134.30.12), 30 hops max, 60 byte packets 1 dsldevice.attlocal.net (192.168.1.254) 0.484 ms 0.474 ms 0.422 ms 2 107-131-124-1.lightspeed.sntcca.sbcglobal.net (107.131.124.1) 1.592 ms 1.657 ms 1.607 ms 3 71.148.149.196 (71.148.149.196) 1.676 ms 1.697 ms 1.705 ms 4 12.242.105.110 (12.242.105.110)…
My suspicion is that since a lot of internal comms runs through the FB domain and since everyone is still WFH, then its probably a massive issue just to get people talking to each other to solve the problem.