Cool Ideas Fibre ISP - Feedback

Status
Not open for further replies.
International, she is broken.



Code: 
Tracing route to speedtest.vodafone-ip.de [145.253.248.206]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  155.93.250.1
  2     2 ms     2 ms     2 ms  wc-grwf-ars1-vl1701.enetworks.net [45.220.191.17]
  3     2 ms     5 ms     2 ms  wc-grwf-br1-gi0-3-3203.enetworks.net [45.220.129.84]
  4     3 ms     2 ms     2 ms  41.60.242.1
  5   146 ms   145 ms   145 ms  ten0-0-0-7.luk-p1-tho.liquidtelecom.net [5.11.10.156]
  6   145 ms   145 ms   145 ms  be5.luk-pe1-tcy.liquidtelecom.net [5.11.10.191]
  7   211 ms   182 ms   208 ms  10ge3-10.core1.lon2.he.net [216.66.87.61]
  8   207 ms   193 ms   190 ms  100ge6-2.core1.ams1.he.net [72.52.92.214]
  9   177 ms   182 ms   178 ms  amdgw2.arcor-ip.net [80.249.208.123]
 10   183 ms   185 ms   187 ms  145.254.2.204
 11   186 ms   193 ms   190 ms  145.254.1.199
 12   189 ms     *        *     145.254.1.218
 13   191 ms   187 ms   186 ms  92.79.215.123
 14   190 ms   185 ms   183 ms  speedtest.vodafone-ip.de [145.253.248.206]
 
PBCool said:
What kind of VPN service did they offer? You can just use a dyndns service for this?
Click to expand...

It allowed me to register a site ... that would allow me to do that dyndns thing into my camera, once i opened the port on the router
 
[MENTION=394133]PBCool[/MENTION], as per my post above - all my international stuff is completely borked.

Octotel 200/200, Table view area.
 
DrJohnZoidberg said:
[MENTION=394133]PBCool[/MENTION], as per my post above - all my international stuff is completely borked.

Octotel 200/200, Table view area.
Click to expand...

Yeap also relative to carrier, have switched some traffic around and waiting for resolution.
 
So just over 24 hours and my ticket status is still "OPEN", not even a reply to say "We're working on it" - come on guys.. really?

I realise you need to get a hold of MTN - but why not let me know what's happening?

Pings started improving since this afternoon but still a consistent 40% packet loss on the first hop - every time without fail.

Code: 
HOST: VivoBox                     Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- router.ibox.xx.xx          0.0%    10    0.6   0.5   0.4   0.7   0.0
  2.|-- u2wc-cust.coolideas.co.za 40.0%    10   21.3  22.2  20.8  25.3   1.7
  3.|-- 154.0.4.30                 0.0%    10   27.5  25.6  21.4  36.9   4.5
  4.|-- unm-cust.coolideas.co.za   0.0%    10   21.4  21.5  21.2  21.8   0.0
  5.|-- ur1-cust.coolideas.co.za   0.0%    10   21.9  21.6  21.1  22.0   0.0
  6.|-- 154.0.4.45                 0.0%    10   22.5  22.1  21.6  22.5   0.0
  7.|-- c35-backbone.coolideas.co  0.0%    10   22.9  22.4  21.7  22.9   0.0
  8.|-- urm-cust.coolideas.co.za   0.0%    10   22.0  22.3  21.5  23.1   0.0
  9.|-- u2n3-cust.coolideas.co.za 10.0%    10   22.8  23.0  22.0  24.8   0.8
 
blunt said:
So just over 24 hours and my ticket status is still "OPEN", not even a reply to say "We're working on it" - come on guys.. really?

I realise you need to get a hold of MTN - but why not let me know what's happening?

Pings started improving since this afternoon but still a consistent 40% packet loss on the first hop - every time without fail.

Code: 
HOST: VivoBox                     Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- router.ibox.xx.xx          0.0%    10    0.6   0.5   0.4   0.7   0.0
  2.|-- u2wc-cust.coolideas.co.za 40.0%    10   21.3  22.2  20.8  25.3   1.7
  3.|-- 154.0.4.30                 0.0%    10   27.5  25.6  21.4  36.9   4.5
  4.|-- unm-cust.coolideas.co.za   0.0%    10   21.4  21.5  21.2  21.8   0.0
  5.|-- ur1-cust.coolideas.co.za   0.0%    10   21.9  21.6  21.1  22.0   0.0
  6.|-- 154.0.4.45                 0.0%    10   22.5  22.1  21.6  22.5   0.0
  7.|-- c35-backbone.coolideas.co  0.0%    10   22.9  22.4  21.7  22.9   0.0
  8.|-- urm-cust.coolideas.co.za   0.0%    10   22.0  22.3  21.5  23.1   0.0
  9.|-- u2n3-cust.coolideas.co.za 10.0%    10   22.8  23.0  22.0  24.8   0.8
Click to expand...

To be fair, if you're not seeing loss beyond that hop, then that device is not causing packet loss on your connections. It's just being a bit sporadic about sending you the ICMP message back for its own TTL exceeded messages, because traffic generated by/destined for a device often handles a different path, via different processors, to traffic passing through a device. So the CPU on it could be maxed out, hence it's bad at creating the ICMP error message, but the backplane that's forwarding the packets is fine.
 
blunt said:
So just over 24 hours and my ticket status is still "OPEN", not even a reply to say "We're working on it" - come on guys.. really?

I realise you need to get a hold of MTN - but why not let me know what's happening?

Pings started improving since this afternoon but still a consistent 40% packet loss on the first hop - every time without fail.

Code: 
HOST: VivoBox                     Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- router.ibox.xx.xx          0.0%    10    0.6   0.5   0.4   0.7   0.0
  2.|-- u2wc-cust.coolideas.co.za 40.0%    10   21.3  22.2  20.8  25.3   1.7
  3.|-- 154.0.4.30                 0.0%    10   27.5  25.6  21.4  36.9   4.5
  4.|-- unm-cust.coolideas.co.za   0.0%    10   21.4  21.5  21.2  21.8   0.0
  5.|-- ur1-cust.coolideas.co.za   0.0%    10   21.9  21.6  21.1  22.0   0.0
  6.|-- 154.0.4.45                 0.0%    10   22.5  22.1  21.6  22.5   0.0
  7.|-- c35-backbone.coolideas.co  0.0%    10   22.9  22.4  21.7  22.9   0.0
  8.|-- urm-cust.coolideas.co.za   0.0%    10   22.0  22.3  21.5  23.1   0.0
  9.|-- u2n3-cust.coolideas.co.za 10.0%    10   22.8  23.0  22.0  24.8   0.8
Click to expand...

It has been logged with MTN, but they move slowly, that being said packet loss on that hop doesn't mean anything relative to your end destination though.
 
Sinbad said:
To be fair, if you're not seeing loss beyond that hop, then that device is not causing packet loss on your connections. It's just being a bit sporadic about sending you the ICMP message back for its own TTL exceeded messages, because traffic generated by/destined for a device often handles a different path, via different processors, to traffic passing through a device. So the CPU on it could be maxed out, hence it's bad at creating the ICMP error message, but the backplane that's forwarding the packets is fine.
Click to expand...

To be fair, 24 hours without an update to the ticket is not acceptable - regardless of the issue.
 
PBCool said:
It has been logged with MTN, but they move slowly, that being said packet loss on that hop doesn't mean anything relative to your end destination though.
Click to expand...

Thanks, please get your support team to respond to the ticket next time, don't want to have to come check these forums
 
blunt said:
Thanks, please get your support team to respond to the ticket next time, don't want to have to come check these forums
Click to expand...

Just to confirm your latency looks to be resolved?
 
blunt said:
Seems to be now yes - aside from that 40% packet loss which is apparently acceptable?
Click to expand...

Cool, do you have the IP of the device with the packet loss for me?

Packet loss along a path doesn't mean anything so long as there isn't any packet loss beyond that IP, or to your final destination.
 
PBCool said:
Cool, do you have the IP of the device with the packet loss for me?

Packet loss along a path doesn't mean anything so long as there isn't any packet loss beyond it, or to your final destination.
Click to expand...

The problem child is 154.0.14.172, connection has been fine in terms of being able to do what I need to do, it's just a bit concerning to have packet loss on the first hop with a fibre connection
 
[MENTION=394133]PBCool[/MENTION] I don't suppose the CPT peering with MTN has had any progress?
 
blunt said:
The problem child is 154.0.14.172, connection has been fine in terms of being able to do what I need to do, it's just a bit concerning to have packet loss on the first hop with a fibre connection
Click to expand...

You dont have packet loss on your line, just to that IP, which belongs to an MTN device, they are just limiting ICMP on the device, it's nothing to worry about.
 
PBCool said:
You dont have packet loss on your line, just to that IP, which belongs to an MTN device, they are just limiting ICMP on the device, it's nothing to worry about.
Click to expand...

ahh ok cool that explains it then - thanks for the info
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X