Could it be that your event breaks work fine at 10,11 or 12 o'clock?
Then the problem might be in your TIME_FORMAT , and most of the times these things happen (improper event breaking) is when splunk fails to parse timestamps.
You define your TIME_FORMAT with %I for the hour portion (uppercase "i"), which means that values from 01 .. 12 are valid.
I believe that changing to %l (lowercase "L") instead might do the trick, since this means hours from 1 .. 12, i.e. without the leading zero.
see www.strftime.net
Hope this helps,
/K
PS. The reason that numbers like 1432712121 get parsed as timestamps, is that splunk, when failing to detect a proper timestamp according to your configuration may revert to default auto-detecting behaviour, and a numeric string of this size and value can be interpreted as an epoch timestamp (around May 27 2015).
... View more