Re: [outages] WhatsApp down?

2021-10-04 Thread Jay Farrell via Outages
Yes, Facebook and Instagram as well. On Mon, Oct 4, 2021 at 11:58 AM James Lawrie via Outages < outages@outages.org> wrote: > No connection at all from my side and twitter seems to confirm > ___ > Outages mailing list > Outages@outages.org >

Re: [outages] Facebook and Instagram are down for some users

2019-03-15 Thread Jay Farrell via Outages
That was two (2) days ago, beginning ~noon EDT Wednesday. The outage and subsequent impairment lasted 10+ hours for most users. It's possible there is some residual impairment I suppose. I haven't seen problems at all today myself, but your mileage may vary. On Fri, Mar 15, 2019 at 4:03 PM Robbie

Re: [outages] Facebook

2018-09-03 Thread Jay Farrell via Outages
Seems to be worldwide, judging by the disqus comments pouring in (dozens per minute) at downdetector.com. Went down for me in Philadelphia at ~4:45 PM EDT. On Mon, Sep 3, 2018 at 5:03 PM Jon Lewis via Outages wrote: > So...did Trump shut them down? :) > >

[outages] Facebook commenting and Messenger down on Safari since late last evening

2017-10-04 Thread Jay Farrell via Outages
Facebook is broken in Safari web browser again since late last evening (this also happened a month or two ago). Can see posts, but cannot see nor add comments. Also FB Messenger is blank. Works ok in Chrome browser. Multiple reports of the issue on downdetector.com.

Re: [outages] smugmug.com (on cloudfront) is down

2017-09-15 Thread Jay Farrell via Outages
Working from Conshohocken/Philadelphia PA; doesn't redirect. Jay On Fri, Sep 15, 2017 at 10:32 PM, Patrick W. Gilmore via Outages < outages@outages.org> wrote: > Thanks. Wish I were in Milwaukee. :-) > > DownForEveryoneOrJustMe says: > It's not just you!

Re: [outages] www.LinkedIn.com Down?

2017-05-03 Thread Jay Farrell via Outages
No problem from Philadelphia via Vz DSL On Wed, May 3, 2017 at 7:26 PM, Ivan Kovacevic via Outages < outages@outages.org> wrote: > > > > > “It's not just you! http://www.linkedin.com looks down from here.” > > > > Microsoft… bringing you the web equivalent of the BSOD. > > > > Best Regards, > >

Re: [outages] Amazon S3 down

2017-03-03 Thread Jay Farrell via Outages
RFO: https://aws.amazon.com/message/41926/ On Wed, Mar 1, 2017 at 11:44 AM, Chapman, Brad (NBCUniversal) via Outages < outages@outages.org> wrote: > Well, that makes **two** post-mortems I look forward to reading about > this month: the Oscar night best picture kerfuffle, and now this Amazon >

Re: [outages] Cogent Outage in Philadelphia

2016-11-25 Thread Jay Farrell via Outages
A relatively small fire I'm sure, as it hasn't made the news here in Philly. That address is the Mellon Center, fwiw. On Fri, Nov 25, 2016 at 1:58 PM, John Petrini via Outages < outages@outages.org> wrote: > Thank You! > > ___ > > John Petrini > > NOC Systems Administrator // *CoreDial, LLC*

Re: [outages] Facebook is down

2016-08-26 Thread Jay Farrell via Outages
Facebook is back up in Philadelphia as well. On Fri, Aug 26, 2016 at 7:17 PM, Randall (Randy) Raitz via Outages < outages@outages.org> wrote: > Seeing recoveries in Denver, CO at this time. > > -Original Message- > From: Outages [mailto:outages-boun...@outages.org] On Behalf Of Seth >

Re: [outages] Facebook is down

2016-08-26 Thread Jay Farrell via Outages
Appears to be very widespread, judging by the rapidly incrementing discus comments on downdetector, as well as their live outage map. In Philadelphia it died for me at ~7pm EDT. http://downdetector.com/status/facebook/map/ ___ Outages mailing list

Re: [outages] Cannot access 132.60.0.0/16 from 141.219.0.0/16

2016-06-08 Thread Jay Farrell via Outages
16 at 9:38 AM, Jay Farrell via Outages > <outages@outages.org> wrote: >> >> Here's an odd trace from Verizon DSL in phl; traceroute *passes thru* >> the target IP (18th & 19th hop) and keeps on going >> >> $ traceroute 132.60.10.110 >> >>

Re: [outages] Cannot access 132.60.0.0/16 from 141.219.0.0/16

2016-06-08 Thread Jay Farrell via Outages
Here's an odd trace from Verizon DSL in phl; traceroute *passes thru* the target IP (18th & 19th hop) and keeps on going $ traceroute 132.60.10.110 traceroute to 132.60.10.110 (132.60.10.110), 64 hops max, 52 byte packets 1 192.168.1.1 (192.168.1.1) 4.847 ms 0.775 ms 0.729 ms 2