[nSLUG] Significant packet loss with aliant?

Jason Kenney jdkenney at gmail.com
Mon Nov 27 16:52:24 AST 2006


Er whoops, I'm silly. Looks like there is a problem with the
64.230.147.41 hop which is Bell in Toronto. Maybe 64.230.187.18 too.
The losses all start after that first guy, so I'd say it's a safe bet
something is wonky in Toronto.


Jason

On 11/27/06, Jason Kenney <jdkenney at gmail.com> wrote:
> Aren't those upstream hops outside of Aliant's scope though? Just
> because they aren't replying to all of your ping traffic, doesn't
> necessarily mean they are dropping your "normal" traffic. But even if
> they are, I'm not sure what Aliant could do about it?
>
> Or am I not understanding your post correctly?
>
>
> Jason
>
> On 11/27/06, D G Teed <donald.teed at gmail.com> wrote:
> > Howdy.
> >
> > At home, I have Eastlink.  At work, Aliant.  I've been
> > comparing mtr reports to various destinations and I see
> > significant packet loss along Aliant hops which do
> >  not show up in Eastlink hops.
> >
> > e.g. www.cnn.com on Aliant:
> >                                  Loss%   Snt   Last   Avg
> > Best  Wrst StDev
> >  1. wfvlnsauh05-fe-0-0.aliant.ne  1.0%   100    3.0   2.7   2.3   4.9   0.4
> >  2. hlfxns01h29-ge-4-0.aliant.ne  0.0%   100    3.1   2.6    2.2   3.9   0.3
> >  3. rtp629049rts                  0.0%   100    2.7   2.7   2.2   3.7   0.4
> >   4. 64.230.166.53                 0.0%   100    2.6   2.7   2.3   3.5   0.3
> >   5. 64.230.147.41                68.0%   100   19.8  48.6  18.4 215.7  53.2
> >  6. 64.230.207.138                1.0%   100   26.3  26.4  25.7  47.1   2.2
> >  7. 64.230.187.18                 55.0%   100   29.5  29.6  27.6  33.7   1.5
> >  8. pop1-nye-P8-1.atdn.net         7.0%   100   26.5  45.8  26.1 230.6  50.5
> >  9. bb2-nye-P0-0.atdn.net          2.0%   100   30.7  28.6  26.1 162.0  14.5
> >  10. bb2-vie-P12-0.atdn.net         3.0%   100   31.9  41.2  31.2 227.4
> > 37.6
> >  11. bb2-atm-P3-0.atdn.net          2.0%   100   41.5  48.5  41.1 235.9
> > 31.2
> >  12. ???                          100.0   100    0.0   0.0   0.0    0.0
> > 0.0
> >
> >
> > e.g. www.cnn.com on Eastlink:
> >                                  Loss%   Snt   Last   Avg
> > Best  Wrst StDev
> >  1. clark.localdomain.domain      1.0%   100    0.5   0.6   0.5   8.2   0.8
> >   2. ???                          100.0   100    0.0   0.0   0.0   0.0   0.0
> >  3. nwmn-asr2.eastlink.ca         0.0%   100    9.1  11.9   7.7  28.3   3.8
> >  4. hlfx-br2.eastlink.ca          0.0%   100   18.4  26.9  15.3 209.7  32.3
> >  5. 65.203.200.77                  0.0%   100   31.7  34.8  30.5  73.9   5.6
> >  6. 0.so-0-1-0.XT2.MTL1.ALTER.NE   0.0%   100   34.2  34.4  30.7  54.5   3.9
> >  7. 0.so-7-0-0.XL4.NYC4.ALTER.NE   0.0%   100   41.1  43.8  39.0  77.5   6.3
> >  8. 0.ge-4-1-0.BR2.NYC4.ALTER.NE   5.0%   100   39.4  44.0  39.0  75.6   7.0
> >  9. 204.255.169.42                 0.0%   100  143.4  49.7  39.1 256.6  27.6
> >  10. bb2-nye-P0-0.atdn.net         0.0%   100   43.2  50.7  39.2 233.8  31.9
> >  11. bb2-vie-P12-0.atdn.net         0.0%   100   47.4  52.9  45.5 205.9
> > 20.2
> >  12. bb2-atm-P3-0.atdn.net         0.0%   100   57.0  66.1  56.9 253.2  28.9
> >  13. ???                          100.0   100    0.0   0.0   0.0   0.0   0.0
> >
> > It isn't specific to CNN.
> >
> > Can anyone else on Aliant confirm if there are problems
> > in recent days like this, or is this experience unique from
> > our location?
> >
> > --Donald
> >
> >  
> > _______________________________________________
> > nSLUG mailing list
> > nSLUG at nslug.ns.ca
> > http://nslug.ns.ca/cgi-bin/mailman/listinfo/nslug
> >
> >
> > !DSPAM:456b2723127131377688803!
> >
> >
> >
>

!DSPAM:456b5dbb144673480620373!




More information about the nSLUG mailing list