Yeah it was orphaned by f2pool.
F2pool's block was 5s later than the same height solo block.
[2015-11-11 14:00:48.440+00] 0000000000000000045792b02a12ecf0767d50d392471a3fded2371d56ab7b8a recv'd, size 998146 with 111285 bytes on the wire
[2015-11-11 14:00:53.293+00] 000000000000000008f0667bc0b60726ea2035d1bc6ab1910f81f2ed19d8741e recv'd, size 999907 with 954717 bytes on the wire
But f2pool confirmed their own block and thus, since it is the next found block that decides the orphan, in this case f2 pushed out the earlier solo block and orphaned it.
At this point in time f2pool has 8 of the last 10 blocks ...
It's somewhat very similar to how a 51% attack works because f2 is so big.
51% means it's expected over time to keep winning races, but with a lower than 51%, but still high % of the network, you can do the same for a short period of time if luck is on your side.