spenceteeth

Just a query. Is the residential gateway/ modem provided by Spectrum?
If so is PC connected directly to that provided modem or passed through either a switch or isp extender device or perhaps a wall jack rj45 ethernet port using inside wire in the walls. 
Also if straight to router is there a port out of usually 4 or 5 grouped ports that are not of the same color or may even labeled as "1Gbps" some go higher when dealing with fastest speeds. Att and Comcast have equipment that use this
 
Internet speed on PC is largely hardware specific. gpu, cpu, memory, Network interface 
 
 
As a former tech for the Death Star I would bet its the top suggestions. Lasty the PC...but it is more common than you think of coming up shy.
 
820 on here is good on testmy I wouldn't fret

Just a query. Is the residential gateway/ modem provided by Spectrum?
If so is PC connected directly to that provided modem or passed through either a switch or isp extender device or perhaps a wall jack rj45 ethernet port using inside wire in the walls. 
Also if straight to router is there a port out of usually 4 or 5 grouped ports that are not of the same color or may even labeled as "1Gbps" some go higher when dealing with fastest speeds. Att and Comcast have equipment that use this
 
Internet speed on PC is largely hardware specific. gpu, cpu, memory, Network interface 
 
 
As a former tech for the Death Star I would bet its the top suggestions. Lasty the PC...but it is more common than you think of coming up shy.
 
820 on here is good on testmy I wouldn't fret

Using DNS in Singapore doesn't really help for your latency to the server.
 
Latency is like the time it takes for you to send a message to your friend and for them to respond. In the world of the internet, when you click on something or ask your computer to do something online, it sends a request to another computer far away. Latency is how long it takes for that request to reach the other computer and for you to get an answer back. If it takes a long time, everything online feels slow, like when you're waiting for someone to respond to a text.
 
When you ask your computer to load a website, it sends a message to another computer far away called a server. That server holds the information for the website you want. The message travels through wires, cables, or even space (if it’s using satellites!), and when the server gets it, it sends the website information back to your computer the same way. The time it takes for the message to go to the server and back to your computer is what we call latency. The quicker it travels, the faster things load!
 
You can't improve this unless you're able to take a shorter path to the server.  The physical distance creates unavoidable latency... the speed of light is the limiting factor.
 
What the Latency Test is showing you is that servers in Singapore will perform best for you.  Amazon is hosted on a CDN (content delivery network) so when you request using that test it pulls from a server closer to you automatically.
 
To improve latency over long distances, here’s how it works:
Use servers closer to you: Imagine a game of telephone. The closer the person, the quicker the message gets to you. Using servers that are closer (like a local one instead of one far away) speeds things up.
Optimize the route: Think of taking the quickest path home. By using smarter routes (like special internet paths called "content delivery networks"), the message travels faster, just like choosing a shortcut.
Use faster connections: Just like a fast car on a highway, using better internet connections helps the message travel quicker, even over long distances!

Possible your ISP and test server for Dallas are one in the same.
 
I run speed tests out of boredom I have seen all kinds of weird things across national and international tests. I wouldn't be concerned 

working now. good job Cable
 

This is so weird!
 
Here's the rules I'm testing.
 
RewriteRule ^statstest/tekwav$ /tools/database/db_search.php?type=user_name&q=tekwav [L,QSA] RewriteRule ^statstest/tekwav.$ /tools/database/db_search.php?type=user_name&q=tekwav [L,QSA] RewriteRule ^statstest/.tekwav$ /tools/database/db_search.php?type=user_name&q=tekwav [L,QSA] RewriteRule ^statstest/.tekwav.$ /tools/database/db_search.php?type=user_name&q=tekwav [L,QSA]  
So they are all pointing the the same destination.
 
https://testmy.net/statstest/tekwav -- 404 not found https://testmy.net/statstest/tekwav. -- 200 works https://testmy.net/statstest/.tekwav -- 404 not found https://testmy.net/statstest/.tekwav. -- 200 works  
They should all work.
 
I went directly to the server IP and had the same result, so it's definitely not cloudflare.
 
lol... I think it's because your username ends in wav ... like a wav file.  This probably boils down to a poorly written expression in nginx additional directives.
 
Here's why I have this theory.
 
RewriteRule ^statstest/.ekwav$ /tools/database/db_search.php?type=user_name&q=tekwav [L,QSA] -- 404 not found RewriteRule ^statstest/t.kwav$ /tools/database/db_search.php?type=user_name&q=tekwav [L,QSA] -- 404 not found RewriteRule ^statstest/te.wav$ /tools/database/db_search.php?type=user_name&q=tekwav [L,QSA] -- 404 not found RewriteRule ^statstest/tek.av$ /tools/database/db_search.php?type=user_name&q=tekwav [L,QSA] -- 200 works RewriteRule ^statstest/tekw.v$ /tools/database/db_search.php?type=user_name&q=tekwav [L,QSA] -- 200 works RewriteRule ^statstest/tekwa.$ /tools/database/db_search.php?type=user_name&q=tekwav [L,QSA] -- 200 works  
results in
 
https://testmy.net/statstest/.ekwav -- 404 not found https://testmy.net/statstest/t.kwav -- 404 not found https://testmy.net/statstest/te.wav -- 404 not found https://testmy.net/statstest/tek.av -- 200 works https://testmy.net/statstest/tekw.v -- 200 works https://testmy.net/statstest/tekwa. -- 200 works  
As I iterate through, as soon as the URL it no longer ends in "wav" it works.
 
Now the rule is supposed to be looking for .wav not wav
 
Here's the culprit.  In nginx additional directives.
 
location ~* .(js|jpg|jpeg|gif|css|tgz|gz|rar|bz2|doc|pdf|ppt|tar|wav|bmp|rtf|swf|ico|flv|txt|woff|woff2|svg|json)$ { etag on; if_modified_since exact; add_header Pragma "public"; add_header Cache-Control "max-age=31536000, public"; }  
To further test the theory that this is the culprit I add additional test rules to my .htaccess (mod_rewrite)
 
We'll pretend a new member has a name ending in doc and tgz -- then test with one character blocking the pattern I suspect is being detected.
RewriteRule ^statstest/tekdoc$ /tools/database/db_search.php?type=user_name&q=tekwav [L,QSA] RewriteRule ^statstest/tekdo.$ /tools/database/db_search.php?type=user_name&q=tekwav [L,QSA] RewriteRule ^statstest/tektgz$ /tools/database/db_search.php?type=user_name&q=tekwav [L,QSA] RewriteRule ^statstest/tektg.$ /tools/database/db_search.php?type=user_name&q=tekwav [L,QSA]  
https://testmy.net/statstest/tekdoc -- 404 not found https://testmy.net/statstest/tekdo. -- 200 works https://testmy.net/statstest/tektgz -- 404 not found https://testmy.net/statstest/tektg. -- 200 works  
Still, I don't see a mistake in how that nginx directive is written.  That should only capture if it has a preceding period.  I'll have to think about this.  Obviously I can just remove that rule and it will work but I have it there for a reason. 
 
Maybe I simply need to remove the leading period and then add it to each.  Like this... (update: nevermind, same result)
 
Yup, without that nginx directive it works.  I'll try to understand why it's not working as expected and rewrite that directive and post it here for other webmasters.
 
 

Deathstar employee here.
 
Have you asked for Att to validate address?
 
also try this:
 
https://broadbandmap.fcc.gov/#/