RESOLVED - Tifia cancelled over 4000 EUR in profits

AsstModerator said:
Of the 471 cancelled trades, what was the close date on the oldest trade cancelled?
Click to expand...

Of the 471 cancelled trades, the open date on the oldest trade cancelled was 2017.11.28 19:44:10 and the close date was 2017.11.28 19:44:13.
The open date on the latest trade cancelled was 2017.11.28 20:25:10 and the close date was 2017.11.28 20:25:11.
 
Tifia FX said:
Of the 471 cancelled trades, the open date on the oldest trade cancelled was 2017.11.28 19:44:10 and the close date was 2017.11.28 19:44:13.
The open date on the latest trade cancelled was 2017.11.28 20:25:10 and the close date was 2017.11.28 20:25:11.
Click to expand...

So what Tifia is saying the were not able to hedge any trades within that close to 1hr period. Doesn't this look odd? On top of that there was an attempt to block my account due to AML and when that didn't work as I am not doing anything even remotely related to money laundering they say they couldn't hedge.
 
chitak said:
So what Tifia is saying the were not able to hedge any trades within that close to 1hr period. Doesn't this look odd? On top of that there was an attempt to block my account due to AML and when that didn't work as I am not doing anything even remotely related to money laundering they say they couldn't hedge.
Click to expand...
Dear sir,

Your account was blocked as our Service for Trade Operations had conducted an internal investigation and found out that logins to your account 6026336 МТ4 had been from different IP addresses and CIDs. It can be normal though if you’ve been using different devices.
Logins to account 6026336 from 09.2017 to 12.2017

2017.09.07 23:54:47.034 185.28.165.107 '6026336': login (1090, client, dc: 0, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 35 ms)

2017.11.09 03:40:13.133 34.216.27.240 '6026336': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 115 ms)

2017.11.09 17:57:26.875 54.70.15.135 '6026336': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 123 ms)

2017.11.08 16:36:31.746 34.216.27.240 '6026336': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 117 ms)

2017.09.06 22:49:05.888 5.10.18.43 '6026336': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 23 ms)

However, the same IPs and CIDs were used to log in to other clients’ accounts.

login 6026340:

2017.10.02 05:12:16.228 185.28.165.107 '6026340': login (1090, client, dc: 0, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 33 ms)
2017.11.08 02:53:22.786 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 513 ms)
2017.10.26 17:16:49.010 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 426 ms)
2017.10.05 01:19:48.096 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 215 ms)
2017.11.15 03:12:23.046 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 214 ms)
2017.11.24 00:11:01.431 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 212 ms)
2017.10.25 04:00:26.969 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 205 ms)
2017.10.12 00:46:37.440 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 199 ms)
2017.11.22 17:51:23.460 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 195 ms)
2017.11.23 12:35:09.345 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 188 ms)
2017.11.15 03:12:13.233 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 185 ms)
2017.10.11 03:34:23.496 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 179 ms)
2017.11.30 09:49:19.807 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 176 ms)
2017.10.04 01:09:43.906 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 173 ms)
2017.11.22 16:58:57.444 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 171 ms)
2017.10.11 03:07:03.121 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 171 ms)
2017.11.27 01:33:47.863 185.28.165.107 '6026340': login (1090, client, dc: 0, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 8 ms)
2017.10.29 23:06:18.223 185.28.165.107 '6026340': login (1090, client, dc: 0, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 6 ms)
2017.10.09 05:38:17.014 185.28.165.107 '6026340': login (1090, client, dc: 0, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 6 ms)
2017.11.20 00:43:33.453 185.28.165.107 '6026340': login (1090, client, dc: 0, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 54 ms)
2017.11.27 01:33:45.009 185.28.165.107 '6026340': login (1090, client, dc: 0, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 51 ms)

logins to 6003650:
2017.09.19 16:16:42.699 54.71.183.203 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 102 ms)
2017.09.01 00:35:15.418 54.70.103.16 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 106 ms)
2017.10.09 03:45:29.394 54.148.72.67 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 106 ms)
2017.09.19 07:04:57.475 34.212.11.123 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 109 ms)
2017.10.25 23:05:35.839 34.211.57.140 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 109 ms)
2017.10.11 14:56:52.600 34.214.237.247 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 110 ms)
2017.10.02 10:17:36.602 34.215.105.141 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 111 ms)
2017.09.22 07:19:32.125 35.162.33.70 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 112 ms)
2017.09.25 04:42:14.728 35.163.25.232 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 112 ms)
2017.10.27 01:14:09.802 52.42.171.180 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 113 ms)
2017.10.30 06:43:42.556 34.213.116.69 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 113 ms)
2017.10.26 19:12:16.545 52.42.171.180 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 114 ms)
2017.10.19 16:16:32.316 35.161.203.79 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 115 ms)
2017.10.25 03:40:49.838 34.212.119.164 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 116 ms)
2017.10.19 07:01:04.168 52.42.50.168 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 117 ms)
2017.10.02 15:43:17.618 52.11.147.192 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 118 ms)
2017.10.03 01:38:42.055 52.11.147.192 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 119 ms)
2017.10.03 12:54:54.687 52.11.147.192 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 119 ms)
2017.10.24 03:42:54.091 52.24.201.249 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 121 ms)
2017.09.08 22:02:46.701 34.214.68.16 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 122 ms)
2017.09.18 09:35:36.273 52.11.232.210 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 122 ms)
2017.09.25 09:12:23.297 35.163.25.232 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 122 ms)
2017.10.03 12:54:34.158 52.11.147.192 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 122 ms)
2017.10.04 19:48:21.852 34.215.155.242 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 122 ms)
2017.10.19 07:00:54.543 52.42.50.168 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 122 ms)
2017.10.31 10:38:28.729 52.11.107.237 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 122 ms)

logins to 6012846:

2017.10.23 09:18:43.589 52.89.164.67 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 106 ms)
2017.10.25 19:27:32.346 34.211.57.140 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 107 ms)
2017.11.09 23:34:50.175 54.70.15.135 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 107 ms)
2017.11.29 20:37:38.414 54.68.118.170 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 107 ms)
2017.11.30 02:50:49.065 54.68.118.170 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 107 ms)
2017.10.13 02:11:41.096 54.68.191.103 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 108 ms)
2017.11.13 21:55:28.686 35.164.248.57 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 108 ms)
2017.10.31 06:40:40.647 52.11.107.237 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 111 ms)
2017.09.01 13:19:11.059 54.70.103.16 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 112 ms)
2017.11.01 10:05:43.227 54.191.102.163 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 112 ms)
2017.11.20 11:09:36.061 34.216.112.43 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 112 ms)
2017.10.03 19:08:31.724 34.213.158.209 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 113 ms)
2017.11.29 02:34:56.248 35.161.102.120 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 113 ms)

logins to 6019697:

2017.11.07 13:28:08.708 35.167.24.135 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 129 ms)
2017.11.08 23:48:48.001 34.216.27.240 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 129 ms)
2017.11.16 00:40:52.334 52.32.13.28 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 129 ms)
2017.11.17 03:02:21.388 52.42.136.235 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 129 ms)
2017.10.31 07:39:04.632 52.11.107.237 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 130 ms)
2017.11.07 13:28:03.373 35.167.24.135 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 130 ms)
2017.11.09 10:24:32.548 34.216.27.240 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 130 ms)
2017.11.15 19:07:06.501 52.32.13.28 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 130 ms)
2017.11.28 21:21:04.403 35.161.102.120 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 130 ms)
2017.11.03 05:07:01.735 34.210.232.218 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 131 ms)
2017.11.17 00:59:27.239 52.42.136.235 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 131 ms)
2017.10.30 19:53:53.520 52.11.107.237 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 132 ms)
2017.10.27 13:47:02.574 52.42.171.180 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 133 ms)
2017.11.22 18:03:43.407 52.27.236.127 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 133 ms)
2017.10.27 23:37:57.755 52.34.173.44 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 134 ms)
2017.11.29 20:15:12.025 54.68.118.170 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 137 ms)
2017.11.10 14:37:21.183 50.112.27.187 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 138 ms)
2017.11.24 11:31:35.881 34.216.112.59 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 138 ms)
2017.10.31 09:30:36.841 52.11.107.237 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 140 ms)
2017.11.06 16:14:22.910 35.167.24.135 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 140 ms)
2017.11.15 11:22:17.645 52.33.100.200 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 142 ms)
2017.11.06 18:15:11.869 35.167.24.135 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 143 ms)
2017.11.08 02:38:46.657 52.38.111.149 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 143 ms)
2017.11.20 01:08:28.964 34.216.112.43 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 143 ms)

logins to 6023966:

2017.10.25 05:57:53.549 34.212.119.164 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.10.25 23:37:21.929 34.211.57.140 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.10.30 12:06:26.418 34.213.116.69 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.10.31 01:27:19.837 52.11.107.237 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.03 06:06:30.615 34.210.232.218 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.03 08:07:51.694 34.210.232.218 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.06 06:11:55.398 34.211.4.58 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.07 12:23:23.334 35.167.24.135 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.07 12:23:27.858 35.167.24.135 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.09 23:39:27.309 54.70.15.135 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.10 11:52:19.247 54.70.15.135 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.13 03:06:08.890 52.88.242.6 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.10.06 21:53:45.913 34.213.239.219 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 126 ms)
2017.10.19 15:08:35.093 35.161.203.79 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 127 ms)
2017.11.20 11:12:53.395 34.216.112.43 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 127 ms)
2017.10.02 15:59:21.621 52.11.147.192 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 128 ms)
2017.11.20 15:09:23.025 52.34.205.123 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 128 ms)
2017.11.27 01:27:11.919 35.167.17.155 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 128 ms)
2017.11.27 20:39:00.843 54.200.3.117 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 128 ms)
2017.11.29 16:42:52.215 54.68.118.170 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 128 ms)
2017.11.23 07:49:19.449 52.27.236.127 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 129 ms)
2017.11.23 10:14:12.706 52.27.236.127 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 129 ms)

logins to 6028144:

2017.10.24 01:09:08.110 5.10.18.43 '6028144': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 20 ms)
2017.10.24 01:01:10.437 5.10.18.43 '6028144': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 25 ms)
2017.10.24 00:59:06.339 5.10.18.43 '6028144': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 32 ms)
2017.10.24 01:08:45.318 5.10.18.43 '6028144': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 37 ms)
2017.10.13 17:27:14.763 5.10.18.43 '6028144': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 39 ms)
2017.10.13 17:26:08.167 5.10.18.43 '6028145': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 32 ms)
2017.10.24 00:55:02.854 5.10.18.43 '6028243': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 13 ms)
2017.10.24 00:58:05.483 5.10.18.43 '6028243': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 6 ms)
2017.10.04 21:59:08.151 5.10.18.43 '6028374': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 37 ms)
2017.10.24 01:13:19.473 5.10.18.43 '6029848': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 28 ms)
2017.10.24 00:55:47.267 5.10.18.43 '6029848': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 29 ms)

logins to 6026788:

2017.09.18 17:38:27.048 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 11 ms)
2017.09.15 15:07:00.178 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 15 ms)
2017.09.13 15:01:33.502 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 31 ms)
2017.09.15 15:11:44.755 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 34 ms)
2017.09.14 17:26:51.650 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 35 ms)
2017.09.13 22:23:21.828 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 36 ms)
2017.09.11 21:53:41.655 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 40 ms)
2017.09.12 15:02:14.165 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 55 ms)
2017.09.11 15:37:29.085 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 7 ms)


Pursuant to its service instructions, the AML service had therefore to request additional information to confirm your ID and establish the source of your funds.

Regarding your assertion that it’s odd not to be able to hedge trades during 41 minutes ... The thing is, the prices didn’t correspond to market ones during that whole period. They were much slower than the real prices, and your trading advisor used that fact, having opened a big number of orders at non-existing prices. The architecture of the MT4 platform allowed those trades to be executed. However, the liquidity provider was not able to process the trades with those parameters because they didn’t correspond to the market situation.

Here’s a bright example of the trades opened at non-market prices which even were not in the chart (Attachment Wrongprices.xls). (Examples of orders indicated in the screenshots are highlighted in green).

View attachment 36362

Here are some screenshots of our charts:
upload_2018-2-21_18-19-41.png


upload_2018-2-21_18-20-9.png


upload_2018-2-21_18-20-32.png


upload_2018-2-21_18-21-19.png


As we see, the difference between the prices reached 50 points at some moments, which is a huge difference and an important sign of an incorrect data flow even under Forex decentralization.

If you do not confide in our data, I suggest you compare opening prices from a free access archive of quotes at DukasСopy, one of the most competent Forex brokers.

Probably, you have some examples of prices at which the above orders were opened with other brokers at that moment of time.

Also, you mentioned you are a news trader. Could you please name some fundamental news released from 19:44:10 to 20:25:11?
 

Attachments

  • GBPAUD_s 21.02.2018.png
    GBPAUD_s 21.02.2018.png
    22.6 KB · Views: 9
  • GBPCHF_s 21.02.2018.png
    GBPCHF_s 21.02.2018.png
    23.7 KB · Views: 9
  • Intersection by IPs.txt
    17 KB · Views: 9
  • Wrongprices.png
    Wrongprices.png
    59.1 KB · Views: 9
  • GBPJPY_s 21.02.2018.png
    GBPJPY_s 21.02.2018.png
    23.4 KB · Views: 10
  • GBPNZD_s 21.02.2018.png
    GBPNZD_s 21.02.2018.png
    25.7 KB · Views: 8
Tifia FX said:
Dear sir,

Your account was blocked as our Service for Trade Operations had conducted an internal investigation and found out that logins to your account 6026336 МТ4 had been from different IP addresses and CIDs. It can be normal though if you’ve been using different devices.
Logins to account 6026336 from 09.2017 to 12.2017

2017.09.07 23:54:47.034 185.28.165.107 '6026336': login (1090, client, dc: 0, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 35 ms)

2017.11.09 03:40:13.133 34.216.27.240 '6026336': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 115 ms)

2017.11.09 17:57:26.875 54.70.15.135 '6026336': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 123 ms)

2017.11.08 16:36:31.746 34.216.27.240 '6026336': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 117 ms)

2017.09.06 22:49:05.888 5.10.18.43 '6026336': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 23 ms)

However, the same IPs and CIDs were used to log in to other clients’ accounts.

login 6026340:

2017.10.02 05:12:16.228 185.28.165.107 '6026340': login (1090, client, dc: 0, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 33 ms)
2017.11.08 02:53:22.786 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 513 ms)
2017.10.26 17:16:49.010 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 426 ms)
2017.10.05 01:19:48.096 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 215 ms)
2017.11.15 03:12:23.046 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 214 ms)
2017.11.24 00:11:01.431 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 212 ms)
2017.10.25 04:00:26.969 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 205 ms)
2017.10.12 00:46:37.440 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 199 ms)
2017.11.22 17:51:23.460 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 195 ms)
2017.11.23 12:35:09.345 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 188 ms)
2017.11.15 03:12:13.233 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 185 ms)
2017.10.11 03:34:23.496 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 179 ms)
2017.11.30 09:49:19.807 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 176 ms)
2017.10.04 01:09:43.906 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 173 ms)
2017.11.22 16:58:57.444 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 171 ms)
2017.10.11 03:07:03.121 185.28.165.107 '6026340': login (1090, client, dc: 1, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 171 ms)
2017.11.27 01:33:47.863 185.28.165.107 '6026340': login (1090, client, dc: 0, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 8 ms)
2017.10.29 23:06:18.223 185.28.165.107 '6026340': login (1090, client, dc: 0, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 6 ms)
2017.10.09 05:38:17.014 185.28.165.107 '6026340': login (1090, client, dc: 0, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 6 ms)
2017.11.20 00:43:33.453 185.28.165.107 '6026340': login (1090, client, dc: 0, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 54 ms)
2017.11.27 01:33:45.009 185.28.165.107 '6026340': login (1090, client, dc: 0, cid: c699ce3b4624b794fb4a4290bb3eccf1, ping: 51 ms)

logins to 6003650:
2017.09.19 16:16:42.699 54.71.183.203 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 102 ms)
2017.09.01 00:35:15.418 54.70.103.16 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 106 ms)
2017.10.09 03:45:29.394 54.148.72.67 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 106 ms)
2017.09.19 07:04:57.475 34.212.11.123 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 109 ms)
2017.10.25 23:05:35.839 34.211.57.140 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 109 ms)
2017.10.11 14:56:52.600 34.214.237.247 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 110 ms)
2017.10.02 10:17:36.602 34.215.105.141 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 111 ms)
2017.09.22 07:19:32.125 35.162.33.70 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 112 ms)
2017.09.25 04:42:14.728 35.163.25.232 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 112 ms)
2017.10.27 01:14:09.802 52.42.171.180 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 113 ms)
2017.10.30 06:43:42.556 34.213.116.69 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 113 ms)
2017.10.26 19:12:16.545 52.42.171.180 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 114 ms)
2017.10.19 16:16:32.316 35.161.203.79 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 115 ms)
2017.10.25 03:40:49.838 34.212.119.164 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 116 ms)
2017.10.19 07:01:04.168 52.42.50.168 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 117 ms)
2017.10.02 15:43:17.618 52.11.147.192 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 118 ms)
2017.10.03 01:38:42.055 52.11.147.192 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 119 ms)
2017.10.03 12:54:54.687 52.11.147.192 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 119 ms)
2017.10.24 03:42:54.091 52.24.201.249 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 121 ms)
2017.09.08 22:02:46.701 34.214.68.16 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 122 ms)
2017.09.18 09:35:36.273 52.11.232.210 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 122 ms)
2017.09.25 09:12:23.297 35.163.25.232 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 122 ms)
2017.10.03 12:54:34.158 52.11.147.192 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 122 ms)
2017.10.04 19:48:21.852 34.215.155.242 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 122 ms)
2017.10.19 07:00:54.543 52.42.50.168 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 122 ms)
2017.10.31 10:38:28.729 52.11.107.237 '6003650': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 122 ms)

logins to 6012846:

2017.10.23 09:18:43.589 52.89.164.67 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 106 ms)
2017.10.25 19:27:32.346 34.211.57.140 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 107 ms)
2017.11.09 23:34:50.175 54.70.15.135 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 107 ms)
2017.11.29 20:37:38.414 54.68.118.170 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 107 ms)
2017.11.30 02:50:49.065 54.68.118.170 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 107 ms)
2017.10.13 02:11:41.096 54.68.191.103 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 108 ms)
2017.11.13 21:55:28.686 35.164.248.57 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 108 ms)
2017.10.31 06:40:40.647 52.11.107.237 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 111 ms)
2017.09.01 13:19:11.059 54.70.103.16 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 112 ms)
2017.11.01 10:05:43.227 54.191.102.163 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 112 ms)
2017.11.20 11:09:36.061 34.216.112.43 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 112 ms)
2017.10.03 19:08:31.724 34.213.158.209 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 113 ms)
2017.11.29 02:34:56.248 35.161.102.120 '6012846': login (1090, client, dc: 0, cid: e04b4a6fdd0da6bba52ce4fa43853e95, ping: 113 ms)

logins to 6019697:

2017.11.07 13:28:08.708 35.167.24.135 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 129 ms)
2017.11.08 23:48:48.001 34.216.27.240 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 129 ms)
2017.11.16 00:40:52.334 52.32.13.28 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 129 ms)
2017.11.17 03:02:21.388 52.42.136.235 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 129 ms)
2017.10.31 07:39:04.632 52.11.107.237 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 130 ms)
2017.11.07 13:28:03.373 35.167.24.135 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 130 ms)
2017.11.09 10:24:32.548 34.216.27.240 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 130 ms)
2017.11.15 19:07:06.501 52.32.13.28 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 130 ms)
2017.11.28 21:21:04.403 35.161.102.120 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 130 ms)
2017.11.03 05:07:01.735 34.210.232.218 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 131 ms)
2017.11.17 00:59:27.239 52.42.136.235 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 131 ms)
2017.10.30 19:53:53.520 52.11.107.237 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 132 ms)
2017.10.27 13:47:02.574 52.42.171.180 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 133 ms)
2017.11.22 18:03:43.407 52.27.236.127 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 133 ms)
2017.10.27 23:37:57.755 52.34.173.44 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 134 ms)
2017.11.29 20:15:12.025 54.68.118.170 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 137 ms)
2017.11.10 14:37:21.183 50.112.27.187 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 138 ms)
2017.11.24 11:31:35.881 34.216.112.59 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 138 ms)
2017.10.31 09:30:36.841 52.11.107.237 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 140 ms)
2017.11.06 16:14:22.910 35.167.24.135 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 140 ms)
2017.11.15 11:22:17.645 52.33.100.200 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 142 ms)
2017.11.06 18:15:11.869 35.167.24.135 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 143 ms)
2017.11.08 02:38:46.657 52.38.111.149 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 143 ms)
2017.11.20 01:08:28.964 34.216.112.43 '6019697': login (1090, client, dc: 0, cid: e65c7288df1230b8bd185bd54b4f7b55, ping: 143 ms)

logins to 6023966:

2017.10.25 05:57:53.549 34.212.119.164 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.10.25 23:37:21.929 34.211.57.140 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.10.30 12:06:26.418 34.213.116.69 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.10.31 01:27:19.837 52.11.107.237 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.03 06:06:30.615 34.210.232.218 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.03 08:07:51.694 34.210.232.218 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.06 06:11:55.398 34.211.4.58 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.07 12:23:23.334 35.167.24.135 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.07 12:23:27.858 35.167.24.135 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.09 23:39:27.309 54.70.15.135 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.10 11:52:19.247 54.70.15.135 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.11.13 03:06:08.890 52.88.242.6 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 125 ms)
2017.10.06 21:53:45.913 34.213.239.219 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 126 ms)
2017.10.19 15:08:35.093 35.161.203.79 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 127 ms)
2017.11.20 11:12:53.395 34.216.112.43 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 127 ms)
2017.10.02 15:59:21.621 52.11.147.192 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 128 ms)
2017.11.20 15:09:23.025 52.34.205.123 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 128 ms)
2017.11.27 01:27:11.919 35.167.17.155 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 128 ms)
2017.11.27 20:39:00.843 54.200.3.117 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 128 ms)
2017.11.29 16:42:52.215 54.68.118.170 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 128 ms)
2017.11.23 07:49:19.449 52.27.236.127 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 129 ms)
2017.11.23 10:14:12.706 52.27.236.127 '6023966': login (1090, client, dc: 0, cid: e7d558c470e6f9bff4526a0a91a60bb4, ping: 129 ms)

logins to 6028144:

2017.10.24 01:09:08.110 5.10.18.43 '6028144': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 20 ms)
2017.10.24 01:01:10.437 5.10.18.43 '6028144': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 25 ms)
2017.10.24 00:59:06.339 5.10.18.43 '6028144': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 32 ms)
2017.10.24 01:08:45.318 5.10.18.43 '6028144': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 37 ms)
2017.10.13 17:27:14.763 5.10.18.43 '6028144': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 39 ms)
2017.10.13 17:26:08.167 5.10.18.43 '6028145': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 32 ms)
2017.10.24 00:55:02.854 5.10.18.43 '6028243': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 13 ms)
2017.10.24 00:58:05.483 5.10.18.43 '6028243': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 6 ms)
2017.10.04 21:59:08.151 5.10.18.43 '6028374': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 37 ms)
2017.10.24 01:13:19.473 5.10.18.43 '6029848': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 28 ms)
2017.10.24 00:55:47.267 5.10.18.43 '6029848': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 29 ms)

logins to 6026788:

2017.09.18 17:38:27.048 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 11 ms)
2017.09.15 15:07:00.178 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 15 ms)
2017.09.13 15:01:33.502 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 31 ms)
2017.09.15 15:11:44.755 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 34 ms)
2017.09.14 17:26:51.650 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 35 ms)
2017.09.13 22:23:21.828 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 36 ms)
2017.09.11 21:53:41.655 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 40 ms)
2017.09.12 15:02:14.165 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 55 ms)
2017.09.11 15:37:29.085 5.10.18.43 '6026788': login (1090, client, dc: 0, cid: e8744f3375e4347b534e2fe930bb1cff, ping: 7 ms)


Pursuant to its service instructions, the AML service had therefore to request additional information to confirm your ID and establish the source of your funds.

Regarding your assertion that it’s odd not to be able to hedge trades during 41 minutes ... The thing is, the prices didn’t correspond to market ones during that whole period. They were much slower than the real prices, and your trading advisor used that fact, having opened a big number of orders at non-existing prices. The architecture of the MT4 platform allowed those trades to be executed. However, the liquidity provider was not able to process the trades with those parameters because they didn’t correspond to the market situation.

Here’s a bright example of the trades opened at non-market prices which even were not in the chart (Attachment Wrongprices.xls). (Examples of orders indicated in the screenshots are highlighted in green).

View attachment 36362

Here are some screenshots of our charts:
View attachment 36365

View attachment 36366

View attachment 36367

View attachment 36368

As we see, the difference between the prices reached 50 points at some moments, which is a huge difference and an important sign of an incorrect data flow even under Forex decentralization.

If you do not confide in our data, I suggest you compare opening prices from a free access archive of quotes at DukasСopy, one of the most competent Forex brokers.

Probably, you have some examples of prices at which the above orders were opened with other brokers at that moment of time.

Also, you mentioned you are a news trader. Could you please name some fundamental news released from 19:44:10 to 20:25:11?
Click to expand...


I think enough has been said. Your company is very persistent in not paying out my profit and it seems nothing I can say can change that. I'd like to see what the community has to say after all the evidence has been presented. At the end of the day this is a public forum and after everything has been presented the traders get to decide if this is a scam or not.

I will answer your questions anyway:

On the pictures you are showing the price difference is between 4 and 6 pips, Tifia uses 5-decimal pricing, so 50 points in reality is 5 pips. a negligable difference in volatile times I often trades at times where the spread could even get higher than 10 pips or 100 in 5-decimal pricing. The price was provided I traded on it, as simple as that. As far as I know Tifia is my counterpart, whether any trades were hedged with another broker or liquidity provider(which is the same thing) is not under my control at all, Tifia might not even hedge anything at all as a business model, I don't know, but it does look this way

The IP addresses - this is most likely due to the VPS I use and the main EA I use might be used by others. I use icloudhosting.com and macrospike.com. Which I don't think I'm the only one in the world using, probably thousands of traders use these services, I don't know I can only speak for my own trading.

As for what news I traded that day. There was UK related chatter on ransqwak which also came through on macrospike, it was not a scheduled news release so the volatility in that case was pretty good for profit making, as I did on 3 other brokers(which I provided on here), during trades such as this one volatility remains for a while(up to 1-2 hrs) and I take full advantage whenever I can.

I don't need to justify why I took any trades I took, but I expect Tifia and any other broker I use to honor prices on the terminal whether profits or losses. Had I made a loss it would be impossible to get Tifia to reverse it, why should keeping my profits be any different, once the trade is booked you can't just come up with reasons to cancel it. It is standard practice in many jurisdictions once a trade is booked and 24 hours have passed it can't be altered, even 24 hours seem too long. Tifia is basically unregulated, I will tell you why, so you can try to do stuff like this and be able to stay in business.
 
Hello Tifia Rep,

If Chitak was complaining about a fill which was 6 pips off from another broker, the default response I've seen from all brokers is that forex is a decentralized marketplace, so there will be differences between brokers. Due to variable lag on the time orders take to fill, variations of several seconds would be expected.

News trading using ransquawk would give traders the chance to legitimately catch small spikes. Traders in this situation would not sit around waiting for the market to settle. They would also expect to have price differences between brokers. If a trader know that one broker was nearly always slower, than the others, why would that trader waste time trading the other brokers? If the trader is consistently making the same trades in the same direction within seconds of each other at several brokers, this argues against any of the usual arbitrage manipulation schemes.

Can you please clearly explain why several other large and alert brokers thought these trades were OK, but Tifia didn't?
 
AsstModerator said:
Hello Tifia Rep,

If Chitak was complaining about a fill which was 6 pips off from another broker, the default response I've seen from all brokers is that forex is a decentralized marketplace, so there will be differences between brokers. Due to variable lag on the time orders take to fill, variations of several seconds would be expected.

News trading using ransquawk would give traders the chance to legitimately catch small spikes. Traders in this situation would not sit around waiting for the market to settle. They would also expect to have price differences between brokers. If a trader know that one broker was nearly always slower, than the others, why would that trader waste time trading the other brokers? If the trader is consistently making the same trades in the same direction within seconds of each other at several brokers, this argues against any of the usual arbitrage manipulation schemes.

Can you please clearly explain why several other large and alert brokers thought these trades were OK, but Tifia didn't?
Click to expand...
Dear AsstModerator,
We are doing our best to explain the situation regarding these trades. If you have a look at the screenshots of the charts, you’ll see that such prices were not available in the chart. There were no spikes at which the advisor opened. There was a 40-min long problem on the server and the advisor opened at non-existing prices. You won’t find those prices with any broker; they just didn’t exist on our server and our charts. This was the reason why the trades were not opened at the counterparty. Do you really want the company to pay its own funds to the client for the trades which were not hedged by the counterparty due to the server’s malfunction? I need to mention that the client’s loss-making trades were canceled too. If FPA does insist, the company can make a compensatory payment. But do you think paying the client profits from non-existing trades is fair? Also, I need to remind you that a profit of almost 5000 euro has been already paid to the client.
 
Tifia FX said:
Do you really want the company to pay its own funds to the client for the trades which were not hedged by the counterparty due to the server’s malfunction?
Click to expand...

Yes 100%. My counterparty is Tifia, I can't go and ask some other broker to pay out my money, I don't have a relationship with your liquidity provider.

Tifia FX said:
Dear AsstModerator,
Also, I need to remind you that a profit of almost 5000 euro has been already paid to the client.
Click to expand...

How is that relevant to this at all? What are you trying to say, that Tifia pays only a 50% of profits or whatever the percentage is and I should be greatful for that? I don't get it...
 
Tifia Representative,

I have to strongly agree with Chitak's point regarding the profits. If you've paid out previous profits, that doesn't give any special rights to not honor other trades. If my bank even hinted that processing my paychecks all these years somehow meant it was ok to decide whether or not to credit my account for my most recently deposited paycheck, I'd close my account. Then I'd notify the regulators and warn everyone I knew to get their money out now.

Regarding the malfunction you claim, did this result in all trades opened or closed during that 40 minute window being cancelled? Was an announcement sent out about this malfunction to all users affected by the problem?
 
Tifia FX said:
Dear AsstModerator,
If FPA does insist, the company can make a compensatory payment. But do you think paying the client profits from non-existing trades is fair?
Click to expand...

Hey AsstMod would you please comment on this? It seems Tifia might be willing to do the right thing...
 
AsstModerator said:
Tifia Representative,

I have to strongly agree with Chitak's point regarding the profits. If you've paid out previous profits, that doesn't give any special rights to not honor other trades. If my bank even hinted that processing my paychecks all these years somehow meant it was ok to decide whether or not to credit my account for my most recently deposited paycheck, I'd close my account. Then I'd notify the regulators and warn everyone I knew to get their money out now.

Regarding the malfunction you claim, did this result in all trades opened or closed during that 40 minute window being cancelled? Was an announcement sent out about this malfunction to all users affected by the problem?
Click to expand...
Dear moderator,
You’ve drawn an analogy with a bank, but do you really think a bank wouldn’t take back interest paid wrongly due to a technical failure? Concerning your question: all the trades opened or closed during that 40 minute window were cancelled regardless of the result.

Loss-making trades were cancelled as well. If we hadn’t done that, clients might have come here complaining about losses incurred because of non-market prices. There was only one fair way to settle the issue: to cancel the result of all transactions opened/closed at non-market rate.

All the clients affected were notified of that malfunction. Unfortunately, the problem wasn’t detected immediately. However, when opening an account with our company, the client accepted the terms of our Public Offer, item 2.12 in particular:
2.12. The Company has a right to cancel or revise the results of the Client's transaction in the following cases:
- The transaction is opened/closed at non-market rate;
- In case of Server malfunctions;
https://tifia.com/uploads/docs/terms-of-business-en.pdf

We have already proved there was a server malfunction. None of the brokers would pay profits from trades opened at non-existing prices.
 
You must log in or register to reply here.

Similar threads

A
Problem Tifia: A huge problem
Replies
4
Views
14K
Amos Esele
A
B
Resolved: ACY is charging retroactive swaps in an unfair manner, effectively abusing consumer
Replies
9
Views
627
FxMaster
FxMaster
yrkaus
Resolved : Warning: HotForex (HF Markets) is no longer able to pay! Hurry up to WD your money
2
Replies
15
Views
375
FxMaster
FxMaster
F
Resolved: Octa Fx unilateral changing partial closes
Replies
7
Views
126
FxMaster
FxMaster
Ykpuffy07
Resolved: Exness price glitch
2
Replies
13
Views
660
FxMaster
FxMaster

Share this page

Back
Top