Very weird internet issue, beyond my ken.

Hi. We have a new internet circuit through Verizon (unsure of LEC), business class, 100/100. We get those speeds as long as we stay in the metro NYC area. Once we go out - to California, Chicago, etc - those speeds drop to 10/5.

Latency cross-coast seems normal, but we aren't used to this. I understand as latency goes up, our throughput goes down, but it shouldn't be like this.

My best guess is a BGP table entry error somewhere? duplicate paths once we get outside the LEC network? Or maybe a peering choke, but that shouldn't happen with such a small circuit on Verizon, right?

I have no idea how to troubleshoot this, and Verizon says "you're getting your 100mb, not our issue".

Thanks in advance. Scary

edit: traceroutes. latency is 72ms.

NY to LA: C:\Users\username>tracert -d 70.231.54.177

Tracing route to 70.231.54.177 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.3

2 2 ms 1 ms 1 ms 207.86.176.141

3 2 ms 2 ms 43 ms 216.156.16.212

4 2 ms 2 ms 2 ms 216.156.16.133

5 13 ms 3 ms 3 ms 206.111.13.246

6 79 ms 70 ms 71 ms 12.122.131.86

7 71 ms 71 ms 70 ms 12.122.1.2

8 73 ms 72 ms 70 ms 12.122.2.53

9 74 ms 71 ms 71 ms 12.122.28.77

10 74 ms 71 ms 71 ms 12.122.28.46

11 76 ms 71 ms 77 ms 12.122.1.185

12 72 ms 74 ms 71 ms 12.122.85.37

13 * * * Request timed out.

14 71 ms 70 ms 71 ms 75.20.1.78

15 * * * Request timed out.

16 73 ms 72 ms 72 ms 64.148.105.209

17 72 ms 72 ms 72 ms 104.191.67.108

18 73 ms 73 ms 72 ms 70.231.54.177

19 72 ms 72 ms 72 ms 70.231.54.177

Trace complete.

LA to NY

C:\Users\username>tracert -d 207.86.176.142

Tracing route to 207.86.176.142 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.3.3

2 <1 ms 205 ms 79 ms 162.195.124.1

3 2 ms 1 ms 1 ms 64.148.105.208

4 * * * Request timed out.

5 4 ms 7 ms 7 ms 12.83.38.201

6 6 ms 7 ms 7 ms 12.122.128.101

7 4 ms 4 ms 4 ms 205.158.79.241

8 70 ms 70 ms 70 ms 207.88.13.10

9 70 ms 70 ms 70 ms 207.88.12.182

10 70 ms 70 ms 70 ms 216.156.16.179

11 72 ms 72 ms 72 ms 207.86.176.142

12 72 ms 72 ms 72 ms 207.86.176.142

Trace complete.

image of d/l test from various AWS points: https://imgur.com/a/ENNrJJn