Cool Ideas Fibre ISP – Feedback Thread 4

TheRoDent

Cool Ideas Rep
Joined
Aug 6, 2003
Messages
5,962
I am on Vuma Reach and I assume Cool Ideas uses CGNAT for this since everyone else does. @PBCool is there anyway for me to get a Public IP address for my line since I’m pretty sure it’s one of the reasons I struggle to find games or lose connection on FIFA 21 which uses P2P matchmaking.
Yes, you can log a ticket requesting a public IP to support@coolideas.co.za
 

SplaT

Well-Known Member
Joined
Feb 12, 2008
Messages
237
So if you're on 200/200 then 90Mbps upload should not have any packet loss.

The best way is to test with something basic for upload, like 10Mbps. If that's still showing loss then it's definately a line issue, and needs to be investigated. Either cabling from your PC to the router, or from the router to the ONT. Finally it could then be the actual ONT uplink to the POP itself, or the ONT itself, which Vumatel will have to check.

48% loss on upload will definately affect your upload performance, but it is strange that it improved a bit after your winsock reset.

Another way to narrow down the issue is to try and connect directly to the ONT with your PC and test just to eliminate the router.

If it persists please log a ticket stating that you have upload packetloss with a copy of the UDP upload results.

This is my iperf test bypassing the router and plugging my PC directly into the ONT.
I'm assuming this means it's my router that's screwed and nothing to do with CISP?

0.066% packet loss is a teensy bit better than 48%, I would say...

Code:
C:\iperf>iperf3 -u -b 90M -O2 -t 10 -p 17001 -c cptspeedtest.cisp.co.za
Connecting to host cptspeedtest.cisp.co.za, port 17001
[  4] local 155.93.162.118 port 51910 connected to 154.0.15.181 port 17001
[ ID] Interval           Transfer     Bandwidth       Total Datagrams
[  4]   0.00-1.01   sec  9.90 MBytes  82.5 Mbits/sec  1267  (omitted)
[  4]   1.01-2.00   sec  10.7 MBytes  90.1 Mbits/sec  1370  (omitted)
[  4]   0.00-1.01   sec  10.6 MBytes  88.4 Mbits/sec  1362
[  4]   1.01-2.00   sec  10.7 MBytes  90.0 Mbits/sec  1367
[  4]   2.00-3.00   sec  10.9 MBytes  91.6 Mbits/sec  1391
[  4]   3.00-4.01   sec  10.6 MBytes  88.5 Mbits/sec  1359
[  4]   4.01-5.00   sec  11.0 MBytes  93.3 Mbits/sec  1414
[  4]   5.00-6.01   sec  10.4 MBytes  86.7 Mbits/sec  1331
[  4]   6.01-7.00   sec  11.0 MBytes  93.0 Mbits/sec  1411
[  4]   7.00-8.01   sec  10.4 MBytes  87.0 Mbits/sec  1335
[  4]   8.01-9.01   sec  10.8 MBytes  90.5 Mbits/sec  1387
[  4]   9.01-10.00  sec  10.8 MBytes  91.2 Mbits/sec  1380
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-10.00  sec   107 MBytes  90.0 Mbits/sec  0.326 ms  9/13737 (0.066%)
[  4] Sent 13737 datagrams
 

MDE

Expert Member
Joined
May 18, 2009
Messages
2,149
This is my iperf test bypassing the router and plugging my PC directly into the ONT.
I'm assuming this means it's my router that's screwed and nothing to do with CISP?

0.066% packet loss is a teensy bit better than 48%, I would say...

Code:
C:\iperf>iperf3 -u -b 90M -O2 -t 10 -p 17001 -c cptspeedtest.cisp.co.za
Connecting to host cptspeedtest.cisp.co.za, port 17001
[ 4] local 155.93.162.118 port 51910 connected to 154.0.15.181 port 17001
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.01 sec 9.90 MBytes 82.5 Mbits/sec 1267 (omitted)
[ 4] 1.01-2.00 sec 10.7 MBytes 90.1 Mbits/sec 1370 (omitted)
[ 4] 0.00-1.01 sec 10.6 MBytes 88.4 Mbits/sec 1362
[ 4] 1.01-2.00 sec 10.7 MBytes 90.0 Mbits/sec 1367
[ 4] 2.00-3.00 sec 10.9 MBytes 91.6 Mbits/sec 1391
[ 4] 3.00-4.01 sec 10.6 MBytes 88.5 Mbits/sec 1359
[ 4] 4.01-5.00 sec 11.0 MBytes 93.3 Mbits/sec 1414
[ 4] 5.00-6.01 sec 10.4 MBytes 86.7 Mbits/sec 1331
[ 4] 6.01-7.00 sec 11.0 MBytes 93.0 Mbits/sec 1411
[ 4] 7.00-8.01 sec 10.4 MBytes 87.0 Mbits/sec 1335
[ 4] 8.01-9.01 sec 10.8 MBytes 90.5 Mbits/sec 1387
[ 4] 9.01-10.00 sec 10.8 MBytes 91.2 Mbits/sec 1380
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 107 MBytes 90.0 Mbits/sec 0.326 ms 9/13737 (0.066%)
[ 4] Sent 13737 datagrams
Could be.

1. Could be the cable
2. Could be QoS on the router
3. Faulty port on the router.

List can go on
 

TheRoDent

Cool Ideas Rep
Joined
Aug 6, 2003
Messages
5,962
This is my iperf test bypassing the router and plugging my PC directly into the ONT.
I'm assuming this means it's my router that's screwed and nothing to do with CISP?

0.066% packet loss is a teensy bit better than 48%, I would say...

Code:
C:\iperf>iperf3 -u -b 90M -O2 -t 10 -p 17001 -c cptspeedtest.cisp.co.za
Connecting to host cptspeedtest.cisp.co.za, port 17001
[  4] local 155.93.162.118 port 51910 connected to 154.0.15.181 port 17001
[ ID] Interval           Transfer     Bandwidth       Total Datagrams
[  4]   0.00-1.01   sec  9.90 MBytes  82.5 Mbits/sec  1267  (omitted)
[  4]   1.01-2.00   sec  10.7 MBytes  90.1 Mbits/sec  1370  (omitted)
[  4]   0.00-1.01   sec  10.6 MBytes  88.4 Mbits/sec  1362
[  4]   1.01-2.00   sec  10.7 MBytes  90.0 Mbits/sec  1367
[  4]   2.00-3.00   sec  10.9 MBytes  91.6 Mbits/sec  1391
[  4]   3.00-4.01   sec  10.6 MBytes  88.5 Mbits/sec  1359
[  4]   4.01-5.00   sec  11.0 MBytes  93.3 Mbits/sec  1414
[  4]   5.00-6.01   sec  10.4 MBytes  86.7 Mbits/sec  1331
[  4]   6.01-7.00   sec  11.0 MBytes  93.0 Mbits/sec  1411
[  4]   7.00-8.01   sec  10.4 MBytes  87.0 Mbits/sec  1335
[  4]   8.01-9.01   sec  10.8 MBytes  90.5 Mbits/sec  1387
[  4]   9.01-10.00  sec  10.8 MBytes  91.2 Mbits/sec  1380
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-10.00  sec   107 MBytes  90.0 Mbits/sec  0.326 ms  9/13737 (0.066%)
[  4] Sent 13737 datagrams
Yes, 9 packets out of 13000 is pretty much to be expected, definately a "teensy" bit better.

So that indicates something from the ONT to your Router, or perhaps onwards.
 

neoassasin

Senior Member
Joined
Dec 22, 2005
Messages
761
Yes, you can log a ticket requesting a public IP to support@coolideas.co.za

@TheRoDent are you sure you guys use CGNAT on Vuma Reach and that I can request a Public IP address. Because I logged the ticket and one of your support consultants contacted me saying you don’t and that all your clients have public IP addresses. He also said he spoke to the engineers there and nobody has any idea of what I’m talking about. He said I should screenshot the post where you said I can contact support to request a Public IP address.
 

TheRoDent

Cool Ideas Rep
Joined
Aug 6, 2003
Messages
5,962
Additionally, use the latest version of iperf3 to avoid any erroneous packet loss results - older versions would count out of order datagrams towards total loss.


Some comparisons below, same test, diff versions 80% of line upload
Code:
iperf3 -u -b 80M -p 17001 -c cptspeedtest.cisp.co.za -O 2
[ ID] Interval           Transfer     Bandwidth       Total Datagrams
[  4]   0.00-1.01   sec  8.68 MBytes  72.0 Mbits/sec  1111  (omitted)
[  4]   1.00-1.00   sec  10.4 MBytes  43.5 Mbits/sec  2562
[  4]   1.00-2.00   sec  9.54 MBytes  80.1 Mbits/sec  1221
[  4]   2.00-3.00   sec  9.56 MBytes  80.0 Mbits/sec  1224
[  4]   3.00-4.00   sec  9.01 MBytes  75.9 Mbits/sec  1153
[  4]   4.00-5.00   sec  9.23 MBytes  77.4 Mbits/sec  1182
[  4]   5.00-6.00   sec  10.0 MBytes  84.1 Mbits/sec  1282
[  4]   6.00-7.00   sec  9.86 MBytes  82.5 Mbits/sec  1262
[  4]   7.00-8.01   sec  9.59 MBytes  80.2 Mbits/sec  1228
[  4]   8.01-9.00   sec  9.49 MBytes  79.8 Mbits/sec  1215
[  4]   9.00-10.00  sec  8.61 MBytes  72.7 Mbits/sec  1102
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-10.00  sec  95.3 MBytes  80.0 Mbits/sec  0.130 ms  13/12201 (0.11%)
[  4] Sent 12201 datagrams

iperf3 -u -b 80M -p 17001 -c cptspeedtest.cisp.co.za -O 2
[ ID] Interval           Transfer     Bandwidth       Total Datagrams
[  4]   0.00-1.01   sec  8.87 MBytes  73.3 Mbits/sec  1135  (omitted)
[  4]   1.01-2.01   sec  9.48 MBytes  80.1 Mbits/sec  1213  (omitted)
[  4]   0.00-1.00   sec  9.80 MBytes  82.2 Mbits/sec  1254
[  4]   1.00-2.00   sec  9.38 MBytes  78.7 Mbits/sec  1201
[  4]   2.00-3.00   sec  9.64 MBytes  80.9 Mbits/sec  1234
[  4]   3.00-4.00   sec  9.58 MBytes  80.3 Mbits/sec  1226
[  4]   4.00-5.00   sec  9.34 MBytes  78.4 Mbits/sec  1196
[  4]   5.00-6.01   sec  9.42 MBytes  78.4 Mbits/sec  1206
[  4]   6.01-7.00   sec  9.55 MBytes  80.3 Mbits/sec  1222
[  4]   7.00-8.00   sec  9.47 MBytes  79.5 Mbits/sec  1212
[  4]   8.00-9.00   sec  9.76 MBytes  82.2 Mbits/sec  1249
[  4]   9.00-10.00  sec  9.59 MBytes  80.9 Mbits/sec  1228
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-10.00  sec  95.5 MBytes  80.2 Mbits/sec  0.120 ms  3/12227 (0.025%)
[  4] Sent 12227 datagrams

iperf3 -u -b 80M -p 17001 -c cptspeedtest.cisp.co.za -O 2
[ ID] Interval           Transfer     Bandwidth       Total Datagrams
[  4]   0.00-1.00   sec  8.73 MBytes  73.1 Mbits/sec  1117  (omitted)
[  4]   1.00-2.00   sec  9.65 MBytes  80.7 Mbits/sec  1235  (omitted)
[  4]   0.00-1.01   sec  9.45 MBytes  78.4 Mbits/sec  1210
[  4]   1.01-2.00   sec  9.81 MBytes  82.8 Mbits/sec  1256
[  4]   2.00-3.01   sec  9.28 MBytes  77.7 Mbits/sec  1188
[  4]   3.01-4.00   sec  9.77 MBytes  82.3 Mbits/sec  1251
[  4]   4.00-5.00   sec  9.57 MBytes  80.5 Mbits/sec  1225
[  4]   5.00-6.01   sec  9.22 MBytes  76.5 Mbits/sec  1180
[  4]   6.01-7.01   sec  9.55 MBytes  80.4 Mbits/sec  1222
[  4]   7.01-8.01   sec  9.52 MBytes  79.9 Mbits/sec  1218
[  4]   8.01-9.01   sec  9.55 MBytes  79.8 Mbits/sec  1222
[  4]   9.01-10.00  sec  9.64 MBytes  81.2 Mbits/sec  1234
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-10.00  sec  95.4 MBytes  80.0 Mbits/sec  0.127 ms  1/12206 (0.0082%)
[  4] Sent 12206 datagrams

Code:
iperf3 -u -b 80M -p 17001 -c cptspeedtest.cisp.co.za -O 2
[ ID] Interval           Transfer     Bitrate         Total Datagrams
[  5]   0.00-1.00   sec  9.49 MBytes  79.6 Mbits/sec  6815  (omitted)
[  5]   1.00-2.01   sec  9.55 MBytes  79.6 Mbits/sec  6860  (omitted)
[  5]   0.00-1.01   sec  9.59 MBytes  80.0 Mbits/sec  6890
[  5]   1.01-2.00   sec  9.54 MBytes  80.5 Mbits/sec  6855
[  5]   2.00-3.01   sec  9.54 MBytes  79.4 Mbits/sec  6851
[  5]   3.01-4.00   sec  9.51 MBytes  80.4 Mbits/sec  6829
[  5]   4.00-5.00   sec  9.52 MBytes  79.6 Mbits/sec  6838
[  5]   5.00-6.00   sec  9.52 MBytes  80.1 Mbits/sec  6837
[  5]   6.00-7.01   sec  9.61 MBytes  79.9 Mbits/sec  6901
[  5]   7.01-8.01   sec  9.52 MBytes  80.0 Mbits/sec  6835
[  5]   8.01-9.00   sec  9.51 MBytes  80.2 Mbits/sec  6829
[  5]   9.00-9.99   sec  9.52 MBytes  80.4 Mbits/sec  6838
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-9.99   sec  95.4 MBytes  80.1 Mbits/sec  0.000 ms  0/68503 (0%)  sender
[  5]   0.00-10.05  sec  95.8 MBytes  80.0 Mbits/sec  0.075 ms  0/68499 (0%)  receiver

iperf3 -u -b 80M -p 17001 -c cptspeedtest.cisp.co.za -O 2
[ ID] Interval           Transfer     Bitrate         Total Datagrams
[  5]   0.00-1.01   sec  9.52 MBytes  79.3 Mbits/sec  6839  (omitted)
[  5]   1.01-2.00   sec  9.54 MBytes  80.6 Mbits/sec  6853  (omitted)
[  5]   0.00-1.01   sec  9.53 MBytes  79.3 Mbits/sec  6841
[  5]   1.01-2.01   sec  9.53 MBytes  80.0 Mbits/sec  6845
[  5]   2.01-3.00   sec  9.51 MBytes  80.3 Mbits/sec  6831
[  5]   3.00-4.00   sec  9.51 MBytes  79.6 Mbits/sec  6831
[  5]   4.00-5.01   sec  9.60 MBytes  80.2 Mbits/sec  6896
[  5]   5.01-6.00   sec  9.55 MBytes  80.7 Mbits/sec  6858
[  5]   6.00-7.00   sec  9.47 MBytes  79.3 Mbits/sec  6804
[  5]   7.00-8.00   sec  9.59 MBytes  80.7 Mbits/sec  6891
[  5]   8.00-9.01   sec  9.53 MBytes  79.3 Mbits/sec  6847
[  5]   9.01-10.00  sec  9.48 MBytes  80.0 Mbits/sec  6807
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-10.00  sec  95.3 MBytes  79.9 Mbits/sec  0.000 ms  0/68451 (0%)  sender
[  5]   0.00-10.04  sec  95.7 MBytes  79.9 Mbits/sec  0.044 ms  0/68451 (0%)  receiver

iperf3 -u -b 80M -p 17001 -c cptspeedtest.cisp.co.za -O 2
[ ID] Interval           Transfer     Bitrate         Total Datagrams
[  5]   0.00-1.00   sec  9.49 MBytes  79.6 Mbits/sec  6819  (omitted)
[  5]   1.00-2.01   sec  9.54 MBytes  79.6 Mbits/sec  6853  (omitted)
[  5]   0.00-1.00   sec  9.57 MBytes  80.1 Mbits/sec  6871
[  5]   1.00-2.01   sec  9.58 MBytes  79.9 Mbits/sec  6882
[  5]   2.01-3.01   sec  9.52 MBytes  80.0 Mbits/sec  6834
[  5]   3.01-4.00   sec  9.53 MBytes  80.5 Mbits/sec  6843
[  5]   4.00-5.01   sec  9.55 MBytes  79.6 Mbits/sec  6856
[  5]   5.01-6.00   sec  9.56 MBytes  80.7 Mbits/sec  6867
[  5]   6.00-7.01   sec  9.54 MBytes  79.3 Mbits/sec  6852
[  5]   7.01-8.00   sec  9.47 MBytes  80.0 Mbits/sec  6801
[  5]   8.00-9.01   sec  9.60 MBytes  80.1 Mbits/sec  6897
[  5]   9.01-10.00  sec  9.47 MBytes  80.0 Mbits/sec  6800
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-10.00  sec  95.4 MBytes  80.0 Mbits/sec  0.000 ms  0/68503 (0%)  sender
[  5]   0.00-10.05  sec  95.8 MBytes  80.0 Mbits/sec  0.064 ms  0/68503 (0%)  receiver

@PBCool @TheRoDent If possible, wouldn't it make sense to sticky the latest troubleshooting tools with some instructions to the first post of the thread? Things like iperf, PingPlotter, etc.
Good suggestion, I've created an iPerf test thread, will find out if someone can sticky it. @rpm or @Jan ?

 

TheRoDent

Cool Ideas Rep
Joined
Aug 6, 2003
Messages
5,962
@TheRoDent are you sure you guys use CGNAT on Vuma Reach and that I can request a Public IP address. Because I logged the ticket and one of your support consultants contacted me saying you don’t and that all your clients have public IP addresses. He also said he spoke to the engineers there and nobody has any idea of what I’m talking about. He said I should screenshot the post where you said I can contact support to request a Public IP address.
Hi, do you have a ticket number for me, and I'll follow up with the agent. Yes, we do use CGNAT for the Vuma Reach base, and yes, you can request a public IP.
 

SplaT

Well-Known Member
Joined
Feb 12, 2008
Messages
237
That's odd. I swapped cables and stuff and I narrowed it down to a faulty router.
So I updated the router firmware, boom. 0.08% packet loss.

How a firmware update fixed packet loss is beyond me. I was almost ready to just order a new router.

But thanks for the help everyone!

This is my iperf test bypassing the router and plugging my PC directly into the ONT.
I'm assuming this means it's my router that's screwed and nothing to do with CISP?

0.066% packet loss is a teensy bit better than 48%, I would say...

Code:
C:\iperf>iperf3 -u -b 90M -O2 -t 10 -p 17001 -c cptspeedtest.cisp.co.za
Connecting to host cptspeedtest.cisp.co.za, port 17001
[  4] local 155.93.162.118 port 51910 connected to 154.0.15.181 port 17001
[ ID] Interval           Transfer     Bandwidth       Total Datagrams
[  4]   0.00-1.01   sec  9.90 MBytes  82.5 Mbits/sec  1267  (omitted)
[  4]   1.01-2.00   sec  10.7 MBytes  90.1 Mbits/sec  1370  (omitted)
[  4]   0.00-1.01   sec  10.6 MBytes  88.4 Mbits/sec  1362
[  4]   1.01-2.00   sec  10.7 MBytes  90.0 Mbits/sec  1367
[  4]   2.00-3.00   sec  10.9 MBytes  91.6 Mbits/sec  1391
[  4]   3.00-4.01   sec  10.6 MBytes  88.5 Mbits/sec  1359
[  4]   4.01-5.00   sec  11.0 MBytes  93.3 Mbits/sec  1414
[  4]   5.00-6.01   sec  10.4 MBytes  86.7 Mbits/sec  1331
[  4]   6.01-7.00   sec  11.0 MBytes  93.0 Mbits/sec  1411
[  4]   7.00-8.01   sec  10.4 MBytes  87.0 Mbits/sec  1335
[  4]   8.01-9.01   sec  10.8 MBytes  90.5 Mbits/sec  1387
[  4]   9.01-10.00  sec  10.8 MBytes  91.2 Mbits/sec  1380
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-10.00  sec   107 MBytes  90.0 Mbits/sec  0.326 ms  9/13737 (0.066%)
[  4] Sent 13737 datagrams
 

TheRoDent

Cool Ideas Rep
Joined
Aug 6, 2003
Messages
5,962
Please chat to her - my issue very clearly isn't fixed.
I have. Your connection is up, but you want to know what the root cause of the issue was. At this point, we do not know.

If it reoccurs, with a CISP supplied router, with our standard default configuration on it, we will escalate the matter to MTN, to see why there appears to be a stale session, and why a new PPPoE connection cannot be established. This could however take quite some time and we'd have to leave the stale session in it's stale state until they have concluded their investigation.

We do not have this issue with any other MTN customers, using the same infrastructure, so if it was a common thing we would have had many more incidents of it due to all the loadshedding.

If the situation re-occurs please re-open the ticket.
 

TheRoDent

Cool Ideas Rep
Joined
Aug 6, 2003
Messages
5,962
That's odd. I swapped cables and stuff and I narrowed it down to a faulty router.
So I updated the router firmware, boom. 0.08% packet loss.

How a firmware update fixed packet loss is beyond me. I was almost ready to just order a new router.

But thanks for the help everyone!
For interest, was it one our TP-Links ?
 

SplaT

Well-Known Member
Joined
Feb 12, 2008
Messages
237
For interest, was it one our TP-Links ?

No, it's an Archer C6. I signed up to CISP way back and got a router that only supported 100Mpbs ports. I have since upgraded the line to 200Mbps so I bought a new router that supported gigabit ethernet.

Although I might have spoken too soon, uploads are still slow. But at least I know where the issue is now and it's something I can fix myself.
 

MDKza

Senior Member
Joined
May 24, 2012
Messages
732
I have. Your connection is up, but you want to know what the root cause of the issue was. At this point, we do not know.

If it reoccurs, with a CISP supplied router, with our standard default configuration on it, we will escalate the matter to MTN, to see why there appears to be a stale session, and why a new PPPoE connection cannot be established. This could however take quite some time and we'd have to leave the stale session in it's stale state until they have concluded their investigation.

We do not have this issue with any other MTN customers, using the same infrastructure, so if it was a common thing we would have had many more incidents of it due to all the loadshedding.

If the situation re-occurs please re-open the ticket.

Wow... Okay then, nevermind the fact it doesn't work with any router at all :ROFL:
 

TheRoDent

Cool Ideas Rep
Joined
Aug 6, 2003
Messages
5,962
Wow... Okay then, nevermind the fact it doesn't work with any router at all :ROFL:
Well, it currently works, your session is up we can ping you and according to Tayla you could browse ?

If it reoccurs we have to go down to a standard "known" configuration, with our router and see if it re-occurs.
 

Lepep

Member
Joined
Apr 4, 2018
Messages
21
BAHRAIN LATENCY TO AWS

I have noticed a latency of 125ms to Bahrain and it got me playing VALORANT again (it did feel better than EU, especially with no packet loss). I know Bahrain game servers are dead in other games but I was able to consistently find games in VALORANT.

I still had my usual 160ms to EU as well, if I needed it for Apex where Bahrain is dead, but now the ping to Bahrain is back to 260ms, but why?
Why can't there be the best of both worlds?
 

PBCool

Cool Ideas
Company Rep
Joined
Jan 11, 2016
Messages
11,813
BAHRAIN LATENCY TO AWS

I have noticed a latency of 125ms to Bahrain and it got me playing VALORANT again (it did feel better than EU, especially with no packet loss). I know Bahrain game servers are dead in other games but I was able to consistently find games in VALORANT.

I still had my usual 160ms to EU as well, if I needed it for Apex where Bahrain is dead, but now the ping to Bahrain is back to 260ms, but why?
Why can't there be the best of both worlds?
Nothing we have changed so down to AWS and their transit.
 

CrypticZA

Expert Member
Joined
Sep 21, 2019
Messages
2,270
Nothing we have changed so down to AWS and their transit.
I assume no feedback from them about getting their capacity up on WACS? Going to assume they probably blaming Covid and all even though they ran perfect for a few days on it when EASSY had troubles
 

PBCool

Cool Ideas
Company Rep
Joined
Jan 11, 2016
Messages
11,813
I assume no feedback from them about getting their capacity up on WACS? Going to assume they probably blaming Covid and all even though they ran perfect for a few days on it when EASSY had troubles
Yeah it's tricky, I imagine they are awaiting more capacity and the feedback I have from the market is that there isn't any, they are awaiting a WACs and Eassy upgrade.
 
Top