Cool Ideas Fibre ISP – Feedback Thread 2

Loppas · Jun 22, 2019

image132 said:
I'm in CPT. I'm assuming all the people that live in JHB have no issues as they don't have to get routed outside of their city to connect to the server. It looks to me very much like I'm being routed through EU to get to the jhb discord server.

I'm in CPT and I haven't seen the same high latency to za. I'm testing it by connecting to my friends discord group under voice channel.

image132 · Jun 22, 2019

underdose said:
You can get the IP addresss for Discord server you're connected to by tracerouting to servername.discord.gg (according to this article). In your case that would be

Code:

traceroute southafrica579.discord.gg traceroute to southafrica579.discord.gg (185.179.201.104), 30 hops max, 38 byte packets

and

Code:

traceroute eu-west225.discord.gg traceroute to eu-west225.discord.gg (88.202.186.153), 30 hops max, 38 byte packets

Thanks for that.

PBCool said:
Yeah I can see the issue I just need to engineer the preference of the local peer, I have started doing this already.

Thank you. If it helps at all underdose corrected me and as it turns out I can give you my route to that server:

MTR to southafrica579.discord.gg

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         router.asus.com -    0 |   11 |   11 |    0 |    0 |    0 |    0 |
|                             154.0.0.246 -    0 |   11 |   11 |    0 |    0 |    1 |    0 |
|                             154.0.4.162 -    0 |   11 |   11 |    0 |    0 |    1 |    1 |
|                      de-cix.nyc.i3d.net -    0 |   11 |   11 |  190 |  190 |  190 |  190 |
|              10ge.nlrtm1-rt002i.i3d.net -    0 |   11 |   11 |  265 |  265 |  266 |  265 |
|         60ge.ar0-cr1.nikhef.ams.i3d.net -    0 |   11 |   11 |  276 |  450 |  485 |  478 |
|    1ge.zajnb1-rt001i.teraco-jb1.i3d.net -    0 |   11 |   11 |  233 |  236 |  269 |  233 |
|                       hosted-by.i3d.net -    0 |   11 |   11 |  233 |  233 |  233 |  233 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Looks like its going to New York which is pretty funny and impressive its only 190 ping to it.

Seeyou · Jun 22, 2019

Google services still being routed overseas:

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |   15 |   15 |    0 |    0 |    0 |    0 |
|                             154.0.0.246 -    0 |   15 |   15 |    0 |    0 |    1 |    0 |
|                             154.0.4.162 -    0 |   15 |   15 |    0 |    0 |    2 |    0 |
|          core1-0-2-0.lga.net.google.com -    0 |   15 |   15 |  198 |  199 |  211 |  198 |
|                          108.170.248.52 -    0 |   15 |   15 |  216 |  216 |  218 |  218 |
|                          216.239.58.111 -    0 |   15 |   15 |  220 |  220 |  222 |  220 |
|                          172.253.65.167 -    0 |   15 |   15 |  216 |  216 |  218 |  216 |
|                          216.239.58.130 -    0 |   15 |   15 |  216 |  216 |  221 |  216 |
|                          172.253.67.158 -    0 |   15 |   15 |  216 |  216 |  217 |  216 |
|                          74.125.245.193 -    0 |   15 |   15 |  216 |  216 |  217 |  216 |
|                          172.253.65.249 -    0 |   15 |   15 |  216 |  217 |  229 |  217 |
|                jnb02s03-in-f3.1e100.net -    0 |   15 |   15 |  216 |  216 |  217 |  216 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

ajan · Jun 22, 2019

Anyone else getting massively bad ping?

https://imgur.com/4Ij3j8p

https://imgur.com/J2ReK9N

image132 · Jun 22, 2019

ajan said:
Anyone else getting massively bad ping?

https://imgur.com/4Ij3j8p

https://imgur.com/J2ReK9N

You in Cape Town?

CISP's new peering has clearly caused routing issues for us. I'm pretty sure they're aware of it though and are fixing it.

That being said I personally don't have issues to Valve's JHB server:

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         router.asus.com -    0 |   11 |   11 |    0 |    0 |    0 |    0 |
|                             154.0.0.246 -    0 |   11 |   11 |    0 |    0 |    1 |    0 |
|                             154.0.4.162 -    0 |   11 |   11 |    0 |    0 |    1 |    0 |
|                            196.26.90.82 -    0 |   11 |   11 |    2 |    2 |    2 |    2 |
|     mi-za-cpt-p7-te0-7-0-0.ip.isnet.net -    0 |   11 |   11 |    2 |    2 |    4 |    2 |
|                         168.209.100.101 -    0 |   11 |   11 |   17 |   17 |   18 |   17 |
|                            196.38.180.1 -    0 |   11 |   11 |   17 |   17 |   21 |   18 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Loppas · Jun 22, 2019

@ajan @image132

Weird how people in cpt are seeing different routing. I'm on vumatel, but could also be that im on the gigabit ip range (102.132.X.X) as well.

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |    3 |    3 |    0 |    0 |    0 |    0 |
|                           102.132.248.1 -    0 |    3 |    3 |    2 |    4 |    5 |    2 |
|                         102.132.175.109 -    0 |    3 |    3 |    1 |    1 |    1 |    1 |
|                             154.0.1.249 -    0 |    3 |    3 |   16 |   16 |   16 |   16 |
|                             154.0.5.133 -    0 |    3 |    3 |   16 |   16 |   16 |   16 |
|                         i3d.jinx.net.za -    0 |    3 |    3 |   17 |   23 |   36 |   36 |
|                       hosted-by.i3d.net -    0 |    3 |    3 |   17 |   17 |   17 |   17 |
|________________________________________________|______|______|______|______|______|______|

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |    5 |    5 |    0 |    0 |    0 |    0 |
|                           102.132.248.1 -    0 |    5 |    5 |    2 |    2 |    5 |    2 |
|                         102.132.175.109 -    0 |    5 |    5 |    0 |    0 |    1 |    0 |
|                             154.0.1.233 -    0 |    5 |    5 |   16 |   16 |   17 |   16 |
|                             154.0.1.138 -    0 |    5 |    5 |   16 |   16 |   17 |   16 |
|                          197.96.214.112 -    0 |    5 |    5 |   18 |   21 |   29 |   20 |
|                           168.209.1.165 -    0 |    5 |    5 |   17 |   17 |   18 |   17 |
|                            196.38.180.1 -    0 |    5 |    5 |   17 |   19 |   25 |   17 |
|________________________________________________|______|______|______|______|______|______|

Phinix · Jun 22, 2019

@PBCool Please fix your routing.

5.200.8.222 is messed up and is giving 230ms, while on vox (and used to be on CI) it is 152ms.

PBCool · Jun 22, 2019

Phinix said:
@PBCool Please fix your routing.

5.200.8.222 is messed up and is giving 230ms, while on vox (and used to be on CI) it is 152ms.

Yeah aware of it, busy with it.

PBCool · Jun 22, 2019

Phinix said:
@PBCool Please fix your routing.

5.200.8.222 is messed up and is giving 230ms, while on vox (and used to be on CI) it is 152ms.

Yeah aware of it, busy with it. Check again for me in a few mins.

image132 · Jun 22, 2019

Loppas said:

@ajan @image132

Weird how people in cpt are seeing different routing. I'm on vumatel, but could also be that im on the gigabit ip range (102.132.X.X) as well.

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |    3 |    3 |    0 |    0 |    0 |    0 |
|                           102.132.248.1 -    0 |    3 |    3 |    2 |    4 |    5 |    2 |
|                         102.132.175.109 -    0 |    3 |    3 |    1 |    1 |    1 |    1 |
|                             154.0.1.249 -    0 |    3 |    3 |   16 |   16 |   16 |   16 |
|                             154.0.5.133 -    0 |    3 |    3 |   16 |   16 |   16 |   16 |
|                         i3d.jinx.net.za -    0 |    3 |    3 |   17 |   23 |   36 |   36 |
|                       hosted-by.i3d.net -    0 |    3 |    3 |   17 |   17 |   17 |   17 |
|________________________________________________|______|______|______|______|______|______|

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |    5 |    5 |    0 |    0 |    0 |    0 |
|                           102.132.248.1 -    0 |    5 |    5 |    2 |    2 |    5 |    2 |
|                         102.132.175.109 -    0 |    5 |    5 |    0 |    0 |    1 |    0 |
|                             154.0.1.233 -    0 |    5 |    5 |   16 |   16 |   17 |   16 |
|                             154.0.1.138 -    0 |    5 |    5 |   16 |   16 |   17 |   16 |
|                          197.96.214.112 -    0 |    5 |    5 |   18 |   21 |   29 |   20 |
|                           168.209.1.165 -    0 |    5 |    5 |   17 |   17 |   18 |   17 |
|                            196.38.180.1 -    0 |    5 |    5 |   17 |   19 |   25 |   17 |
|________________________________________________|______|______|______|______|______|______|

There's a special IP range for gigabit users? Why?

PBCool · Jun 22, 2019

image132 said:
There's a special IP range for gigabit users? Why?

It's not special, just a different part of the network that we pickup Vumatels NNI.

Gambit · Jun 22, 2019

Seeing strange routing to SAIX servers in Cape Town and Joburg from my CI connection on Vumatel in Cape Town.

Bash:

traceroute to capetown.spdtst.saix.net (196.25.37.14), 64 hops max, 52 byte packets
 1  192.168.10.254 (192.168.10.254)  0.579 ms  0.339 ms  0.219 ms
 2  102.132.248.1 (102.132.248.1)  4.496 ms  2.332 ms  2.324 ms
 3  102.132.175.109 (102.132.175.109)  1.190 ms  1.121 ms  0.972 ms
 4  cd-backbone.coolideas.co.za (154.0.1.13)  1.370 ms  1.233 ms  1.172 ms
 5  c1l-backbone.coolideas.co.za (154.0.2.57)  1.463 ms  1.313 ms  1.297 ms
 6  154.0.4.158 (154.0.4.158)  141.130 ms  141.102 ms  141.006 ms
 7  u102-cust.coolideas.co.za (154.0.5.18)  141.403 ms  141.049 ms  141.099 ms
 8  lon-ip-hsll-1.telkom-ipnet.co.za (195.66.226.42)  141.997 ms  142.244 ms  143.983 ms
 9  * * *
10  * * *
11  wblv-ip-hsll-1-gig-0-0-0.telkom-ipnet.co.za (196.43.39.62)  298.899 ms
    196.43.39.58 (196.43.39.58)  301.446 ms
    wblv-ip-hsll-1-gig-0-0-0.telkom-ipnet.co.za (196.43.39.62)  298.552 ms
12  196.25.37.2 (196.25.37.2)  298.136 ms !X *  298.005 ms !X

Bash:

PING capetown.spdtst.saix.net (196.25.37.14): 56 data bytes
64 bytes from 196.25.37.14: icmp_seq=0 ttl=49 time=301.945 ms
64 bytes from 196.25.37.14: icmp_seq=1 ttl=49 time=301.526 ms
64 bytes from 196.25.37.14: icmp_seq=2 ttl=49 time=301.587 ms
64 bytes from 196.25.37.14: icmp_seq=3 ttl=49 time=301.476 ms

blunt · Jun 22, 2019

Gambit said:

Seeing strange routing to SAIX servers in Cape Town and Joburg from my CI connection on Vumatel in Cape Town.

Bash:

traceroute to capetown.spdtst.saix.net (196.25.37.14), 64 hops max, 52 byte packets
1  192.168.10.254 (192.168.10.254)  0.579 ms  0.339 ms  0.219 ms
2  102.132.248.1 (102.132.248.1)  4.496 ms  2.332 ms  2.324 ms
3  102.132.175.109 (102.132.175.109)  1.190 ms  1.121 ms  0.972 ms
4  cd-backbone.coolideas.co.za (154.0.1.13)  1.370 ms  1.233 ms  1.172 ms
5  c1l-backbone.coolideas.co.za (154.0.2.57)  1.463 ms  1.313 ms  1.297 ms
6  154.0.4.158 (154.0.4.158)  141.130 ms  141.102 ms  141.006 ms
7  u102-cust.coolideas.co.za (154.0.5.18)  141.403 ms  141.049 ms  141.099 ms
8  lon-ip-hsll-1.telkom-ipnet.co.za (195.66.226.42)  141.997 ms  142.244 ms  143.983 ms
9  * * *
10  * * *
11  wblv-ip-hsll-1-gig-0-0-0.telkom-ipnet.co.za (196.43.39.62)  298.899 ms
    196.43.39.58 (196.43.39.58)  301.446 ms
    wblv-ip-hsll-1-gig-0-0-0.telkom-ipnet.co.za (196.43.39.62)  298.552 ms
12  196.25.37.2 (196.25.37.2)  298.136 ms !X *  298.005 ms !X

Bash:

PING capetown.spdtst.saix.net (196.25.37.14): 56 data bytes
64 bytes from 196.25.37.14: icmp_seq=0 ttl=49 time=301.945 ms
64 bytes from 196.25.37.14: icmp_seq=1 ttl=49 time=301.526 ms
64 bytes from 196.25.37.14: icmp_seq=2 ttl=49 time=301.587 ms
64 bytes from 196.25.37.14: icmp_seq=3 ttl=49 time=301.476 ms

Same roundabout routing here though a bit better pings (CI on MTN)

Code:

PING capetown.spdtst.saix.net (196.25.37.14): 56 data bytes
64 bytes from 196.25.37.14: icmp_seq=0 ttl=55 time=150.765 ms
64 bytes from 196.25.37.14: icmp_seq=1 ttl=55 time=155.608 ms
64 bytes from 196.25.37.14: icmp_seq=2 ttl=55 time=146.805 ms
64 bytes from 196.25.37.14: icmp_seq=3 ttl=55 time=159.440 ms
64 bytes from 196.25.37.14: icmp_seq=4 ttl=55 time=146.106 ms

Code:

traceroute to capetown.spdtst.saix.net (196.25.37.14), 64 hops max, 52 byte packets
1  router.ibox.za.net (10.23.23.1)  2.206 ms  3.377 ms  4.244 ms
2  u33m-cust.coolideas.co.za (154.0.15.178)  4.836 ms  4.213 ms  4.088 ms
3  u33l-cust.coolideas.co.za (154.0.15.177)  4.284 ms  3.750 ms  4.034 ms
4  uwy-cust.coolideas.co.za (154.0.4.162)  4.135 ms  7.291 ms  10.121 ms
5  uvu-cust.coolideas.co.za (154.0.4.122)  144.950 ms  144.572 ms  143.965 ms
6  u102-cust.coolideas.co.za (154.0.5.18)  144.656 ms  144.673 ms  144.553 ms
7  lon-ip-hsll-1.telkom-ipnet.co.za (195.66.226.42)  146.610 ms  145.266 ms  145.150 ms
8  10.189.30.1 (10.189.30.1)  147.005 ms  146.770 ms  145.758 ms
9  10.189.10.2 (10.189.10.2)  145.929 ms  146.175 ms  147.214 ms
10  196.43.39.58 (196.43.39.58)  148.523 ms  147.020 ms
    wblv-ip-hsll-1-gig-0-0-0.telkom-ipnet.co.za (196.43.39.62)  148.107 ms
11  196.25.37.2 (196.25.37.2)  146.607 ms !X *  146.339 ms !X

Phinix · Jun 22, 2019

PBCool said:
Yeah aware of it, busy with it. Check again for me in a few mins.

No change:

PBCool · Jun 22, 2019

Made some changes check Google etc for me again.

Orihalcon · Jun 22, 2019

Connection just died. Brackenfell Vuma trenched. Anyone else?

image132 · Jun 23, 2019

PBCool said:
Made some changes check Google etc for me again.

Discord back to what it should be. Thank you

Phinix · Jun 23, 2019

PBCool said:
Made some changes check Google etc for me again.

Back to normal it seems:

wir · Jun 23, 2019

No connection this morning in Bloemfontein, Langenhovenpark - Frogfoot network.

Log on router reads “ppp2 Timeout waiting for PADO packets”

PBCool · Jun 23, 2019

wir said:
No connection this morning in Bloemfontein, Langenhovenpark - Frogfoot network.

Log on router reads “ppp2 Timeout waiting for PADO packets”

If there's nothing on announcements please log as normal.

Cool Ideas Fibre ISP – Feedback Thread 2

Senior Member

Expert Member

Expert Member

Senior Member

Expert Member

Senior Member

Expert Member

Cool Ideas Rep

Cool Ideas Rep

Expert Member

Cool Ideas Rep

Expert Member

Expert Member

Expert Member

Cool Ideas Rep

Expert Member

Expert Member

Expert Member

Well-Known Member

Cool Ideas Rep