tntdsl
join:2005-12-01
Canada
| IGS high latency
Hi everybody,
Former Istop cunstomer if that makes any difference, I've seen high latency immediately after the switch to IGS/Cybersurf: minimum of 30ms to 192.168.200.1. Now, after a few hours of failed authentication 2 days ago, my latency jumps up to 50ms. Any body knows what's up with that?
Ping statistics for 192.168.200.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 93ms, Average = 52ms
Thanks for any insights. |
|
fromage
join:2003-03-31 | Isn't 192.168.200.1 a private IP range? Only used for lan networks? |
|
nyt
join:2003-02-20
france
| nothing prevents the ISP to use private addressing within its network, as long as the original and destination adresses are public. traceroute ftp.videotron.ca and see some 10.x.x.x private adresses on the path  |
|
tntdsl
join:2005-12-01
Canada | reply to fromage
192.168.200.1 is the first hop beyond modem for all of the IGS trace routes I've seen posted on this site. Mine too. |
|
donoreo
Premium
join:2002-05-30
North York, ON | reply to tntdsl
192.168.200.1 is the first hop, it is also slow to respond to ICMP packets (i.e. pings from taceroutes) on purpose.
--
I cannot deny anything I did not say |
|
tntdsl
join:2005-12-01
Canada
| What purpose does slow response serve??? And why does it serve me and not everybody else? Most other IGS trace routes show 20ms or less for the first hop (when there's no problem). In fact, 50ms at first hop is absolutely useless for any kind of serious online game. |
|
drewfar
join:2002-10-01
Mississauga, ON
| reply to tntdsl
50ms first hop consistently could mean you've been put on an interleave profile by Bell cause you have a crap line.
Maybe Bell is doing work in your area?
It could also depend on where you're located. IGS' POP is in Toronto, so if you're far away from Toronto, there is additional latency becuase your traffic needs to be backhauled from your location to Toronto before it even touches IGS' network.
There could be many reasons.
A slow response on any single hop along the way doesn't mean anything, as long as on the next hop it's fine. Some routers are configured to give low priority to ICMP traffic so they can concentrate on giving the best performance to forwarding actual traffic. |
|
tntdsl
join:2005-12-01
Canada
| said by drewfar  :50ms first hop consistently could mean you've been put on an interleave profile by Bell cause you have a crap line. Not on interleave. Attainable line rate is 7548 kbit/sec. Download speed around 2600kbps consistent.
said by drewfar :Maybe Bell is doing work in your area? The above few hours of failed authentication was probably because of their work. But what I've seen after their work is just worse latency.
said by drewfar :It could also depend on where you're located. IGS' POP is in Toronto, so if you're far away from Toronto, there is additional latency becuase your traffic needs to be backhauled from your location to Toronto before it even touches IGS' network. I'm in Ottawa. I didn't think much of it when from ~20ms at Istop it jumped to ~30ms as I was switched to IGS/Cybesurf. But 50ms is not like something normal.
said by drewfar :A slow response on any single hop along the way doesn't mean anything, as long as on the next hop it's fine. Some routers are configured to give low priority to ICMP traffic so they can concentrate on giving the best performance to forwarding actual traffic. It's adding up over the whole trace route. My number is 40ms higher than yours from first hop to last:
===================
Tracing route to www.l.google.com [72.14.203.99]
over a maximum of 30 hops:
1 46 ms 99 ms 99 ms 10.0.0.138
2 50 ms 51 ms 51 ms 192.168.200.1
3 50 ms 51 ms 50 ms i216-58-0-1.cybersurf.com [216.58.0.1]
4 51 ms 52 ms 51 ms h64-187-19-249.gtconnect.net [64.187.19.249]
5 51 ms 51 ms 52 ms 66.59.191.121
6 62 ms 61 ms 61 ms 66.59.191.110
7 63 ms 62 ms 106 ms core1-2-2-0.ord.net.google.com [206.223.119.21]
8 66 ms 66 ms 62 ms 66.249.95.249
9 66 ms 63 ms 63 ms 72.14.238.89
10 80 ms 68 ms 70 ms 64.233.175.94
11 63 ms 63 ms 63 ms 72.14.203.99
==================
BTW, anyone knows how to contact for support being former Istop customer using istop@igs.net login? |
|
trax
join:2002-07-21
Pincourt, QC | Getting 100ms to the 1st hop. It's normally 20ms. Packet loss is 20% at times. Montreal West Island with IGS. Power cycled the modem a few times in case it was an ATM cloud issue, but latencies are still very high. |
|
The Flash
You don't win friends with salad
Premium
join:2002-10-17
Toronto, ON | reply to tntdsl
I think there's too many 3web users now since the network is all the same.
IGS has gone down hill since 3web bought them. |
|
Laike
join:2004-01-25
Mississauga, ON
| I've been having that sort of weird behavior off and on for a few days. One of the tech's pulled me off interleave a few days ago, and things improved, and now this afternoon, things went back to the crapper again. My patience is really being tried here... |
|
micron06
Premium
join:2003-11-19
York Region
1 edit | reply to tntdsl
Try bugging igsjake and see what he has to say about the network performance.
And I hope you guys are contacting support and reporting it or else IGS will no clue about the on-going problem. This forum isn't their official support means. |
|
