What region? If you aren't sure, please check a traceroute. We are most concerned about our Cape Town site (105.226.0.* on hops 2 and 3 or 3 and 4).
Netflix was tested and seemed quite good via our Gauteng site.
Ranger see below the trace, it looks like the following hops (105.226.0.6 & 105.226.0.13)
C:\Users\Will>tracert netflix.com
Tracing route to netflix.com [69.53.236.17]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 11 ms 11 ms ti-224-180-01.telkomadsl.co.za [105.224.180.1]
3 12 ms 12 ms 12 ms ti-226-0-06.telkomadsl.co.za [105.226.0.6]
4 12 ms 13 ms 12 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13]
5 11 ms 11 ms 12 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.45]
6 219 ms 219 ms 219 ms ams-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.90]
7 376 ms 196 ms 186 ms te2-5.ccr01.ams07.atlas.cogentco.com [149.6.60.69]
8 187 ms 187 ms 187 ms te0-7-0-32.mpd22.ams03.atlas.cogentco.com [130.117.3.237]
9 194 ms 191 ms 191 ms be2185.ccr22.lpl01.atlas.cogentco.com [154.54.37.106]
10 261 ms 261 ms 262 ms be2385.ccr22.ymq02.atlas.cogentco.com [154.54.44.141]
11 267 ms 269 ms 268 ms be2093.ccr22.yyz02.atlas.cogentco.com [154.54.44.105]
12 282 ms 282 ms 302 ms be2080.ccr22.ord01.atlas.cogentco.com [154.54.42.5]
13 293 ms 292 ms 292 ms be2157.ccr22.mci01.atlas.cogentco.com [154.54.6.117]
14 331 ms 330 ms 330 ms be2133.ccr22.sfo01.atlas.cogentco.com [154.54.30.65]
15 332 ms 345 ms 332 ms be2016.ccr21.sjc04.atlas.cogentco.com [154.54.0.178]
16 332 ms 332 ms 333 ms 206.111.12.197.ptr.us.xo.net [206.111.12.197]
17 342 ms 334 ms 335 ms 207.88.13.233.ptr.us.xo.net [207.88.13.233]
18 * 333 ms 334 ms 207.88.14.226.ptr.us.xo.net [207.88.14.226]
19 333 ms 331 ms 331 ms 216.156.84.6.ptr.us.xo.net [216.156.84.6]
20 333 ms 332 ms 332 ms xe-2-2-0-955.jnrt-edge02.prod1.netflix.com [69.53.225.30]
21 336 ms 339 ms 335 ms te1-8.csrt-agg02.prod1.netflix.com [69.53.225.10]
22 334 ms 334 ms 333 ms www.trynetflix.com [69.53.236.17]
Trace complete.
