The problem surfaces on list views with the option enabled, and/or when using the tribehiderecurrence query parameter. Here’s the incorrect SQL being outputted https://gist.github.com/neverarriving/4ef72e49536732a375ea
… When an event is repeated the query incorrectly grabs whichever end date it wants rather than the first one (Like the start date), which results in incorrect ordering.
It surfaces on all views, I was able to confirm the problem at the SQL level using the Query Monitor plugin.