Southern Rail first reported the incident, at 10.50am, on Saturday (March 21). The issue was fixed by midday but reoccurred around two hours later. Trains which run between the two Sussex stations ...