Honestly, with that many failed requests, I'd expect that something shut down your test, or that there's a significant configuration issue with the server. If you're running the test from a remote machine over the network, I wouldn't be surprised if some network security software decided the test was an attack and stopped responding to your client machine for the remainder of the test.
On the other hand, since your previous test was returning nothing more than a 302, the response times which seemed OK when receiving content do seem more problematic. I'm not sure, though, what kind of failure would result in the longest request taking only 262ms, unless it's only counting the successful responses in that last listing.
