Trackside
MARC

MARC — October 2026

Every service problem and tracking or data issue Trackside counted this month. Repeats on the same train are grouped, with the affected dates.

Service problems

Possibly cancelled (no train was ever tracked on it)

  • Train 429 (Oct 22): was possibly cancelled (no train was ever tracked on it) — MARC posted an alert covering it. Train 429 →

Cancelled

  • Train 443 — 2 days (Oct 2, Oct 23): was cancelled — MARC posted an alert covering each of them. Train 443 →
  • Train 447 — 2 days (Oct 2, Oct 8): was cancelled — MARC posted an alert covering each of them. Train 447 →
  • Train 413 (Oct 19): was cancelled — MARC posted an alert covering it. Train 413 →
  • Train 414 (Oct 22): was cancelled — MARC posted an alert covering it. Train 414 →
  • Train 424 (Oct 14): was cancelled — MARC posted an alert covering it. Train 424 →
  • Train 426 (Oct 2): was cancelled — MARC posted an alert covering it. Train 426 →
  • Train 439 (Oct 14): was cancelled — MARC posted an alert covering it. Train 439 →
  • Train 445 (Oct 2): was cancelled — MARC posted an alert covering it. Train 445 →
  • Train 446 (Oct 8): was cancelled — MARC posted an alert covering it. Train 446 →
  • Train 497 (Oct 17): was cancelled — MARC posted an alert covering it. Train 497 →
  • Train 544 (Oct 23): was cancelled — MARC posted an alert covering it. Train 544 →
  • Train 642 (Oct 2): was cancelled — MARC posted an alert covering it. Train 642 →
  • Train 696 (Oct 17): was cancelled — MARC posted an alert covering it. Train 696 →
  • Train 858 (Oct 16): was cancelled — MARC posted an alert covering it. Train 858 →
  • Train 874 (Oct 20): was cancelled — MARC posted an alert covering it. Train 874 →
  • Train 879 (Oct 19): was cancelled — MARC posted an alert covering it. Train 879 →

Cut short before its last stop

  • Train 859 — 2 days (Oct 16, Oct 27): was cut short before its last stop — MARC posted an alert covering each of them. Train 859 →
  • Train 544 (Oct 2): was cut short before its last stop — MARC posted an alert covering it. Train 544 →
  • Train 642 (Oct 29): was cut short before its last stop — MARC posted an alert covering it. Train 642 →
  • Train 857 (Oct 16): was cut short before its last stop — MARC posted an alert covering it. Train 857 →

Left the first station 20+ min late

  • Train 860 — 3 days (Oct 6, Oct 27–28): left 20+ min late — MARC posted an alert covering each of them. Train 860 →
  • Train 448 — 2 days (Oct 26, Oct 29): left 20+ min late — MARC posted an alert covering each of them. Train 448 →
  • Train 449 — 2 days (Oct 2, Oct 8): left 30+ min late — MARC posted an alert covering each of them. Train 449 →
  • Train 455 — 2 days (Oct 21, Oct 27): left 20+ min late — MARC posted an alert covering each of them. Train 455 →
  • Train 426 (Oct 14): left 20+ min late — MARC posted an alert covering it. Train 426 →
  • Train 430 (Oct 2): left 30+ min late — MARC posted an alert covering it. Train 430 →
  • Train 438 (Oct 2): left 30+ min late — MARC posted an alert covering it. Train 438 →
  • Train 440 (Oct 2): left 20+ min late — we found no MARC alert naming this train. Train 440 →
  • Train 446 (Oct 27): left 20+ min late — MARC posted an alert covering it. Train 446 →
  • Train 452 (Oct 2): left 30+ min late — MARC posted an alert covering it. Train 452 →
  • Train 536 (Oct 2): left 20+ min late — MARC posted an alert covering it. Train 536 →
  • Train 548 (Oct 26): left 20+ min late — MARC posted an alert covering it. Train 548 →
  • Train 579 (Oct 2): left 30+ min late — MARC posted an alert covering it. Train 579 →
  • Train 634 (Oct 2): left 30+ min late — MARC posted an alert covering it. Train 634 →
  • Train 859 (Oct 28): left 30+ min late — MARC posted an alert covering it. Train 859 →
  • Train 873 (Oct 15): left 20+ min late — MARC posted an alert covering it. Train 873 →
  • Train 893 (Oct 2): left 20+ min late — MARC posted an alert covering it. Train 893 →
  • Train 895 (Oct 15): left 20+ min late — MARC posted an alert covering it. Train 895 →

Tracking and data issues

Tracking stayed active after arrival

  • Train 880 — 4 days (Oct 5, Oct 8, Oct 15, Oct 27): tracking stayed active after the train arrived. Train 880 →
  • Train 537 (Oct 23): tracking stayed active for 47 min after it arrived at Union Station, the vehicle moved away while the trip was still active, and an arrival was published 47 min later than the train actually arrived. Train 537 →
  • Train 892 (Oct 19): tracking stayed active for 9 min after it arrived at Union Station, the vehicle moved away while the trip was still active, and an arrival was published 27 min later than the train actually arrived. Train 892 →

Tracking ended before arrival

  • Train 851 — 6 days (Oct 6–8, Oct 21, Oct 23, Oct 27): the trip disappeared from tracking before the train reached its final stop. Train 851 →
  • Train 698 — 5 days (Oct 3, Oct 10, Oct 17, Oct 24, Oct 31): the trip disappeared from tracking before the train reached its final stop. Train 698 →
  • Train 878 — 5 days (Oct 8, Oct 14, Oct 16, Oct 19, Oct 22): the trip disappeared from tracking before the train reached its final stop. Train 878 →
  • Train 407 — 3 days (Oct 15, Oct 21–22): the trip disappeared from tracking before the train reached its final stop. Train 407 →
  • Train 517 — 3 days (Oct 1, Oct 15–16): the trip disappeared from tracking before the train reached its final stop. Train 517 →
  • Train 685 — 3 days (Oct 3, Oct 17, Oct 24): the trip disappeared from tracking before the train reached its final stop. Train 685 →
  • Train 845 — 3 days (Oct 5, Oct 20, Oct 23): the trip disappeared from tracking before the train reached its final stop. Train 845 →
  • Train 849 — 3 days (Oct 23, Oct 27–28): the trip disappeared from tracking before the train reached its final stop. Train 849 →
  • Train 401 — 2 days (Oct 8, Oct 21): the trip disappeared from tracking before the train reached its final stop. Train 401 →
  • Train 403 — 2 days (Oct 7–8): the trip disappeared from tracking before the train reached its final stop. Train 403 →
  • Train 415 — 2 days (Oct 1–2): the trip disappeared from tracking before the train reached its final stop. Train 415 →
  • Train 511 — 2 days (Oct 7, Oct 23): the trip disappeared from tracking before the train reached its final stop. Train 511 →
  • Train 579 — 2 days (Oct 5–6): the trip disappeared from tracking before the train reached its final stop. Train 579 →
  • Train 847 — 2 days (Oct 12, Oct 20): the trip disappeared from tracking before the train reached its final stop. Train 847 →
  • Train 880 — 2 days (Oct 19, Oct 22): the trip disappeared from tracking before the train reached its final stop. Train 880 →
  • Train 894 — 2 days (Oct 12, Oct 15): the trip disappeared from tracking before the train reached its final stop. Train 894 →
  • Train 409 (Oct 23): the trip disappeared from tracking about 0.9 mi short of Union Station, with its arrival still shown 16 min away. Train 409 →
  • Train 413 (Oct 2): the trip disappeared from tracking about 0.8 mi short of Union Station, with its arrival still shown 6 min away. Train 413 →
  • Train 443 (Oct 5): the trip disappeared from tracking about 0.9 mi short of Union Station, with its arrival still shown 14 min away. Train 443 →
  • Train 445 (Oct 6): the trip disappeared from tracking about 1.9 mi short of Union Station, with its arrival still shown 17 min away. Train 445 →
  • Train 446 (Oct 5): the trip disappeared from tracking about 1.3 mi short of Baltimore Penn Station, with its arrival still shown 16 min away. Train 446 →
  • Train 447 (Oct 6): the trip disappeared from tracking about 2.5 mi short of Union Station, with its arrival still shown 12 min away. Train 447 →
  • Train 452 (Oct 2): the trip disappeared from tracking about 26.3 mi short of Baltimore Penn Station, with its arrival still shown 43 min away. Train 452 →
  • Train 492 (Oct 31): the trip disappeared from tracking about 1.3 mi short of Baltimore Penn Station, with its arrival still shown 9 min away. Train 492 →
  • Train 497 (Oct 31): the trip disappeared from tracking about 0.9 mi short of Union Station, with its arrival still shown 9 min away. Train 497 →
  • Train 634 (Oct 6): the trip disappeared from tracking about 5.2 mi short of Martin State Airport, with its arrival still shown 14 min away. Train 634 →
  • Train 841 (Oct 20): the trip disappeared from tracking about 1.2 mi short of Union Station, with its arrival still shown 5 min away. Train 841 →
  • Train 843 (Oct 8): the trip disappeared from tracking about 1.6 mi short of Union Station, with its arrival still shown 6 min away. Train 843 →
  • Train 858 (Oct 27): the trip disappeared from tracking about 16 mi short of Camden Station, with its arrival still shown 36 min away. Train 858 →
  • Train 870 (Oct 22): the trip disappeared from tracking about 1.4 mi short of Union Station, with its arrival still shown 14 min away. Train 870 →
  • Train 874 (Oct 29): the trip disappeared from tracking about 1.9 mi short of Union Station, with its arrival still shown 18 min away. Train 874 →
  • Train 890 (Oct 29): the trip disappeared from tracking about 0.7 mi short of Union Station, with its arrival still shown 10 min away. Train 890 →

No position published

  • Train 426 (Oct 22): no position was published for 52 min while the train covered about 35.5 mi. Train 426 →
  • Train 446 (Oct 23): no position was published for 17 min while the train covered about 10.4 mi. Train 446 →
  • Train 520 (Oct 12): no position was published for 26 min while the train covered about 18.2 mi. Train 520 →
  • Train 860 (Oct 16): no position was published for 38 min while the train covered about 25.5 mi. Train 860 →
  • Train 871 (Oct 16): no position was published for 28 min while the train covered about 7.8 mi. Train 871 →

Position published, no trip data

  • Train 453 (Oct 2): no trip data was published for the train, although its position showed it running about 29 mi along its route. Train 453 →

Positions in two places at once

  • Train 426 (Oct 15): the trip showed positions in two places at once, about 10.1 mi apart. Train 426 →
  • Train 440 (Oct 12): the trip showed positions in two places at once, about 15.3 mi apart. Train 440 →
  • Train 448 (Oct 2): the trip showed positions in two places at once, about 35.1 mi apart. Train 448 →
  • Train 454 (Oct 21): the trip showed positions in two places at once, about 35 mi apart. Train 454 →
  • Train 520 (Oct 29): the trip showed positions in two places at once, about 7.2 mi apart. Train 520 →
  • Train 532 (Oct 5): the trip showed positions in two places at once, about 7.7 mi apart. Train 532 →
  • Train 612 (Oct 12): the trip showed positions in two places at once, about 9.6 mi apart. Train 612 →

Predicted times stopped updating

  • Train 853 — 2 days (Oct 2, Oct 5): predicted times stopped updating for a stretch of the trip. Train 853 →
  • Train 440 (Oct 29): predicted times stopped updating for 25 min, and the time shown for Baltimore Penn Station passed before the train got there. Train 440 →
  • Train 536 (Oct 29): predicted times stopped updating for 57 min while the train moved about 0.4 mi, and the time shown for Martin State Airport passed before the train got there. Train 536 →
  • Train 537 (Oct 2): predicted times stopped updating for 35 min, and the time shown for New Carrollton passed before the train got there. Train 537 →
  • Train 844 (Oct 8): predicted times stopped updating for 15 min, and the time shown for Camden Station passed before the train got there. Train 844 →
  • Train 878 (Oct 22): predicted times stopped updating for 15 min while the train moved about 0.2 mi, and the time shown for Harpers Ferry passed before the train got there. Train 878 →
  • Train 883 (Oct 2): predicted times stopped updating for 19 min while the train moved about 0.5 mi, and the time shown for Point of Rocks passed before the train got there. Train 883 →

Tracking and data issues describe what the feed showed, not who caused it. See About for methodology.

← All months · MARC