Cool Ideas Fibre ISP - Feedback

[chopsky]

Hi, still massive issues with Octotel in CT? Our internet is completely screwed. Sites not loading...

 

[Yster21]

Did you see the maintenance notice for London last night on our networks page? This was specific to last night though.

Hi PBCool. No I did not see that.

My issue had more to do with the spikey latency that's ubiquitous in the evenings. It's probably a Vumatel issue. It wasn't always like this.

 

[DrJohnZoidberg]

Let's compare after tomorrow and see.

Thanks. After tomorrow as in tomorrow?

 

[newb5000]

Hi @PBCool ,

I can't seem to access www.absa.co.za or speedtest.net at all using my new CISP account. The network provider is Metro Fibre. The cool zone network status page does not indicate that there are any issues.

I opened ticket COOL-20180822-137300 in this regard.

Traceroute to ABSA:

$ traceroute www.absa.co.za
traceroute: Warning: www.absa.co.za has multiple addresses; using
54.77.160.153
traceroute to absa-prod-front-alb2-1785404226.eu-west-1.elb.amazonaws.com
(54.77.160.153), 64 hops max, 52 byte packets
1 router.asus.com (10.0.1.1) 2.735 ms 2.479 ms 2.369 ms
2 154.0.0.120 (154.0.0.120) 5.413 ms 4.774 ms 4.604 ms
3 154.0.4.210 (154.0.4.210) 4.592 ms 4.903 ms 4.628 ms
4 154.0.4.82 (154.0.4.82) 4.962 ms 4.923 ms 4.647 ms
5 196-60-9-105.ixp.joburg (196.60.9.105) 4.754 ms 5.041 ms 4.847 ms
6 52.93.56.104 (52.93.56.104) 5.564 ms
  52.93.56.8 (52.93.56.8) 5.983 ms
  52.93.56.56 (52.93.56.56) 5.654 ms
7 52.93.56.65 (52.93.56.65) 5.293 ms
  52.93.56.117 (52.93.56.117) 6.373 ms
  52.93.56.53 (52.93.56.53) 5.268 ms
8 54.239.46.76 (54.239.46.76) 178.577 ms
  54.239.46.72 (54.239.46.72) 173.243 ms
  54.239.46.78 (54.239.46.78) 176.459 ms
9 54.239.46.87 (54.239.46.87) 177.371 ms 178.704 ms
  54.239.46.85 (54.239.46.85) 178.998 ms
10 * * *
11 54.239.44.140 (54.239.44.140) 175.384 ms
   54.239.44.142 (54.239.44.142) 179.596 ms 173.603 ms
12 * * *
13 52.93.6.180 (52.93.6.180) 200.062 ms
   52.93.6.184 (52.93.6.184) 205.711 ms
   52.93.6.148 (52.93.6.148) 181.700 ms
14 52.93.101.45 (52.93.101.45) 177.226 ms
   52.93.101.21 (52.93.101.21) 175.160 ms
   52.93.101.11 (52.93.101.11) 175.074 ms
15 52.93.101.26 (52.93.101.26) 179.595 ms
   52.93.101.48 (52.93.101.48) 179.840 ms
   52.93.101.30 (52.93.101.30) 174.078 ms
16 52.93.7.63 (52.93.7.63) 177.378 ms
   52.93.7.79 (52.93.7.79) 174.542 ms
   52.93.7.73 (52.93.7.73) 172.491 ms
17 * * *
18 * * *
19 * * *
20 * * *

 

[PBCool]

Thanks. After tomorrow as in tomorrow?

After tomorrows change, the day before the day after tomorrow.

 

[PBCool]

Also the Octotel change has been done, so please test and let me know.

 

[DrJohnZoidberg]

Also the Octotel change has been done, so please test and let me know.

My connection died momentarily a little while ago but doesn't look like anything changed after that.

Actually looks like my latency got slightly worse.

 

[MDE]

Also the Octotel change has been done, so please test and let me know.

Thanks.. Looks alot better from my side. Getting 140ms to London Vodafone.

See you changed Mikrotik devices.

 

[rash1233]

Mines looking a lot better, back to 144 ping and good speeds to Vodafone London

On Octotel 100/100

 

[Tinuva]

It means Vodacom are preffing the JHB peer, so will tweak today with some deaggs.

Thank you, I see its routing through cape town now.

 

[DrJohnZoidberg]

Ahh there we go, much better!



London test also looking good again.

Thanks @PBCool!

 

[Phinix]

@PBCool

I have noticed that google.co.za seems to toss and turn between two IPs.

I'm in Cape Town and this one 216.58.223.99 averages around 70ms while this one 216.58.223.35 averages around 22ms.

Any reason for it constantly and randomly switching between these?

 

[PBCool]

Ahh there we go, much better!



London test also looking good again.

Thanks @PBCool!

Cool we still have some tweaking to do, but for the most part performance should be better.

 

[PBCool]

Thank you, I see its routing through cape town now.

Sort off, it looks like Vodacom are load balancing via JHB and CPT now, I have asked them to look into it.

 

[image132]

Yup mine looks a whole lot better too, thank you.

What did you change PBcool?

 

[PBCool]

Yup mine looks a whole lot better too, thank you.

What did you change PBcool?

Great, we changed an access router, because there are more than one it makes it relatively difficult to narrow down, seems to be a faulty interface.

 

[blacklung]

Cool we still have some tweaking to do, but for the most part performance should be better.

International not so great here :

Local at least there / there abouts. ( 200/200 Octotel West Beach CT )

 

[image132]

Great, we changed an access router, because there are more than one it makes it relatively difficult to narrow down, seems to be a faulty interface.

Mine is still holding so it may have worked. The true test is going be at 8-9pm though, that's usually when it was at its worst. I will report back then, in the meantime thanks for the effort PBcool.

 

[stefan9]

Still having issues with subpar intertional tcp speeds. Ticket COOL-20180711-122832
Local speeds and international udp performs at +- line speeds but tcp is barely reaching 40mbps...
This is on frogfoot.

 

[dotdan]

Hi PBcool, as mentioned in the PM, here is two screenshots of in game stats. One connected to router, the other directly in CPE box. The one does have a lower latency, but still at least out with 80-100ms.