dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
11373

torobull123
join:2009-06-20

torobull123 to JenSuisUn

Member

to JenSuisUn

Re: [DSL] DSL Slow Speeds Update (ON/QC)

I'd suggest checking your gateway loads.
torobull123

torobull123 to JenSuisUn

Member

to JenSuisUn
Tracing route to google.ca [74.125.226.111]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms x.x.x.x
2 213 ms 196 ms 176 ms lo-100.erx06.tor.packetflow.ca [206.248.154.106]
3 51 ms 31 ms 56 ms ae0_2110-bdr04-tor.teksavvy.com [69.196.136.36]
4 21 ms 33 ms 26 ms 72.14.212.134
5 * 230 ms * 216.239.47.114
6 185 ms 153 ms 26 ms 209.85.250.207
7 245 ms * 76 ms yyz08s13-in-f15.1e100.net [74.125.226.111]

Trace complete.
torobull123

torobull123 to JenSuisUn

Member

to JenSuisUn
|---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| x.x.x.x - 0 | 129 | 129 | 1 | 3 | 43 | 2 |
| lo-100.erx06.tor.packetflow.ca - 7 | 101 | 94 | 19 | 75 | 386 | 386 |
| ae0_2110-bdr04-tor.teksavvy.com - 7 | 101 | 94 | 21 | 75 | 385 | 385 |
| 72.14.212.134 - 23 | 67 | 52 | 22 | 78 | 302 | 302 |
| 216.239.47.114 - 6 | 105 | 99 | 21 | 81 | 386 | 386 |
| 209.85.250.207 - 5 | 109 | 104 | 22 | 82 | 369 | 369 |
| yyz08s13-in-f31.1e100.net - 9 | 96 | 88 | 19 | 69 | 311 | 173 |
|________________________________________________|______|______|______|______|______|______|
torobull123

torobull123 to JenSuisUn

Member

to JenSuisUn
5 reboots/resyncs later.... whats the verdict TSI Martin?

The speeds are horrific.

torobull123

torobull123 to JenSuisUn

Member

to JenSuisUn
Hello????? This is FAR from normal TSI. The silence is even more reassuring.
torobull123

torobull123 to JenSuisUn

Member

to JenSuisUn
9% packet loss on the TSI gateway connecting to teksavvy.com!

|---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| x.x.x.x - 0 | 341 | 341 | 1 | 2 | 81 | 1 |
| lo-100.erx06.tor.packetflow.ca - 9 | 256 | 235 | 19 | 60 | 381 | 37 |
| ae1_2120-agg01-tor.teksavvy.com - 6 | 277 | 261 | 20 | 65 | 275 | 40 |
| ae0_2004-bdr01-tek.teksavvy.com - 5 | 286 | 272 | 25 | 66 | 391 | 137 |
| ge-2-0-0_500-n0-srx01-tek.teksavvy.com - 4 | 298 | 287 | 24 | 67 | 389 | 134 |
| www.teksavvy.com - 7 | 270 | 252 | 25 | 68 | 389 | 138 |
|________________________________________________|______|______|______|______|______|______|

JenSuisUn
Premium Member
join:2006-02-23
Chatham, ON

JenSuisUn

Premium Member

Thanks for the MTR.
341 to 256 is a lot of ignored packets.

Your sync looks fine.

What do you get when you connect with test@test? Do you get high pings to the gateway?

Martin

torobull123
join:2009-06-20

torobull123

Member

what is test@test?

JenSuisUn
Premium Member
join:2006-02-23
Chatham, ON

JenSuisUn

Premium Member

connect with the following.

U: test@test
P: test

note your IP. 10.x.x.x
ping -n 50 (your IP 10.x.x.1)

What are the results.

Regards,
Martin

torobull123
join:2009-06-20

torobull123 to JenSuisUn

Member

to JenSuisUn
ping -n 50 10.11.2.158

Pinging 10.11.2.158 with 32 bytes of data:
Reply from 10.11.2.158: bytes=32 time=2ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=5ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=15ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=5ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=2ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=13ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=5ms TTL=64
Reply from 10.11.2.158: bytes=32 time=4ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=5ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=3ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=22ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=2ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=12ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=3ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=7ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=2ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=2ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64

Ping statistics for 10.11.2.158:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 22ms, Average = 2ms

ping -n 50 10.11.2.158

Pinging 10.11.2.158 with 32 bytes of data:
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=2ms TTL=64
Reply from 10.11.2.158: bytes=32 time=2ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=5ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=2ms TTL=64
Reply from 10.11.2.158: bytes=32 time=7ms TTL=64
Reply from 10.11.2.158: bytes=32 time=2ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=3ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=3ms TTL=64
Reply from 10.11.2.158: bytes=32 time=2ms TTL=64
Reply from 10.11.2.158: bytes=32 time=5ms TTL=64
Reply from 10.11.2.158: bytes=32 time=2ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=22ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=4ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=2ms TTL=64
Reply from 10.11.2.158: bytes=32 time=23ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=2ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64
Reply from 10.11.2.158: bytes=32 time=6ms TTL=64
Reply from 10.11.2.158: bytes=32 time=1ms TTL=64

Ping statistics for 10.11.2.158:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 23ms, Average = 2ms

JenSuisUn
Premium Member
join:2006-02-23
Chatham, ON

JenSuisUn

Premium Member

Hi,

Those would be pinging yourself. See if you can ping the following IP : 10.11.2.1

Thanks.
Martin

torobull123
join:2009-06-20

1 edit

torobull123 to JenSuisUn

Member

to JenSuisUn
I don't know why.... but after connecting back to my regular credentials after the test connect.... my speeds are ok now. There must be some congested gateway.

ZERO packetloss.

|---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| x.x.x.x - 0 | 50 | 50 | 1 | 4 | 27 | 1 |
| lo-100.erx06.tor.packetflow.ca - 0 | 50 | 50 | 18 | 28 | 93 | 18 |
| ae1_2120-agg02-tor.teksavvy.com - 0 | 50 | 50 | 17 | 23 | 49 | 18 |
| ae0_2004-bdr01-tek.teksavvy.com - 0 | 50 | 50 | 23 | 31 | 58 | 23 |
| ge-2-0-0_500-n0-srx01-tek.teksavvy.com - 0 | 50 | 50 | 23 | 29 | 54 | 24 |
| www.teksavvy.com - 0 | 50 | 50 | 23 | 29 | 55 | 23 |
|________________________________________________|______|______|______|______|______|______|

|---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| x.x.x.x - 0 | 116 | 116 | 1 | 4 | 27 | 3 |
| lo-100.erx06.tor.packetflow.ca - 0 | 116 | 116 | 18 | 27 | 102 | 19 |
| ae1_2120-agg02-tor.teksavvy.com - 0 | 116 | 116 | 17 | 23 | 61 | 19 |
| ae0_2004-bdr01-tek.teksavvy.com - 0 | 116 | 116 | 23 | 30 | 58 | 28 |
| ge-2-0-0_500-n0-srx01-tek.teksavvy.com - 0 | 116 | 116 | 23 | 28 | 54 | 23 |
| www.teksavvy.com - 0 | 116 | 116 | 23 | 30 | 55 | 27 |
|________________________________________________|______|______|______|______|______|______|

JenSuisUn
Premium Member
join:2006-02-23
Chatham, ON

JenSuisUn

Premium Member

So it's either, something occurring locally and connection was reestablished after the test@test results.

Or.... Peak period is over & everything is back to normal.

Martin

torobull123
join:2009-06-20

torobull123 to JenSuisUn

Member

to JenSuisUn
No idea. Prior to the test the I'd get an IP but the DNS wasn't resolving for 20+ minutes.

Never had an issue like this before.

If it holds, Im happy. Thank you TSI Martin.
dra6o0n
join:2011-08-15
Mississauga, ON

dra6o0n to JenSuisUn

Member

to JenSuisUn
I heard from a friend that Google DNS is being targeted these days, something to do with DNS hacking or spoofing being the next big thing to do (over DDoS or breaking encryptions or some other stuff).

I mean it makes sense: Target the DNS and you get access to every single computer that talks to it.

TSI Kris
Premium Member
join:2013-11-18
Chatham, ON

2 edits

TSI Kris

Premium Member

You might be thinking of a DNS Reflection attack which is a specific way of performing a DDoS attack. I don't think Google's DNS servers were really usable for those attacks as their security is pretty tight. You might be referring to something else that I've entirely missed, though. :P

Thanks,

TSI Kris

EDIT: In regards to actual spoofs, they seem to be mostly limited to Man in the Middle tampering.
AringSTA
join:2014-03-06

AringSTA to JenSuisUn

Member

to JenSuisUn
said by JenSuisUn:

Would you be able to provide an MTR reading for google.ca.

This way we can see if it's packet loss or simply the routers not giving priority to the ICMP packet.

Regards,
Martin

In support to the above, it is sometimes good to understand the details. Long prez but informative. »www.nanog.org/sites/defa ··· 2.49.pdf

Ian D Allen
If this were easy, everyone would do it.
Premium Member
join:2008-10-26
Ottawa, ON

Ian D Allen to TSI Andre

Premium Member

to TSI Andre
Click for full size
TekSavvy Upload/Download rates in Ottawa (Centretown)
Huge peak-time slowdowns on Tuesday and Wednesday in Ottawa Centretown.

sloth
@75.119.251.x

sloth to torobull123

Anon

to torobull123


25/7 DSL ...

wow, like that until the end of the month? hockey is during peek time, this is Canada, come on!
I cannot stream the game
jablonsa
join:2009-03-08
Mississauga, ON

2 edits

jablonsa to JenSuisUn

Member

to JenSuisUn
Hi just got Teksavvy cable 30 connected. a speed teset a minute ago shows my download speed at 2.5Mbps and my upload speed comes up with an error after the test times out i guess. And ya my actual internet speed is what i remember bad dialup use to be like. Gopd thing I have not disconnected my DLS which I have with another reseller who also uses bell lines. With them i pay for 5Mbps which has been consistent without a single slowdown. since that internet is 100 percent fine I dont see how Teksavvy can blame Bell. If anything its a Bell-Teksavvy issue because this appears to be targeted. so end of the month thing was posted in september its now middle of october.

DataRiker
Premium Member
join:2002-05-19
00000

DataRiker

Premium Member

@jablonsa

Are you hitting a local server or tied a couple of different servers?
jablonsa
join:2009-03-08
Mississauga, ON

1 edit

jablonsa

Member

I have tried a bunch of servers. download fluctuates between 3-10 and upload fails 9 out of 10 times. sometimes it registers as 0.1Mbps. I just connected over to my other internet provider running on DLS. no issues. its running stable as normal.
BTW I am located in Mississauga, Near south common mall.

Ian D Allen
If this were easy, everyone would do it.
Premium Member
join:2008-10-26
Ottawa, ON

Ian D Allen to JenSuisUn

Premium Member

to JenSuisUn
Click for full size
TekSavvy Upload/Download speeds in Ottawa Centretown
The graph shows the huge peak-period DSL slowdowns over the past three days.
My DSL line stats haven't changed in three months (since I unlocked the modem to collect them).
I don't think this is specific to my DSL line here in Ottawa Centretown.
My Distributel cable connection also shows very slight dips on Tuesday and Thursday but nothing as severe as TekSavvy.

Line Status : Port is in Showtime
Mode : 0x4000000 (VDSL2 Profile 17A )
Upstream Payload Rate : 11328 kbps
Downstream : 53936 kbps
DIAG Info:
Attenuation ( dB ) : 11.0 3.20 (FE LATNpb-0)
12.60 (FE LATNpb-1)
21.10 (FE LATNpb-2)
102.30 (FE LATNpb-3)
102.30 (FE LATNpb-4)
SNR margin ( dB ) : 21.3 19.40 (FE SNRMpb-0)
20.30 (FE SNRMpb-1)
18.10 (FE SNRMpb-2)
-51.20 (FE SNRMpb-3)
-51.20 (FE SNRMpb-4)
US Aggregate Power : -9.6 dbm
DS Attainable Data Rate: 101896 kbps
US Attainable Data Rate: 31356 kbps
HEC counter : HEC_F:0
HEC_S:0
CRC counter : CRC_F:0
CRC_S: 0
JMJimmy
join:2008-07-23

JMJimmy to JenSuisUn

Member

to JenSuisUn
Getting horrible speeds here.
JMJimmy

1 edit

JMJimmy to JenSuisUn

Member

to JenSuisUn


>tracert www.google.ca

Tracing route to www.google.ca [173.194.43.79]
over a maximum of 30 hops:

1 11 ms 7 ms 2 ms ControlPanel.Home [192.168.1.1]
2 76 ms 18 ms 23 ms 206.248.154.121
3 12 ms 11 ms 138 ms ae0_2110-bdr04-tor.teksavvy.com [69.196.136.36]

4 58 ms 117 ms 51 ms 72.14.212.134
5 9 ms 64 ms 14 ms 216.239.47.114
6 41 ms 36 ms 106 ms 72.14.239.19
7 28 ms 23 ms 43 ms yyz08s09-in-f15.1e100.net [173.194.43.79]

Trace complete.

>ping www.google.ca /t

Pinging www.google.ca [173.194.43.79] with 32 bytes of data:
Reply from 173.194.43.79: bytes=32 time=9ms TTL=58
Reply from 173.194.43.79: bytes=32 time=19ms TTL=58
Reply from 173.194.43.79: bytes=32 time=27ms TTL=58
Reply from 173.194.43.79: bytes=32 time=53ms TTL=58
Reply from 173.194.43.79: bytes=32 time=10ms TTL=58
Reply from 173.194.43.79: bytes=32 time=30ms TTL=58
Reply from 173.194.43.79: bytes=32 time=38ms TTL=58
Reply from 173.194.43.79: bytes=32 time=31ms TTL=58
Reply from 173.194.43.79: bytes=32 time=213ms TTL=58
Reply from 173.194.43.79: bytes=32 time=9ms TTL=58
Reply from 173.194.43.79: bytes=32 time=15ms TTL=58
Reply from 173.194.43.79: bytes=32 time=17ms TTL=58
Reply from 173.194.43.79: bytes=32 time=43ms TTL=58
Reply from 173.194.43.79: bytes=32 time=49ms TTL=58
Reply from 173.194.43.79: bytes=32 time=30ms TTL=58
Reply from 173.194.43.79: bytes=32 time=17ms TTL=58
Reply from 173.194.43.79: bytes=32 time=32ms TTL=58
Reply from 173.194.43.79: bytes=32 time=25ms TTL=58
Reply from 173.194.43.79: bytes=32 time=75ms TTL=58
Reply from 173.194.43.79: bytes=32 time=45ms TTL=58
Reply from 173.194.43.79: bytes=32 time=19ms TTL=58
Reply from 173.194.43.79: bytes=32 time=12ms TTL=58
Reply from 173.194.43.79: bytes=32 time=21ms TTL=58
Reply from 173.194.43.79: bytes=32 time=17ms TTL=58
Reply from 173.194.43.79: bytes=32 time=44ms TTL=58
Reply from 173.194.43.79: bytes=32 time=35ms TTL=58
Reply from 173.194.43.79: bytes=32 time=15ms TTL=58
Reply from 173.194.43.79: bytes=32 time=47ms TTL=58
Reply from 173.194.43.79: bytes=32 time=36ms TTL=58

Ping statistics for 173.194.43.79:
Packets: Sent = 29, Received = 29, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 213ms, Average = 35ms

Typically 6ms avg, 25/10Mbps

Ian D Allen
If this were easy, everyone would do it.
Premium Member
join:2008-10-26
Ottawa, ON

Ian D Allen to JenSuisUn

Premium Member

to JenSuisUn
Click for full size
TekSavvy Upload/Download speeds in Ottawa Centretown
The graph shows the fourth straight day of huge evening slowdowns for TekSavvy here in Ottawa Centretown.
JMJimmy
join:2008-07-23

JMJimmy to JenSuisUn

Member

to JenSuisUn
Another slow day in TO.

ping www.teksavvy.com -n 50

Pinging www.teksavvy.com [206.248.155.70] with 32 bytes of data:
Reply from 206.248.155.70: bytes=32 time=36ms TTL=123
Reply from 206.248.155.70: bytes=32 time=17ms TTL=123
Reply from 206.248.155.70: bytes=32 time=22ms TTL=123
Reply from 206.248.155.70: bytes=32 time=26ms TTL=123
Reply from 206.248.155.70: bytes=32 time=16ms TTL=123
Reply from 206.248.155.70: bytes=32 time=30ms TTL=123
Reply from 206.248.155.70: bytes=32 time=75ms TTL=123
Reply from 206.248.155.70: bytes=32 time=14ms TTL=123
Reply from 206.248.155.70: bytes=32 time=15ms TTL=123
Reply from 206.248.155.70: bytes=32 time=30ms TTL=123
Reply from 206.248.155.70: bytes=32 time=21ms TTL=123
Reply from 206.248.155.70: bytes=32 time=32ms TTL=123
Reply from 206.248.155.70: bytes=32 time=35ms TTL=123
Reply from 206.248.155.70: bytes=32 time=427ms TTL=123
Reply from 206.248.155.70: bytes=32 time=29ms TTL=123
Reply from 206.248.155.70: bytes=32 time=41ms TTL=123
Reply from 206.248.155.70: bytes=32 time=21ms TTL=123
Reply from 206.248.155.70: bytes=32 time=14ms TTL=123
Reply from 206.248.155.70: bytes=32 time=37ms TTL=123
Reply from 206.248.155.70: bytes=32 time=25ms TTL=123
Reply from 206.248.155.70: bytes=32 time=32ms TTL=123
Reply from 206.248.155.70: bytes=32 time=18ms TTL=123
Reply from 206.248.155.70: bytes=32 time=28ms TTL=123
Reply from 206.248.155.70: bytes=32 time=58ms TTL=123
Reply from 206.248.155.70: bytes=32 time=62ms TTL=123
Reply from 206.248.155.70: bytes=32 time=115ms TTL=123
Reply from 206.248.155.70: bytes=32 time=100ms TTL=123
Reply from 206.248.155.70: bytes=32 time=57ms TTL=123
Reply from 206.248.155.70: bytes=32 time=14ms TTL=123
Reply from 206.248.155.70: bytes=32 time=41ms TTL=123
Reply from 206.248.155.70: bytes=32 time=29ms TTL=123
Reply from 206.248.155.70: bytes=32 time=17ms TTL=123
Reply from 206.248.155.70: bytes=32 time=21ms TTL=123
Reply from 206.248.155.70: bytes=32 time=66ms TTL=123
Reply from 206.248.155.70: bytes=32 time=31ms TTL=123
Reply from 206.248.155.70: bytes=32 time=16ms TTL=123
Reply from 206.248.155.70: bytes=32 time=23ms TTL=123
Reply from 206.248.155.70: bytes=32 time=20ms TTL=123
Reply from 206.248.155.70: bytes=32 time=48ms TTL=123
Reply from 206.248.155.70: bytes=32 time=70ms TTL=123
Reply from 206.248.155.70: bytes=32 time=73ms TTL=123
Reply from 206.248.155.70: bytes=32 time=77ms TTL=123
Reply from 206.248.155.70: bytes=32 time=28ms TTL=123
Reply from 206.248.155.70: bytes=32 time=37ms TTL=123
Reply from 206.248.155.70: bytes=32 time=21ms TTL=123
Reply from 206.248.155.70: bytes=32 time=24ms TTL=123
Reply from 206.248.155.70: bytes=32 time=166ms TTL=123
Reply from 206.248.155.70: bytes=32 time=41ms TTL=123
Reply from 206.248.155.70: bytes=32 time=35ms TTL=123
Reply from 206.248.155.70: bytes=32 time=14ms TTL=123

Ping statistics for 206.248.155.70:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 427ms, Average = 46ms

>tracert www.google.ca

Tracing route to www.google.ca [74.125.226.152]
over a maximum of 30 hops:

1 15 ms 8 ms 1 ms ControlPanel.Home [192.168.1.1]
2 40 ms 21 ms 53 ms lo-100.lns03.tor.packetflow.ca [206.248.154.121]

3 27 ms 19 ms 40 ms ae3_2120-bdr03-tor.teksavvy.com [69.196.136.74]

4 151 ms 109 ms 39 ms ae0_2140-bdr04-tor.teksavvy.com [69.196.136.132]

5 52 ms 24 ms 11 ms 72.14.212.134
6 21 ms 7 ms 18 ms 209.85.255.232
7 8 ms 64 ms 24 ms 209.85.250.7
8 17 ms 10 ms 18 ms yyz08s14-in-f24.1e100.net [74.125.226.152]

Trace complete.

Cho Baka
MVM
join:2000-11-23
there

Cho Baka to JenSuisUn

MVM

to JenSuisUn
I had issues again last night for the first time in a while.

jonana
join:2000-08-05
Saint-Laurent, QC

jonana to JenSuisUn

Member

to JenSuisUn
Never ending story! (Montreal)

Tracing route to www.google.ca [74.125.226.120]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 19 ms 25 ms 20 ms 206.248.154.121
3 21 ms 18 ms 18 ms ae0_2110-bdr04-tor.teksavvy.com [69.196.136.36]

4 * * * Request timed out.
5 19 ms 19 ms 19 ms 216.239.47.114
6 19 ms 19 ms 18 ms 209.85.250.207
7 18 ms 17 ms 17 ms yyz08s13-in-f24.1e100.net [74.125.226.120]

Tracing route to www.google.ca [74.125.226.111]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 21 ms 20 ms 19 ms 206.248.154.121
3 19 ms 19 ms 18 ms ae3_2120-bdr03-tor.teksavvy.com [69.196.136.74]

4 23 ms 23 ms 22 ms ae0_2140-bdr04-tor.teksavvy.com [69.196.136.132]

5 * * 20 ms 72.14.212.134
6 40 ms 36 ms 76 ms 216.239.47.114
7 21 ms 22 ms 21 ms 209.85.250.207
8 20 ms 20 ms 20 ms yyz08s13-in-f15.1e100.net [74.125.226.111]

Trace complete.

Cho Baka
MVM
join:2000-11-23
there

Cho Baka to JenSuisUn

MVM

to JenSuisUn
Again...