Routing
Highlighted
Routing

New Circuit Latency Increase and Upload Speed

‎10-20-2019 09:44 PM

I recently did an upgrade with AT&T from an older ADI/MIS 45M/45M DS3 circuit to a ADI/MIS 100M/100M circuit. Both of these are being provided over fiber run into my office. Both of these are serviced by my local LEC Frontier Communications. In the process of test and turn-up for the new circuit I've noticed the following issues.

1. My old circuit pings to the gateway at 7-8ms whereas the new circuit is 33-34ms

2. My old circuit up and down would speed test would speed test at 40M/40M whereas the new circuit speed tests are 95M Down and 60-80M Up.

I've opened a troube ticket with AT&T but at this point have been unable to get any answers to the issues.

What I know think I know:
I believe that the old circuit is a DS3 that rides over a OC3. The hardware in use at my office is a utilizing a Cisco DS3+ Card in a Cisco 7206VXR Router with an NPE-G1. I believe that the circuit goes from Tuscola, IL to Champaign, IL to Indianapolis In, to Chicago IL.

When talking to the AT&T engineer regarding the trouble ticket he stated that it was provisioned down to St. Louis. From there I assume it goes to Indianapolis.

The AT&T engineer stated that the latency was due to it not being a serial dedicated circuit but ethernet. I just don't know enough about it to be able to dispute that but as a small ISP with microwave wireless internal WAN links that average 9ms going through ethernet connections with 10 routers in between I would have thought the new circuit going over fiber would be better.

 

Traceroutes for each circuit below:

 

Tracing route to 8.8.8.8 over a maximum of 30 hops

100M
1 33 ms 33 ms 33 ms 12.247.177.33
2 41 ms 47 ms 47 ms 12.122.117.174
3 43 ms 43 ms 43 ms 12.122.2.177
4 39 ms 40 ms 39 ms 12.122.99.101
5 39 ms 39 ms 39 ms 12.247.108.6
6 * * * Request timed out.
7 39 ms 39 ms 39 ms 8.8.8.8

Trace complete.

 

45M


Tracing route to 8.8.8.8 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 12.37.71.1
2 13 ms 15 ms 15 ms 12.122.152.242
3 15 ms 15 ms 21 ms 12.122.152.242
4 13 ms 15 ms 15 ms 12.122.152.138
5 12 ms 12 ms 13 ms 12.122.99.93
6 12 ms 13 ms 13 ms 12.247.108.6
7 * * * Request timed out.
8 12 ms 12 ms 12 ms 8.8.8.8

Trace complete.


Below are a sampling of speedtests

101219 - 4:29PM : Speedtest.net:    89D/56U
                            : Fast.com:           94D/64U
9:41PM                : Speedtest.net    : 90D/56U
                            : Fast.com          : 96D/65U
101319 - 12:24AM: Speedtest.net:   91D/69U
                              : Fast.com:         96D/60U
12:58PM                :Speedtest.net:    91D/66U
                              : Fast.com          95D/63U
10:50PM                :Speedtest.net:    91D/60U
                              : Fast.com          94D/59U
                              : DSL Reports:     96D/55U
101419 - 11:14AM: Speedtest.net:   91D/62U
                             : Fast.com :         95D/67U
                             : AT&T :               96D/80U
                             : DSL Reports:      96D/56U
101419 - 3:00PM : Speedtest.net:    91D/66U
                             : Fast.com :         95D/59U
                             : AT&T :               96D/80U
                             : DSL Reports:      96D/68U
101419 - 8:13PM : Speedtest.net:     58D/65U
                             :Fast.com :           86D/65U
                             : AT&T :                96D/85U
                             : DSL Reports:       95D/49U
101519 - 12:53AM: Speedtest.net:    90D/67U
                              : Fast.com :         95D/67U
                              : AT&T :               96D/58U
                              : DSL Reports:      95D/56U

 

So what I'm wondering is what questions should I be asking the AT&T/Frontier engineers to get answers to the latency and non-symmetrical upload issue?

Feedback