title-sfmetro.jpg10 AM: True is now saying that the problem “has cleared and all Muni Metro service is running normally.” So guess it’s back to the usual mysterious, unexplained delays?

9:49 AM: Commenter wlbrn2 says it took nearly an hour to get from 24th and Church to Montgomery, saying

Depart 24th and Church @ 8:35am. Arrive Montgomery @ 9:30am. Includes a forced transfer from the J to an N at Duboce.

Because when you have delays, you want to further inconvenience them by moving them from train to train! Good plan, Muni.

9:15 AM: According to MTA spokesperson Judson True, the problem continues to cause “minor rolling delays for inbound Muni Metro trains.” How is that different from “slow traffic”? Any experts on Muni terminology/spin out there?

9:08 AM: Commenter cygnor reported a 20 minute delay on her commute, saying

I can only speak for the inbound N-Judah I was just on, which was delayed about 20 minutes total, most of that time at Duboce and Church and then again in the Van Ness station.

How was your ride in?

8:38 AM: MTA spokesperson Judson True says that the entire Muni Metro system is experiencing “slow traffic” inbound (that is, towards downtown) “because of a train control problem near Embarcadero Station.” He doesn’t say how slow “slow” is, or recommend riders take other forms of transit — readers, how bad is it? Let us know in the comments or otherwise.

the author

Eve Batey is the editor and publisher of the San Francisco Appeal. She used to be the San Francisco Chronicle's Deputy Managing Editor for Online, and started at the Chronicle as their blogging and interactive editor. Before that, she was a co-founding writer and the lead editor of SFist. She's been in the city since 1997, presently living in the Outer Sunset with her husband, cat, and dog. You can reach Eve at eve@sfappeal.com.

Please make sure your comment adheres to our comment policy. If it doesn't, it may be deleted. Repeat violations may cause us to revoke your commenting privileges. No one wants that!