PDA

View Full Version : Dallas Network Latency - 7PM Friday



VOIPoTim
03-13-2009, 06:26 PM
Around 7PM Central on Friday, we started seeing significant latency into our current primary datacenter in Dallas for users using some ISPs.

This only lasted a few minutes, but could have been noticeable for some users.

If your ATA lost registration during this time, it should have reconnected within minutes or at its next scheduled re-registration if BYOD.

If anyone notices any issues related to this, please let us know.

sr98user
03-13-2009, 09:04 PM
Its pretty bad for east01 currently. Its about 110 ms on average. The last hop is almost doubling the round trip time.

Target Name: east01.voipwelcome.com
IP: 208.43.97.218
Date/Time: 3/13/2009 11:01:08 PM


6 38 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
7 41 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
8 90 ms [216.156.72.5]
9 52 ms 207.88.13.10.ptr.us.xo.net [207.88.13.10]
10 53 ms 207.88.14.70.ptr.us.xo.net [207.88.14.70]
11 59 ms 207.88.183.54.ptr.us.xo.net [207.88.183.54]
12 98 ms border1.te7-2-bbnet2.wdc008.pnap.net [216.52.127.98]
13 65 ms te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66]
14 62 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
15 104 ms east01.voipwelcome.com [208.43.97.218]

usa2k
03-14-2009, 05:19 AM
I had reported my 2nd registration loss with the HT502 in 14 days yesterday.
(The first was 13 days without issue.) [#DQU-493001] (734-437-XXXX Account.)

This 2nd occurrence was likely in the time VOIPo this thread issue.
The vPanel also seemed slow around the same time.

I'll have to see if my HT502 runs hot like the recent email notice?
Its in the basement, under the stairs on a shelf with the router and modem.
Generally, is has not been a major pain.

[Tim, you might want to take a look at some of the observations I left in that ticket.]

Wouldn't it be cute, if something off the wall was the cause of HT502 failures, like too much ripple on the wall-wart power supply? I remember (Vonage I think?) having device issues with CID that corrected itself by rebooting the ATA. That was sourced to bad wall-wart power supplies.