issues parsing output

[vid]

{ traceID: 'eltiempo.com@1418439867852',
now: Fri Dec 12 2014 22:04:53 GMT-0500 (EST),
host: 'eltiempo.com',
data: ' 5 206.223.124.147 40.878 ms',
buffer: ' 1 192.168.0.1 0.994 ms 0.444 ms 0.449 ms 0.426 ms\n 2 * * * *\n 3 10.6.0.157 40.233 ms 106.772 ms 62.710 ms *\n 4 10.5.128.78 39.844 ms\n 10.5.128.98 40.578 ms 43.361 ms 42.018 ms\n',
hops:
[ { '10.6.0.157': [Object] },
{ '10.6.0.157': [Object] },
{ '10.5.128.78': [Object] },
{ '40.578': [Object] } ] } Fri Dec 12 2014 22:04:53 GMT-0500 (EST)

Note that 40.578 is not an ip address but a latency time. I believe that this is occurring due to incorrect exclusion of multiple routers at same hop. in the precious example, hop 4 (10.5.128.78 and 10.5.128.98)

[vid]

A few details
Hops seem to be parsed correctly in this second case, but they are not organized properly in the object that is used to submit the data to the IXmaps server. See for example the repetition of ip 10.6.0.157

{ traceID: 'eltiempo.com@1418444312504',
now: Fri Dec 12 2014 23:19:08 GMT-0500 (EST),
host: 'eltiempo.com',
data: ' 40.811 ms',
buffer: ' 1 192.168.0.1 3.081 ms 0.462 ms 0.851 ms 0.446 ms\n 2 * * * *\n 3 10.6.0.157 39.422 ms 39.413 ms 40.208 ms 47.178 ms\n 4 * 10.5.128.98 40.068 ms 39.345 ms 39.930 ms\n 5 * 206.223.124.147 39.071 ms 40.362 ms 40.347 ms\n 6 * 201.234.65.134 40.894 ms 41.081 ms 41.836 ms\n 7 200.41.9.39 42.619 ms',
hops:
[ { '10.6.0.157': [Object] },
{ '10.6.0.157': [Object] },
{ '10.6.0.157': [Object] },
{ '10.6.0.157': [Object] },
{ '10.6.0.157': [Object] } ] } Fri Dec 12 2014 23:19:08 GMT-0500 (EST)

!!!
Note: that the buffer is correct, and consistent with the results obtained with the raw traceroute and paris-traceroute. However, the array of hops used to submit data to the server has wrong order and also missing routers.