Why using [n] on a Django QuerySet can be unsafe?

What if I told you that the following way of taking the second object from a Django QuerySet might be unreliable and can lead to non-deterministic failures under some circumstances? second_service = Service.objects.filter(service_type="L3Connection")[1]