Status
Not open for further replies.
+1

However something you ned to keep in mind, in the UK the ISPs have more control over the customer routers, where in SA customer still use whatever they please, so many a time, routers are not pingable at all (customers believe blocking pings = security).

So there might be still room for errors for this in SA.

Yeap exactly most routers these days are shipped with ICMP disabled. But not a bad idea.

Just to clarify on this, when I was in the UK, I was on ADSL with various ISP's for around 10 years and never had the router managed by an ISP. With the particular ISP in question, customers just agreed to allow ping from the WAN port only. The more paranoid customers also filtered the ICMP traffic to only allow the ping servers to ping the WAN port.

When they delivered a router, it was set this way by default and any new customer was asked to enable ping to facilitate the monitoring.
 
It all depends on how long it takes CC and Frogfoot take to configure and handover the line. The default router is a WR840N
Thanks for that info.

Yesterday CISP connect told me, "Frogfoot have a standard 4-6 week installation estimation period. At this time the status is build in progress. I will try get some more accurate date."

Which is kind of a crazy generic response to give me considering the fibre is physically laid, and today the ONT has been installed by CCC. All that now remains is for CISP to send me the WR840N fibre wifi router.
 
Last edited:
Thanks for that info.

Yesterday CISP support told me, "Frogfoot have a standard 4-6 week installation estimation period. At this time the status is build in progress. I will try get some more accurate date."

Which is kind of a crazy generic response to give me considering the fibre is physically laid, and today the ONT has been installed by CCC. All that now remains is for CISP to send me the WR840N fibre wifi router.

Not as simple as that unfortunately, Frogfoot need to hand the line over to us which means the backend and backhaul is completed. As soon as they do we would send out and provision the account. It may take far less but this is the average time we have seen from Frogfoot.
 
Not as simple as that unfortunately, Frogfoot need to hand the line over to us which means the backend and backhaul is completed. As soon as they do we would send out and provision the account. It may take far less but this is the average time we have seen from Frogfoot.
Eish... so i should hold off on giving my 30 days notice on cancelling my ADSL and telkom line?
 
Eish... so i should hold off on giving my 30 days notice on cancelling my ADSL and telkom line?
Just keep following up with our connect team every few days and see if they have feedback.
 
@PBCool ping is very high in game right now. Its definitely a cool ideas issue as my friends connection is fine on another isp!!!! This is horrible

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 8 | 442 | 408 | 0 | 0 | 0 | 0 |
| 155.93.141.1 - 0 | 577 | 577 | 1 | 4 | 245 | 2 |
| 154.0.1.177 - 0 | 577 | 577 | 1 | 5 | 266 | 2 |
| 154.0.2.33 - 0 | 577 | 577 | 1 | 5 | 244 | 2 |
| 154.0.1.138 - 0 | 577 | 577 | 1 | 6 | 246 | 2 |
| cdns1.cisp.co.za - 0 | 577 | 577 | 1 | 6 | 247 | 2 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Last edited:
@PBCool

Why is the routing for aws going through joburg in cpt?

E.g. EU Fornite server ip trace:

Code:
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     1 ms     1 ms     1 ms  155.93.248.1
  3     1 ms    <1 ms    <1 ms  154.0.1.125
  4     1 ms     1 ms     1 ms  154.0.1.13
  5    21 ms    20 ms    20 ms  154.0.1.245
  6    21 ms    21 ms    21 ms  154.0.3.86
  7    21 ms    21 ms    21 ms  154.0.3.26
  8    21 ms    21 ms    21 ms  52.95.106.74
  9    21 ms    21 ms    21 ms  52.93.56.8
 10    21 ms    21 ms    21 ms  52.93.56.21
 11   194 ms   192 ms   192 ms  54.239.46.76
 12   192 ms   192 ms   193 ms  54.239.46.85
 13     *        *        *     Request timed out.
 14   194 ms   192 ms   193 ms  54.239.44.142
 15     *        *        *     Request timed out.
 16   199 ms   219 ms   223 ms  52.93.6.188
 17   192 ms   192 ms   192 ms  52.93.101.51
 18   198 ms   235 ms   225 ms  52.93.101.26
 19   193 ms   195 ms   192 ms  52.93.7.135
 20   191 ms   191 ms   191 ms  178.236.0.109
 21     *        *        *     Request timed out.
 
@PBCool ping is very high in game right now. Its definitely a cool ideas issue as my friends connection is fine on another isp!!!! This is horrible

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 8 | 442 | 408 | 0 | 0 | 0 | 0 |
| 155.93.141.1 - 0 | 577 | 577 | 1 | 4 | 245 | 2 |
| 154.0.1.177 - 0 | 577 | 577 | 1 | 5 | 266 | 2 |
| 154.0.2.33 - 0 | 577 | 577 | 1 | 5 | 244 | 2 |
| 154.0.1.138 - 0 | 577 | 577 | 1 | 6 | 246 | 2 |
| cdns1.cisp.co.za - 0 | 577 | 577 | 1 | 6 | 247 | 2 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Which game? You can see the IP spikes are on your first hop which is over the fibre providers network to us will you log a support ticket?
 
@PBCool

Why is the routing for aws going through joburg in cpt?

E.g. EU Fornite server ip trace:

Code:
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     1 ms     1 ms     1 ms  155.93.248.1
  3     1 ms    <1 ms    <1 ms  154.0.1.125
  4     1 ms     1 ms     1 ms  154.0.1.13
  5    21 ms    20 ms    20 ms  154.0.1.245
  6    21 ms    21 ms    21 ms  154.0.3.86
  7    21 ms    21 ms    21 ms  154.0.3.26
  8    21 ms    21 ms    21 ms  52.95.106.74
  9    21 ms    21 ms    21 ms  52.93.56.8
 10    21 ms    21 ms    21 ms  52.93.56.21
 11   194 ms   192 ms   192 ms  54.239.46.76
 12   192 ms   192 ms   193 ms  54.239.46.85
 13     *        *        *     Request timed out.
 14   194 ms   192 ms   193 ms  54.239.44.142
 15     *        *        *     Request timed out.
 16   199 ms   219 ms   223 ms  52.93.6.188
 17   192 ms   192 ms   192 ms  52.93.101.51
 18   198 ms   235 ms   225 ms  52.93.101.26
 19   193 ms   195 ms   192 ms  52.93.7.135
 20   191 ms   191 ms   191 ms  178.236.0.109
 21     *        *        *     Request timed out.

Our direct connect with Amazon is now up in JHB.
 
Our direct connect with Amazon is now up in JHB.

Oh ok. Any eta on the direct connect for cpt? This routing through joburg is significantly higher, before i was getting 153-155ms~ to aws eu and now its 190ms.
 
Oh ok. Any eta on the direct connect for cpt? This routing through joburg is significantly higher, before i was getting 153-155ms~ to aws eu and now its 190ms.
It's in discussions, not a major demand in CT for AWS direct connect as yet, we can just reroute it as normal.
 
Has anyone received their CISP statement yet? Have not received mine and have checked spam folders where it has been known to lurk in the past. Nothing on the cool zone either.
 
Has anyone received their CISP statement yet? Have not received mine and have checked spam folders where it has been known to lurk in the past. Nothing on the cool zone either.

Also nothing received. Maybe a free month for loyal subscribers?
 
Has anyone received their CISP statement yet? Have not received mine and have checked spam folders where it has been known to lurk in the past. Nothing on the cool zone either.
Batch run delay, it will be this morning.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X