From November 12–18, 2026, LIRR riders saw 93 unplanned service-alert threads, according to the MTA’s LIRR service alert feed as recorded by Long Island Traffic. That compares with an average of 57 unplanned threads a week over the previous four weeks, the same records show.
Delay wording topped 77 of those threads, and 13 carried cancellation wording, according to the MTA feed records. None reached suspension wording, the records show. Equipment or mechanical problems were the cause named in 34 threads, the MTA’s alert text shows.
For current conditions, check live LIRR status.
93 threads was the highest weekly count in five weeks of records
The 93 unplanned threads for November 12–18, 2026, are the highest weekly count in the five weeks shown below, according to MTA feed records stored by Long Island Traffic.
The week before, November 5–11, 2026, had 75 threads, the records show. October 29–November 4, 2026, had 48, and that week also carried the single suspension in the table, according to the same records.
Cancellations also rose in the table: 13 threads carried cancellation wording November 12–18, compared with 8 in the week of November 5–11, according to the MTA feed records.
Unplanned LIRR alert threads by week
| Week (ET) | Alert threads | With a suspension | With a cancellation |
|---|---|---|---|
| November 12–18, 2026 | 93 | 0 | 13 |
| November 5–11, 2026 | 75 | 0 | 8 |
| October 29–November 4, 2026 | 48 | 1 | 3 |
| October 22–28, 2026 | 58 | 0 | 5 |
| October 15–21, 2026 | 47 | 0 | 5 |
Delays drove 77 threads, with 13 cancellations and no suspensions
Of the 93 unplanned threads, 77 had delay as their most serious wording, according to the MTA feed as recorded by Long Island Traffic. Another 13 reached cancellation wording, and 3 fell into an “other” category, the records show. No thread reached suspension wording during the week, according to the same records.
The feed also carried 4 planned-work notices the same week, according to MTA feed records stored by Long Island Traffic. Those notices are counted separately from the 93 unplanned threads.
60 threads were first seen during rush windows
Long Island Traffic first saw 60 of the unplanned threads during weekday-style rush windows on any day, according to its records of the MTA feed. Those “first seen” times are Long Island Traffic’s polling times, not the MTA’s posting times.
Ronkonkoma Branch carried 17 threads, the most of any branch
Ronkonkoma Branch led the branch table with 17 unplanned alert threads, according to the MTA route listed in each alert as recorded by Long Island Traffic. Babylon and Port Jefferson branches each had 15, and Montauk Branch had 13, the records show.
Babylon Branch and City Terminal Zone each carried 3 threads with cancellation wording, according to the same records. Port Jefferson Branch had 2 cancellation threads.
Hempstead and Far Rockaway branches each had 6 threads, while Port Washington and West Hempstead branches each had 2, the MTA feed records show. No branch had a suspension, according to the same records.
Unplanned alert threads by branch (MTA route in the alert)
| Branch | Alert threads | Suspensions | Cancellations |
|---|---|---|---|
| Ronkonkoma | 17 | 0 | 1 |
| Babylon | 15 | 0 | 3 |
| Port Jefferson | 15 | 0 | 2 |
| Montauk | 13 | 0 | 1 |
| City Terminal Zone | 8 | 0 | 3 |
| Oyster Bay | 8 | 0 | 1 |
| Hempstead | 6 | 0 | 0 |
| Far Rockaway | 6 | 0 | 1 |
| Port Washington | 2 | 0 | 0 |
| West Hempstead | 2 | 0 | 0 |
| Multiple or unspecified | 1 | 0 | 1 |
Equipment problems were named in 34 threads, and 29 named no cause
Equipment or mechanical problems were named in 34 unplanned threads, according to the MTA’s own alert wording as recorded by Long Island Traffic. Another 29 threads did not state a cause, the records show.
Signal or switch problems appeared in 14 threads, and track condition or work appeared in 12, according to the MTA alert text. Weather, trees or flooding were named in 3 threads, and police, medical or emergency activity in 1, the same records show.
Cause named in the alert text
| Cause (from MTA wording) | Alert threads |
|---|---|
| Equipment or mechanical problem | 34 |
| Not stated in the alert | 29 |
| Signal or switch problem | 14 |
| Track condition or work | 12 |
| Weather, trees or flooding | 3 |
| Police, medical or emergency activity | 1 |
How we measured this
- Records: every LIRR alert LIT stored from the MTA’s real-time alert feed between 12:00 a.m. November 12 and 11:59 p.m. November 18 (Eastern).
- An alert thread is one MTA alert and all of its updates. Threads are classed by the most serious wording in any update: suspension, then cancellation, then delay.
- Branch comes from the MTA route in the alert; causes come from keywords in MTA’s own text. Planned-work notices are counted separately.
- Comparison weeks are the four 7-day periods immediately before this one.
Limitations
- This is not an on-time-performance measure. One alert can cover one late train or a whole branch, and the MTA publishes on-time performance separately.
- LIT polls the feed on a schedule, so a short alert posted and withdrawn between polls may be missing, and “first seen” times are LIT’s, not the MTA’s.
- Cause categories rely on the MTA’s wording; alerts that do not name a cause are listed as not stated.