Rancher API timestamp bug?

I am creating a websocket connection using ws4py (python) to communicate with the API and get container stats continuously

While printing the timestamp that i got i observed that the timezone suddenly shifted from the local timezone to UTC. Is this a bug? Is there any workaround in the API itself or should i handle it on the client side?

here is what i got:

2016-11-02T01:04:03.96128142+08:00

2016-11-02T01:04:05.012862114+08:00

2016-11-02T01:04:06.745380191+08:00

2016-11-02T01:04:07.778539501+08:00

2016-11-01T17:04:09.252280476Z <-- UTC suddenly appears!

2016-11-01T17:04:10.253606253Z

2016-11-01T17:04:11.254846748Z