Quote Originally Posted by chpalmer View Post
C:\>tracert 67.228.77.18

Tracing route to sip-byod.voipwelcome.com [67.228.77.18]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.31.125.1
2 13 ms 17 ms 10 ms 24.113.35.1
3 11 ms 12 ms 14 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 13 ms 12 ms 11 ms 64.146.249.93
5 13 ms 15 ms 13 ms 66.119.192.209
6 14 ms 21 ms 15 ms te1-3.cer01.seattle-datacenter.com [206.81.80.140]
7 84 ms 81 ms 85 ms te2-3.cer01.wdc01.washingtondc-datacenter.com [67.228.118.238]
8 115 ms 115 ms 116 ms te9-6.dar01.dal01.dallas-datacenter.com [208.43.118.193]
9 127 ms 115 ms 118 ms po1.fcr04.dal01.dallas-datacenter.com [66.228.118.214]
10 121 ms 115 ms 116 ms sip-byod.voipwelcome.com [67.228.77.18]

Trace complete.

C:>tracert west01.voipwelcome.com

Tracing route to west01.voipwelcome.com [174.37.45.134]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.31.125.1
2 15 ms 12 ms 14 ms 24.113.35.1
3 11 ms 11 ms 11 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 16 ms 12 ms 13 ms wavebroadband-gw.g11-0.oly-cor0.noanet.net [64.146.232.253]
5 15 ms 13 ms 13 ms srp3-0.wtn-cor0.noanet.net [66.119.192.25]
6 213 ms * 12 ms te1-3.cer01.seattle-datacenter.com [206.81.80.140]
7 90 ms 82 ms 82 ms te2-3.cer01.wdc01.washingtondc-datacenter.com [67.228.118.238]
8 115 ms 115 ms 117 ms te9-6.dar01.dal01.dallas-datacenter.com [208.43.118.193]
9 136 ms 119 ms 117 ms po1.fcr04.dal01.dallas-datacenter.com [66.228.118.214]
10 117 ms 117 ms 115 ms sip-central01.voipwelcome.com [174.37.45.134]

Trace complete.

C:\>tracert sip-east01.voipwelcome.com

Tracing route to sip-east01.voipwelcome.com [208.43.68.151]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.31.125.1
2 11 ms 10 ms 11 ms 24.113.35.1
3 15 ms 9 ms 11 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 13 ms 15 ms 14 ms ip-64-184-129-237.noanet.net [64.184.129.237]
5 17 ms 12 ms 13 ms te1-3.cer01.seattle-datacenter.com [206.81.80.140]
6 81 ms 81 ms 93 ms te2-3.cer01.wdc01.washingtondc-datacenter.com [67.228.118.238]
7 86 ms 81 ms 81 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
8 83 ms 81 ms 85 ms sip-east01.voipwelcome.com [208.43.68.151]

Trace complete.


Looks like my flight lands in DC whether or not its my destination...
Forgot about that. West would be the exception....it's been offline since http://forums.voipo.com/showthread.php?t=1668

We're reviewing west coast options and all that traffic is in Dallas. The problem is that we've seen a few times where there's been some latency since the connections from west are connecting to core stuff back in Dallas through the public internet. There were a few occasional timeouts with database queries, etc.

East is a little different since it connects to Dallas via a private network so it's rock solid in that sense.

We may put something back online for west coast users in the future, but none should have an issue with Dallas. We're still looking at Seattle since we can hit Dallas on the private network then vs the public internet, but it just has a lot of latency in terms of the public internet side that customers would connect to it on.

The goal is to avoid the public internet whenever possible for all internal stuff and handoffs.