October 9–15, 2026 brought 51 unplanned MTA Long Island Rail Road service-alert threads, according to the MTA LIRR service alert feed as recorded by Long Island Traffic. The previous four weeks averaged 61.5 unplanned alert threads per week by the same measure.
No suspension-level alerts appeared in the feed that week. Of the 51 threads, 4 reached cancellation level and 45 reached delay level, with 2 classified as other, the MTA LIRR alert feed recorded by Long Island Traffic shows.
Oyster Bay, Montauk and Port Jefferson led branch alert counts
The Oyster Bay branch logged 13 unplanned alert threads for the week, the most of any branch in the feed. Montauk and Port Jefferson each recorded 10, followed by Babylon with 6 and Ronkonkoma with 4, according to the MTA LIRR alert feed as recorded by Long Island Traffic.
Unplanned alert threads by branch (MTA route in the alert)
| Branch | Alert threads | Suspensions | Cancellations |
|---|---|---|---|
| Oyster Bay | 13 | 0 | 1 |
| Montauk | 10 | 0 | 2 |
| Port Jefferson | 10 | 0 | 1 |
| Babylon | 6 | 0 | 0 |
| Ronkonkoma | 4 | 0 | 0 |
| Hempstead | 3 | 0 | 0 |
| Far Rockaway | 2 | 0 | 0 |
| Port Washington | 2 | 0 | 0 |
| Long Beach | 1 | 0 | 0 |
Cancellations were concentrated on Montauk and Oyster Bay
Among the 4 cancellation-level threads recorded that week, Montauk carried 2 and Oyster Bay carried 1, with Port Jefferson also recording 1, the MTA LIRR alert feed as recorded by Long Island Traffic shows. No branch recorded a suspension.
Equipment problems named most often as cause
Of the 51 unplanned threads, 23 named an equipment or mechanical problem and 5 named a signal or switch problem, according to the MTA LIRR alert feed as recorded by Long Island Traffic. Police, medical or emergency activity was cited in 1 thread. In 22 threads, no cause was stated in the MTA’s alert text.
Cause named in the alert text
| Cause (from MTA wording) | Alert threads |
|---|---|
| Equipment or mechanical problem | 23 |
| Not stated in the alert | 22 |
| Signal or switch problem | 5 |
| Police, medical or emergency activity | 1 |
This week against the prior four
The 51 threads recorded October 9–15 compare with 54 the week of October 2–8, 71 the week of September 25–October 1, 53 the week of September 18–24, and 68 the week of September 11–17, all per the MTA LIRR alert feed as recorded by Long Island Traffic.
Unplanned LIRR alert threads by week
| Week (ET) | Alert threads | With a suspension | With a cancellation |
|---|---|---|---|
| October 9–15, 2026 | 51 | 0 | 4 |
| October 2–8, 2026 | 54 | 1 | 9 |
| September 25–October 1, 2026 | 71 | 3 | 6 |
| September 18–24, 2026 | 53 | 0 | 9 |
| September 11–17, 2026 | 68 | 1 | 8 |
Rush-window alerts and planned-work notices
The MTA LIRR alert feed as recorded by Long Island Traffic shows 19 of the 51 unplanned threads were first seen during weekday-style rush windows — defined as 6–9:59 a.m. or 4–7:59 p.m. Eastern time on any day. Separately, the feed carried 6 planned-work notices the same week, counted apart from the unplanned total.
Riders can check live LIRR status for current service conditions.
How we measured this
- Records: every LIRR alert LIT stored from the MTA’s real-time alert feed between 12:00 a.m. October 9 and 11:59 p.m. October 15 (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.