Afrihost New Network Feedback - Part 3

Status
Not open for further replies.
The regional routing is determined by IPs, when you request access to Reddit, you receive a number of IPs from which you can access the site, if those IPs are all in Australia that is where the routing will go.

We need to work with our Networking Team and Reddit to find the best routing for us.

Right. So when on the AfriHost network, you send a request for the Reddit site and because of something setup with your backbone, Reddit's giving you Australian addresses to connect to. It still boils down to your routing going via Australia instead of a closer route which is evident when using another ISP.

This can go back and forth but the bottom line is that multiple users have confirmed that when using Afrihost, routes to Reddit.com go via Australia while routes via another ISP go consistently via London which is obviously much closer geographically.

I've switched back to WebAfrica and apart from the issues last night, have not had the same type of latency seen with Afrihost since the beginning of the year. Really wish there was an improvement.
 
Right. So when on the AfriHost network, you send a request for the Reddit site and because of something setup with your backbone, Reddit's giving you Australian addresses to connect to. It still boils down to your routing going via Australia instead of a closer route which is evident when using another ISP.

This can go back and forth but the bottom line is that multiple users have confirmed that when using Afrihost, routes to Reddit.com go via Australia while routes via another ISP go consistently via London which is obviously much closer geographically.

I've switched back to WebAfrica and apart from the issues last night, have not had the same type of latency seen with Afrihost since the beginning of the year. Really wish there was an improvement.

That's why our Team is working on getting the traffic routed to Europe. :) It is most definitely something that we are working on. I was just giving a bit of context. :)
 
C:\Users\ tracert google.com

Tracing route to google.com [169.1.2.93]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 10.0.0.2
2 * * * Request timed out.
3 10 ms 8 ms 8 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 27 ms 10 ms 10 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 12 ms 8 ms 9 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 11 ms 10 ms 9 ms 169-1-21-9.ip.afrihost.co.za [169.1.21.9]
7 8 ms 8 ms 8 ms 169-1-2-93.ip.afrihost.co.za [169.1.2.93]

Trace complete.

there does seem to be high latency when tracing Reddit.com around the 15th and 16th hop that i checked

Tracing route to reddit.com [151.101.65.140]
over a maximum of 30 hops:

1 2 ms 1 ms 2 ms 10.0.0.2
2 * * * Request timed out.
3 13 ms 9 ms 8 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 10 ms 9 ms 9 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 8 ms 10 ms 10 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 9 ms 8 ms 10 ms 41.164.52.40
7 9 ms 8 ms 9 ms ix-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
8 190 ms 173 ms 164 ms if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
9 136 ms 137 ms 134 ms if-p-6.core2.PV9-Lisbon.as6453.net [41.206.164.6]
10 157 ms 156 ms 156 ms if-xe-0-0-0-15.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
11 162 ms 162 ms 163 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 166 ms 269 ms 167 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
13 * * * Request timed out.
14 155 ms 155 ms 156 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
15 468 ms 321 ms 1363 ms 195.219.83.186
16 1601 ms 479 ms 161 ms ae-3.r02.londen05.uk.bb.gin.ntt.net [129.250.2.119]
17 * * * Request timed out.
18 166 ms 166 ms 166 ms 151.101.65.140

Trace complete

to mybroadband.co.za and Google.com as above its pretty good

C:\Users\ tracert mybroadband.co.za

Tracing route to mybroadband.co.za [104.20.9.169]
over a maximum of 30 hops:

1 * 1 ms 2 ms 10.0.0.2
2 * * * Request timed out.
3 10 ms 8 ms 8 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 11 ms 8 ms 9 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 9 ms 9 ms 9 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 10 ms 9 ms 9 ms 41.164.52.40
7 29 ms 43 ms 34 ms 172.18.1.164
8 29 ms 29 ms 29 ms cloudflare.ixp.joburg [196.46.25.198]
9 32 ms 34 ms 34 ms 104.20.9.169

Trace complete
 
C:\Users\ tracert google.com

Tracing route to google.com [169.1.2.93]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 10.0.0.2
2 * * * Request timed out.
3 10 ms 8 ms 8 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 27 ms 10 ms 10 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 12 ms 8 ms 9 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 11 ms 10 ms 9 ms 169-1-21-9.ip.afrihost.co.za [169.1.21.9]
7 8 ms 8 ms 8 ms 169-1-2-93.ip.afrihost.co.za [169.1.2.93]

Trace complete.

there does seem to be high latency when tracing Reddit.com around the 15th and 16th hop that i checked

Tracing route to reddit.com [151.101.65.140]
over a maximum of 30 hops:

1 2 ms 1 ms 2 ms 10.0.0.2
2 * * * Request timed out.
3 13 ms 9 ms 8 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 10 ms 9 ms 9 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 8 ms 10 ms 10 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 9 ms 8 ms 10 ms 41.164.52.40
7 9 ms 8 ms 9 ms ix-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
8 190 ms 173 ms 164 ms if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
9 136 ms 137 ms 134 ms if-p-6.core2.PV9-Lisbon.as6453.net [41.206.164.6]
10 157 ms 156 ms 156 ms if-xe-0-0-0-15.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
11 162 ms 162 ms 163 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 166 ms 269 ms 167 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
13 * * * Request timed out.
14 155 ms 155 ms 156 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
15 468 ms 321 ms 1363 ms 195.219.83.186
16 1601 ms 479 ms 161 ms ae-3.r02.londen05.uk.bb.gin.ntt.net [129.250.2.119]
17 * * * Request timed out.
18 166 ms 166 ms 166 ms 151.101.65.140

Trace complete

to mybroadband.co.za and Google.com as above its pretty good

C:\Users\ tracert mybroadband.co.za

Tracing route to mybroadband.co.za [104.20.9.169]
over a maximum of 30 hops:

1 * 1 ms 2 ms 10.0.0.2
2 * * * Request timed out.
3 10 ms 8 ms 8 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 11 ms 8 ms 9 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 9 ms 9 ms 9 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 10 ms 9 ms 9 ms 41.164.52.40
7 29 ms 43 ms 34 ms 172.18.1.164
8 29 ms 29 ms 29 ms cloudflare.ixp.joburg [196.46.25.198]
9 32 ms 34 ms 34 ms 104.20.9.169

Trace complete

Yeah... Those hops are doing something strange... I think it is linked to the routing going to Australia, but I'll pass it onto our Team.
 
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=70ms TTL=63
Reply from 155.239.255.250: bytes=32 time=54ms TTL=63
Reply from 155.239.255.250: bytes=32 time=59ms TTL=63
Reply from 155.239.255.250: bytes=32 time=46ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 70ms, Average = 57ms



Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=92ms TTL=63
Reply from 155.239.255.250: bytes=32 time=77ms TTL=63
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 92ms, Average = 65ms



Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=86ms TTL=63
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 86ms, Average = 42ms



Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Reply from 155.239.255.250: bytes=32 time=79ms TTL=63
Reply from 155.239.255.250: bytes=32 time=63ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 79ms, Average = 59ms

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=86ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 86ms, Average = 52ms

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Reply from 155.239.255.250: bytes=32 time=82ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=93ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 93ms, Average = 64ms

Is this exchange related?
 
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=70ms TTL=63
Reply from 155.239.255.250: bytes=32 time=54ms TTL=63
Reply from 155.239.255.250: bytes=32 time=59ms TTL=63
Reply from 155.239.255.250: bytes=32 time=46ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 70ms, Average = 57ms



Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=92ms TTL=63
Reply from 155.239.255.250: bytes=32 time=77ms TTL=63
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 92ms, Average = 65ms



Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=86ms TTL=63
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 86ms, Average = 42ms



Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Reply from 155.239.255.250: bytes=32 time=79ms TTL=63
Reply from 155.239.255.250: bytes=32 time=63ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 79ms, Average = 59ms

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=86ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 86ms, Average = 52ms

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Reply from 155.239.255.250: bytes=32 time=82ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=93ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 93ms, Average = 64ms

Is this exchange related?

Your average pings seem higher than usual - especially when you ping bras.afrihost.com. Are you running these tests wirelessly? Are you seeing latency and P/L to your router?
 
Im going to do a little test, ping is now 30 on teamspeak, if i see it stay at 100ms later on would that identify an issue?
 
Am I the only one feeling this crap again

Code:
Tracing route to youtube-ui.l.google.com [169.1.2.86]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    61 ms    56 ms    50 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    94 ms   100 ms   101 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6   102 ms   105 ms   105 ms  169-1-21-9.ip.afrihost.co.za [169.1.21.9] 
  7    19 ms    19 ms    18 ms  169-1-2-86.ip.afrihost.co.za [169.1.2.86] 

Trace complete.

Code:
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4   115 ms   110 ms   104 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    97 ms    99 ms    95 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6   103 ms    80 ms    79 ms  optinet.ixp.capetown [196.10.140.15] 
  7   112 ms   108 ms   100 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  8    90 ms    98 ms    94 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  9    21 ms    19 ms    19 ms  196.28.178.66 
 10    94 ms    95 ms    99 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 11    22 ms    20 ms    19 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 12    79 ms    74 ms    86 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 13    19 ms    19 ms    23 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.
 
Nope... I am too - all #$#@$@@#$ day!!! :mad:

Am I the only one feeling this crap again

Code:
Tracing route to youtube-ui.l.google.com [169.1.2.86]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    61 ms    56 ms    50 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    94 ms   100 ms   101 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6   102 ms   105 ms   105 ms  169-1-21-9.ip.afrihost.co.za [169.1.21.9] 
  7    19 ms    19 ms    18 ms  169-1-2-86.ip.afrihost.co.za [169.1.2.86] 

Trace complete.

Code:
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4   115 ms   110 ms   104 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    97 ms    99 ms    95 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6   103 ms    80 ms    79 ms  optinet.ixp.capetown [196.10.140.15] 
  7   112 ms   108 ms   100 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  8    90 ms    98 ms    94 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  9    21 ms    19 ms    19 ms  196.28.178.66 
 10    94 ms    95 ms    99 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 11    22 ms    20 ms    19 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 12    79 ms    74 ms    86 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 13    19 ms    19 ms    23 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.
 
I'm not even going to log a new ticket because then one of their ROCKET SCIENTIST support guys will ask me something stupid like this again:

Thato here

Which games in particular are you having issues with?
Please run traceroutes to those servers.

Yep, let me quickly just ask "Ubisoft" for all their server addresses :rolleyes:

It's not the game, it's Afrihost because as soon as I changed my account to WebAfrica then the bloody game worked fine and when I changed it back, I had issues.
Last couple of weeks has been the pits with Afrihost and I'm finding it frustrating that can't accept fault - they blame others before they realize it's actually their service! :mad:
 
I'm not even going to log a new ticket because then one of their ROCKET SCIENTIST support guys will ask me something stupid like this again:



Yep, let me quickly just ask "Ubisoft" for all their server addresses :rolleyes:

It's not the game, it's Afrihost because as soon as I changed my account to WebAfrica then the bloody game worked fine and when I changed it back, I had issues.
Last couple of weeks has been the pits with Afrihost and I'm finding it frustrating that can't accept fault - they blame others before they realize it's actually their service! :mad:

I can understand that he requests which game you have issues with, in order to do the investigation himself... But why the hell is it the client's job to supply evidence or run tests? If its not congestion at your exchange, then SURELY there has to either be a routing or configuration issue. Why is the client involved at all, other than logging a fault?
 
I can understand that he requests which game you have issues with, in order to do the investigation himself... But why the hell is it the client's job to supply evidence or run tests? If its not congestion at your exchange, then SURELY there has to either be a routing or configuration issue. Why is the client involved at all, other than logging a fault?

It's Afrihost bru... They are frustrating the hell outta me (and others) lately.
 
Having issues with Twitch even at 2AM

Yes it's all streams, yes I've brought it up more than once in the span of a week, no I haven't heard from you.

0e25d816c2.png

a110415681.jpg
 
Am I the only one feeling this crap again

Code:
Tracing route to youtube-ui.l.google.com [169.1.2.86]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    61 ms    56 ms    50 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    94 ms   100 ms   101 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6   102 ms   105 ms   105 ms  169-1-21-9.ip.afrihost.co.za [169.1.21.9] 
  7    19 ms    19 ms    18 ms  169-1-2-86.ip.afrihost.co.za [169.1.2.86] 

Trace complete.

Code:
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4   115 ms   110 ms   104 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    97 ms    99 ms    95 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6   103 ms    80 ms    79 ms  optinet.ixp.capetown [196.10.140.15] 
  7   112 ms   108 ms   100 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  8    90 ms    98 ms    94 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  9    21 ms    19 ms    19 ms  196.28.178.66 
 10    94 ms    95 ms    99 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 11    22 ms    20 ms    19 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 12    79 ms    74 ms    86 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 13    19 ms    19 ms    23 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

That doesn't look right at all... How are your speeds looking at the moment? Are you using our DNS at the moment?
 
Nope... I am too - all #$#@$@@#$ day!!! :mad:

I'm not even going to log a new ticket because then one of their ROCKET SCIENTIST support guys will ask me something stupid like this again:



Yep, let me quickly just ask "Ubisoft" for all their server addresses :rolleyes:

It's not the game, it's Afrihost because as soon as I changed my account to WebAfrica then the bloody game worked fine and when I changed it back, I had issues.
Last couple of weeks has been the pits with Afrihost and I'm finding it frustrating that can't accept fault - they blame others before they realize it's actually their service! :mad:

It's Afrihost bru... They are frustrating the hell outta me (and others) lately.

I understand that you are frustrated, but I'm going to ask that you please remain respectful towards our Support Agents, they are trying to assist you in getting your issue resolved, and calling them names is definitely not on.

I'm not aware of any specific games that we are having issues with, so we'll definitely need to look into this. Which games are problematic for you?

Is there a specific time that the games are playable and then not playable?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X