nextbust.jpg

4:28 PM: True informs us that regular L Taraval service resumed as of 4:06. Apparently, the issue was a “split switch,: which is “when the switch–which directs the train from one track onto another–does not stay in the correct position and the wheels of the train go onto the wrong track.” True says that the MTA’s suspects crap from the storm washing into the switch area contributed to the issue.

And, while we’re at it, NextBus seems to be back online, too. No word yet on what washed into NextBus’ ISP to cause them to go out of service.

2:43 PM: Not really related to what we’re talking about, but since this is already a Muni post, what the hell? MTA spokesperson Judson True says that the L Taraval’s derailed between 35th and 36 Aves at 2:05 today. No one was injured, and the cause for the derailment is still unknown.

L riders will be taking a bus between 22 and the zoo.

1:06 PM: MTA spokesperson Judson True says NextBus is “down because of a problem with NextBus’s Internet Service Provider on the East Coast. All NextBus customers–not just Muni–are affected. No ETA yet on getting it fixed.” Somebody at NextBus is really wishing they hadn’t thrown out those AOL CD-ROMs right now.

10:23 AM: City employees are reporting major Muni delays this morning, and NextBus, the system the SF MTA relies upon to provide Muni riders is not in operation today. This might be a good place to leave you the Muni complaint form.

After a tip from the Muni Alerts twitter, we gave NextBus a call to see if they had any idea when their system, which serves a lot of agencies, might be back online. After all, reliable Muni arrival times seem more important then ever when one is standing in the rain, right? Unfortunately, all we could reach was a voicemail that told us to speak clearly when we left our message.

A call to 311 gave us a bit more information — the representative to whom we spoke said that locally, NextBus was down because of the storm, and that NextBus’ website is down for other reasons. He offered to check his Muni schedule for me — I chose the N Judah stop closest to my house (far Outer Sunset). After checking with his supervisor, he told me that Muni was having major delays today and that I would be better served to walk the 5 blocks up to Noriega to catch the 71, as “I don’t see any Ns coming for a while.”

We’ve emailed MTA spokesperson Judson True to get more details on both the delays and on the state of the NextBus union, and will update when we hear from him.

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!
  • Leon Starr

    When I fired up Routesy this morning and saw “No prediction” I thought “Ah Muni, why am I not surprised?” Of course, it’s RAINING, why would you expect anything to work in the rain? In fact, their complaint link is broken as well – see below… Your tax dollars at work! It’s definitely a car day for me today.

    HTTP Status 500 –

    type Exception report

    message

    description The server encountered an internal error () that prevented it from fulfilling this request.

    exception

    org.apache.jasper.JasperException
    org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:460)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

    root cause

    java.lang.NullPointerException
    org.apache.jsp.General_jsp._jspService(General_jsp.java:1947)
    org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

    note The full stack trace of the root cause is available in the Apache Tomcat/5.5.26 logs.
    Apache Tomcat/5.5.26

  • Leon Starr

    When I fired up Routesy this morning and saw “No prediction” I thought “Ah Muni, why am I not surprised?” Of course, it’s RAINING, why would you expect anything to work in the rain? In fact, their complaint link is broken as well – see below… Your tax dollars at work! It’s definitely a car day for me today.

    HTTP Status 500 –

    type Exception report

    message

    description The server encountered an internal error () that prevented it from fulfilling this request.

    exception

    org.apache.jasper.JasperException
    org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:460)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

    root cause

    java.lang.NullPointerException
    org.apache.jsp.General_jsp._jspService(General_jsp.java:1947)
    org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

    note The full stack trace of the root cause is available in the Apache Tomcat/5.5.26 logs.
    Apache Tomcat/5.5.26

  • Jeff D.

    rain = MUNI delays.
    that is the beginning of the story, not the end.

  • Jeff D.

    rain = MUNI delays.
    that is the beginning of the story, not the end.

  • sfboogie

    I have lived in both SF and Chicago- neither city has particularly reliable public transit. Though I would say Chicago is more reliable than SF. At any rate I don’t think the two things (reliable and PT) go hand-in-hand in any major city where PT is a primary mode of transit. It’s either potential delays and interrupted service on PT or parking tickets and inflated parking fees if you drive. Ride a bike or walk if those two options are not suitable.

    And for anyone going to say NYC PT is reliable… A friend just posted a status update on FB last night complaining about limited evening service on his bus.

  • sfboogie

    I have lived in both SF and Chicago- neither city has particularly reliable public transit. Though I would say Chicago is more reliable than SF. At any rate I don’t think the two things (reliable and PT) go hand-in-hand in any major city where PT is a primary mode of transit. It’s either potential delays and interrupted service on PT or parking tickets and inflated parking fees if you drive. Ride a bike or walk if those two options are not suitable.

    And for anyone going to say NYC PT is reliable… A friend just posted a status update on FB last night complaining about limited evening service on his bus.