:: From NFOrce to 41.233.68.90:
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 85.159.239.222 0.0% 43 7.3 4.0 0.2 12.7 4.5
2. 34-239-159-85.rtr1.z1a-d18.tc5.nl.nforce.com 0.0% 43 0.4 0.5 0.3 1.2 0.2
6-239-159-85.rtr1.b06-s02-az16.gsa.nl.nforce.com
3. 17-137-104-5.rtr2.z4a-a06.tc2.nl.nforce.com 0.0% 43 2.4 8.5 0.3 44.0 11.9
17-136-104-5.rtr2.b06-s02-az16.gsa.nl.nforce.com
4. 195.69.147.21 11.9% 43 55.8 87.5 55.2 302.2 46.4 (ROUTER OF TEDATA)
5. host-163.121.211.126.tedata.net 44.2% 43 59.6 62.1 59.5 117.5 11.8
6. host-163.121.211.133.tedata.net 53.7% 42 60.0 63.4 59.7 117.7 13.3
7. ???


:: From LW to 41.233.68.90:
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. hosted.by.leaseweb.com 0.0% 157 0.5 1.4 0.3 97.5 7.9
2. te4-3.sr1.evo.leaseweb.net 0.0% 157 0.7 3.2 0.3 91.3 11.4
3. be11.crs.evo.leaseweb.net 0.0% 157 3.3 4.1 1.2 46.8 4.7
4. 31.31.32.4 0.0% 157 0.4 1.2 0.3 38.1 4.3
5. 195.69.147.21 10.9% 157 56.1 100.7 55.4 258.9 50.2 (ROUTER OF TEDATA)
6. host-163.121.211.130.tedata.net 59.0% 157 60.0 62.9 60.0 128.1 9.8
7. host-163.121.211.133.tedata.net 64.1% 157 60.1 65.3 59.9 114.0 11.6
8. ???


:: From NFOrce to 197.34.161.114:
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 85.159.239.222 0.0% 18 3.6 3.2 0.1 13.2 4.4
2. 6-239-159-85.rtr1.b06-s02-az16.gsa.nl.nforce.com 0.0% 18 0.4 0.4 0.3 0.6 0.1
34-239-159-85.rtr1.z1a-d18.tc5.nl.nforce.com
3. 17-137-104-5.rtr2.z4a-a06.tc2.nl.nforce.com 0.0% 18 0.4 9.1 0.4 45.6 16.0
17-136-104-5.rtr2.b06-s02-az16.gsa.nl.nforce.com
4. 195.69.147.21 33.3% 18 171.7 101.2 55.2 174.3 50.1 (ROUTER OF TEDATA)
5. host-163.121.238.122.tedata.net 11.1% 18 60.1 60.1 59.8 61.1 0.3
host-163.121.235.62.tedata.net
6. host-163.121.228.198.tedata.net 33.3% 18 59.8 60.2 59.8 60.5 0.2
7. host-163.121.235.57.tedata.net 5.6% 18 60.7 62.0 60.6 64.4 1.3
8. 10.37.244.130 16.7% 18 62.0 62.5 60.7 64.0 1.0
9. 10.44.0.6 5.6% 18 62.1 62.7 61.2 64.0 0.8
10. host-41.41.122.21.tedata.net 5.9% 18 60.1 60.8 60.1 64.2 1.0
11. ???


:: From LW to 197.34.161.114:
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. hosted.by.leaseweb.com 0.0% 58 0.5 1.2 0.3 21.9 3.2
2. te4-3.sr1.evo.leaseweb.net 0.0% 58 14.3 4.8 0.4 55.2 11.2
3. be11.crs.evo.leaseweb.net 0.0% 58 3.0 3.4 0.9 6.1 1.3
4. 31.31.32.8 0.0% 58 0.3 0.8 0.3 22.5 3.0
5. 195.69.147.21 12.1% 58 55.7 99.2 55.5 268.8 58.4 (ROUTER OF TEDATA)
6. host-163.121.238.122.tedata.net 15.5% 58 59.9 60.2 59.7 63.5 0.6
host-163.121.235.62.tedata.net
7. host-163.121.228.198.tedata.net 5.3% 57 60.4 60.7 60.1 65.1 0.9
8. host-163.121.235.57.tedata.net 7.0% 57 62.5 63.3 60.5 81.0 2.8
9. ???
10. ???
11. host-41.41.122.21.tedata.net 10.7% 57 60.8 60.7 60.4 62.7 0.4
12. ???



They seem to have issues the minute it drops off on the AMS-IX with them. But I also see the same when sending it over the DECIX. As it could be their routers are ratelimiting ICMP, it might be good if you had an ICMP enabled IP address of a client over there, then we can rule that out.

As far as I know we did not hear anything back from them.

Something is odd as when you look at the traceroutes from your client to NFOrce for example, you see that TEDATA sends the traffic over Seabone (a transit provider), and not over the AMS-IX peering. Not sure why.. But its rather odd, unless they have done this on purpose as they have capacity problems?



Just to rule things out, I am sending it back over Seabone for a test, which sents it in London to Level3 and then in France to TEDATA. Also packetloss:

Host Loss% Snt Last Avg Best Wrst StDev
1. 85.159.239.222 0.0% 16 0.2 4.8 0.2 12.6 5.0
2. 6-239-159-85.rtr1.b06-s02-az16.gsa.nl.nforce.com 0.0% 16 0.4 0.4 0.3 0.6 0.1
3. xe-10-3-0.amster51.ams.seabone.net 0.0% 16 0.6 2.6 0.6 17.5 5.2
4. te0-15-0-0.londra17.lon.seabone.net 0.0% 16 16.0 16.9 15.1 19.1 1.2
5. xe-4-3-1.londra32.lon.seabone.net 0.0% 16 13.7 13.7 13.7 13.8 0.0
6. ae12.edge3.London.Level3.net 0.0% 16 24.3 21.1 12.1 55.8 15.0
7. vl-3504-ve-118.csw1.London1.Level3.net 0.0% 16 30.3 31.2 30.3 39.5 2.3
8. ae-56-111.ebr1.London1.Level3.net 0.0% 16 29.6 30.8 29.6 41.1 3.0
9. ae-45-45.ebr1.Paris1.Level3.net 0.0% 16 30.6 30.7 30.6 31.8 0.3
10. ae-81-81.csw3.Paris1.Level3.net 0.0% 16 29.7 29.7 29.7 29.8 0.0
11. ae-83-83.ebr3.Paris1.Level3.net 0.0% 16 30.1 30.2 30.1 31.4 0.3
12. ae-1-7.bar1.Marseille1.Level3.net 6.2% 16 29.8 29.8 29.8 29.9 0.0
13. 213.242.116.50 37.5% 16 67.5 87.0 67.4 140.6 28.4
14. host-163.121.235.62.tedata.net 6.7% 16 72.3 72.1 71.9 72.3 0.1
host-163.121.238.122.tedata.net
15. host-163.121.228.198.tedata.net 6.7% 15 72.4 72.2 72.1 72.4 0.1
16. host-163.121.235.57.tedata.net 20.0% 15 76.3 74.4 72.4 76.3 1.4
17. 10.37.244.130 13.3% 15 73.4 74.4 72.6 75.8 1.2
18. 10.44.0.6 13.3% 15 74.1 74.7 73.0 76.5 1.0
19. host-41.41.122.21.tedata.net 6.7% 15 72.6 72.5 72.4 72.8 0.1
20. ???



I am afraid that at this point we could only resent an email to them. But they most likely will ignore or not go into details. We aint a paying customer of them, so they most likely do not 'care' to say simple.