Ailing signals are keeping southbound Red Line commuters from dinner tonight, but possibly driving them to drink.
The T is advising "moderate" delays into town on the Red Line from Braintree due to a train that just could not make it past Quincy Center, and "minor" delays into town on the Orange Line from Forest Hills, due to a train that ascended to the pearly gates at Mass. Ave.
UPDATE: Another Blue Line train died, at Airport. More trolleys died, at Waban and Arlington.
So far this morning, trains have shuffled off this mortal coil on the Green Line (Brookline Village and Reservoir on the D and Washington Street on the B) and the Blue Line (State Street). Riders on the Orange and Red lines didn't miss any of the fun, however, due to what the T says are now fixed signal issues near Wellington and JFK/UMass (the Blue Line also had some signal woes). Red Line riders also saw trains slow due to the ongoing work on the Longfellow.
The T is warning of "moderate" delays in both directions on the Red Line due to a track problem between Kendall Square and Charles/MGH (which would be, what, the Longfellow?).
UPDATE: At 8:20, the T reported delays southbound due to a train that met its maker at Alewife.
The T is reporting "moderate" delays on the Red Line due to signal problems at Central Square. Dave translates the T's "moderate" into English:
Red line is in rough shape. Been sitting between Kendall and Central for at least 10 mins.
Equally intrepid Red Line regular Jake Wark reports from Downtown Crossing that as his Alewife train just sat there, the driver informed people rushing to the train: Read more.
At least they're moving up the line: Instead of Braintree, this time the balky Red Line signals are in North Quincy, where they are causing "moderate" delays into town.
And it is, of course, an inbound train.
The T is reporting "minor" delays in both directions due to an inbound Red Line train that made North Quincy its final destination around 9:40 a.m.
Transit Police have released photos of a man they say "engaged in an a lewd act" on a Red Line train between Alewife and Davis around 8:50 p.m. on Dec. 30.
He's described as white, 25 to 35, clean shaven and 5'10" to 6' with a medium build.
If you know a guy who can't keep it zipped, contact Transit Police at 617-222-1050, or send an anonymous tip to 873873.
The T advises there are "moderate" delays on the Red Line towards Alewife due to an unspecified track issue at Central.
It's buses between Ashmont and JFK/UMass because of track ish at Savin Hill.
There's a train waiting for a pine box northbound on the Ashmont branch and some unspecified issue causing delays southbound on both branches. In other words, it's a Monday.
UPDATE, 11:40 a.m. A Red Line train exhaled its last at Andrew and now the T reports "severe" delays.
Yes, it was return of the signal problems from hell on the Braintree branch this morning.
But don't feel so smug, Orange Line riders - one of your trains bought the farm near Sullivan Square, causing delays from there and Oak Grove.
Around 6:25 a.m. a train needed to be taken out back and shot at Andrew. Inbound, of course.
An Alewife-bound Red Line train developed some electrical issues shortly after 6 p.m. and that meant smoke at Central Square, so the train was taken out of service.
Around the same time, some young women got into a bit of a fight on the outbound platform at Chinatown just as a train was pulling in. The train was halted so police could clear up the affray, but, of course, that halted all the trains behind it.
Reporters at WGBH perform songs about the Red Line.
Yes, it's another commute with signal problems at Braintee on the Red Line. However, all trains are operating with drivers.
WBZ reports the driver of the runaway train used a cord to tie down the speed-control lever to bypass the "dead-man's switch" feature before getting out of the train to flip the switch that would let the train travel through red signals - the ones that had been plaguing the Red Line in Braintree all week. Oops: He didn't set the train's brakes first.
WBUR reports Gov. Charlie Baker called the untended ride "an isolated incident" that resulted when "a single individual made multiple errors."