Jump to content

Recommended Posts

I live in Sugar Land, TX, just outside of Houston. Is there something going on with the Dallas server? I normally test against that, and it's dropped in speed massively in my tests, from the high 300Mbps range to 1 or 2Mbps. I've tried all the other national and international servers, and they're all WAY faster for me than the Dallas server currently is. What's going on, please? This has been going on for days now.

Link to post
Share on other sites

Yes, there appears to be routing issues with Dallas. Not affecting everyone. Looking at https://testmy.net/live I see many still posting results that are 100's of Mbps.

 

I'm seeing the same issue as you on my home connection. Got a support ticket in.

 

Can you post your traceroute please?

 

Quote
How to Run a Traceroute on a Windows 10 Computer
  1. Open the Windows search box. You can do this by clicking the magnifying glass icon in the bottom-left corner of your screen.
  2. Then type CMD in the search bar and click Open.
  3. Next, type tracert followed by a space and then dallas.testmy.net (in this case)
  4. Finally, press Enter on your keyboard and wait for the traceroute to finish.

 

Paste the result back here please.

 

Here's what mine looks like right now

traceroute dallas.testmy.net
traceroute to dallas.testmy.net (45.32.203.96), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  2.756 ms  1.777 ms  0.988 ms
 2  cm-1-acr01.monument.co.denver.comcast.net (96.120.13.101)  11.519 ms  10.723 ms  16.963 ms
 3  ae-251-1203-rur01.monument.co.denver.comcast.net (96.110.242.73)  12.597 ms  12.288 ms  10.210 ms
 4  ae-12-ar01.denver.co.denver.comcast.net (162.151.50.41)  10.671 ms  14.747 ms  10.639 ms
 5  be-36031-cs03.1601milehigh.co.ibone.comcast.net (96.110.43.249)  18.222 ms
    be-36041-cs04.1601milehigh.co.ibone.comcast.net (96.110.43.253)  13.767 ms
    be-36011-cs01.1601milehigh.co.ibone.comcast.net (96.110.43.241)  13.704 ms
 6  be-3402-pe02.910fifteenth.co.ibone.comcast.net (96.110.38.126)  13.832 ms
    be-3302-pe02.910fifteenth.co.ibone.comcast.net (96.110.38.122)  14.802 ms  15.210 ms
 7  ae3-6.cr4-was1.ip4.gtt.net (173.241.130.117)  15.163 ms  15.873 ms  13.893 ms
 8  ae9.cr0-dal2.ip4.gtt.net (89.149.184.97)  91.704 ms  88.706 ms  87.567 ms
 9  ip4.gtt.net (173.205.43.82)  89.286 ms  86.146 ms  108.639 ms
10  * * *
11  * * *
12  * * *
13  dallas.testmy.net (45.32.203.96)  81.030 ms !Z  83.133 ms !Z  78.687 ms !Z

 

Note the spike in latency from hop 7 to 8. I wonder if our routes have that (gtt.net) in common.

 

Other clients may take different routes and will be unaffected.

Link to post
Share on other sites

Here are the results of my trace:

 

Tracing route to dallas.testmy.net [2001:19f0:6401:148c:5400:1ff:fee0:c981]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  2601:2c7:4300:68e:bea5:11ff:fe1f:5821
  2     9 ms     9 ms     8 ms  2001:558:4081:4a::1
  3    11 ms    17 ms    13 ms  2001:558:2c2:4041::1
  4    10 ms    10 ms    10 ms  ae-14-ar01.bearcreek.tx.houston.comcast.net [2001:558:2c0:54::1]
  5    11 ms    10 ms    10 ms  2001:1900:5:3::315
  6    14 ms    16 ms    16 ms  lo-0-v6.ear1.Dallas3.Level3.net [2001:1900::3:1a2]
  7    69 ms    68 ms    68 ms  CHOOPA-LLC.ear1.Dallas3.Level3.net [2001:1900:2100::59ca]
  8     *       68 ms    69 ms  ethernetae2-er1-q8.dal4.constant.com [2001:19f0:fc00::a4e:505]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11    69 ms    74 ms    66 ms  2001:19f0:6401:148c:5400:1ff:fee0:c981

Trace complete.

 

Link to post
Share on other sites

From my end, the latency spike shows up at a different IP, in this case hop #15 due to routing from Ireland.  My connection doesn't appear to support reverse DNS resolution, probably due to being 4G based.

 

Tracing route to dallas.testmy.net [45.32.203.96]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.5.1
  2     *        *        *     Request timed out.
  3    31 ms    21 ms    29 ms  172.16.0.133
  4    38 ms    29 ms    24 ms  172.24.194.174
  5    35 ms    23 ms    19 ms  212.2.180.90
  6    22 ms    22 ms    31 ms  212.2.180.89
  7    25 ms    62 ms    19 ms  193.95.129.239
  8    56 ms    24 ms    21 ms  193.95.129.185
  9    35 ms    51 ms    23 ms  166.49.168.128
 10    60 ms    75 ms    46 ms  166.49.208.170
 11    34 ms    28 ms    32 ms  166.49.164.94
 12    43 ms    59 ms    30 ms  212.119.4.140
 13    76 ms    64 ms    38 ms  129.250.4.140
 14    58 ms    35 ms    37 ms  129.250.2.183
 15   114 ms     *        *     129.250.2.111
 16   138 ms   138 ms   133 ms  129.250.5.12
 17   195 ms   199 ms   137 ms  129.250.3.244
 18   154 ms   131 ms   140 ms  128.241.219.54
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22   177 ms   145 ms   138 ms  45.32.203.96

Trace complete.

 

Edit: Sorry I should have checked.  From further tests, it looks like the transatlantic hop latency from Ireland to US and then from there to Dallas at hop #16.

 

Link to post
Share on other sites

well if it has anything to do with the storms lately I know Monday we could not broadcast our iRacing League race as the Head Guy doing the 4K Live streaming lives in Texas and He was without Power Internet  anything , I think his el even went off right after contacting us.

Link to post
Share on other sites

Noticing latency come down on my sensor. Hard for me to tell if things are better bandwidth wise because I'm getting a shaky connection everywhere for some reason right now. It was fine earlier. Normally fine. Oh well, that's why TMN is here.  Let's test it!

 

Latency wise, it seems to have cleared up.

 

Previously I was focused on a different server (Toronto) and you can see where I switched to Dallas when your post came in. Just recently it started to clear up. 

 

Screen Shot 2021-05-13 at 2.42.16 AM.png

 

This is a tool you'll all have access to soon. The expansions prior to release will make it even more useful. I don't want to say too much before the product is in your hands.

 

I'll just say, you can do interesting things that may be useful to certain people. Useful to me, usually means others will find it useful.

 

Initially this will be exclusive to members. PM me with "BETA ME!" if you want to be part of the beta group.

 

Here's my latest traceroute

 

traceroute dallas.testmy.net
TRACEROUTE to dallas.testmy.net (45.32.203.96), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  0.822 ms  0.386 ms  0.298 ms
 2  cm-1-acr01.monument.co.denver.comcast.net (96.120.13.101)  10.712 ms  8.154 ms  9.836 ms
 3  ae-251-1203-rur01.monument.co.denver.comcast.net (96.110.242.73)  8.213 ms  12.149 ms  11.754 ms
 4  ae-12-ar01.denver.co.denver.comcast.net (162.151.50.41)  22.610 ms  10.198 ms  14.888 ms
 5  be-36041-cs04.1601milehigh.co.ibone.comcast.net (96.110.43.253)  13.292 ms
    be-36011-cs01.1601milehigh.co.ibone.comcast.net (96.110.43.241)  14.948 ms
    be-36041-cs04.1601milehigh.co.ibone.comcast.net (96.110.43.253)  9.451 ms
 6  be-3302-pe02.910fifteenth.co.ibone.comcast.net (96.110.38.122)  9.397 ms
    be-3402-pe02.910fifteenth.co.ibone.comcast.net (96.110.38.126)  13.430 ms  11.052 ms
 7  ae3-6.cr4-was1.ip4.gtt.net (173.241.130.117)  9.545 ms  10.057 ms  9.506 ms
 8  ae9.cr0-dal2.ip4.gtt.net (89.149.184.97)  29.847 ms  31.398 ms  30.328 ms
 9  ip4.gtt.net (173.205.43.82)  26.588 ms  28.248 ms  26.254 ms
10  * * *
11  * * *
12  * * *
13  dallas.testmy.net (45.32.203.96)  25.951 ms !Z  25.291 ms !Z  25.839 ms !Z

 

like I'd expect.

 

But again, hard for me to test bandwidth at home when my connection is now having bandwidth issues everywhere. I test between TMN servers and it's been fine the entire time btw.

 

And yes, reset my modem and router.     :-P 

Link to post
Share on other sites

CA3LE

I did a couple of trace routes for you.

My speed is right the max speed I pay for to a little above.

That is to the Dallas server.

This is the to Dallas trace route:

Tracing route to dallas.testmy.net [45.32.203.96]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    13 ms     9 ms    10 ms  173-219-226-228.suddenlink.net [173.219.226.228]
  4    41 ms    31 ms    28 ms  173-219-233-250.suddenlink.net [173.219.233.250]
  5     *        *       30 ms  dls-b23-link.ip.twelve99.net [213.248.88.228]
  6    27 ms    25 ms    25 ms  ntt-ic325660-dls-b23.ip.twelve99-cust.net [62.115.156.249]
  7    26 ms    25 ms    25 ms  ae-7.r25.dllstx09.us.bb.gin.ntt.net [129.250.5.25]
  8    25 ms    25 ms    26 ms  ae-1.a01.dllstx09.us.bb.gin.ntt.net [129.250.3.30]
  9    27 ms    25 ms    25 ms  ae-0.choopa.dllstx09.us.bb.gin.ntt.net [128.241.219.54]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13    27 ms    35 ms    26 ms  dallas.testmy.net [45.32.203.96]

Trace complete.

 

I hope I did this correctly to the Australia server:

Just for a long distance comparison.

Tracing route to AU.testmy.net [45.32.189.44]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     9 ms     8 ms     9 ms  173-219-226-228.suddenlink.net [173.219.226.228]
  4    29 ms    31 ms    30 ms  173-219-233-250.suddenlink.net [173.219.233.250]
  5    26 ms    27 ms    24 ms  dls-b23-link.ip.twelve99.net [213.248.88.228]
  6     *       25 ms    25 ms  dls-b24-link.ip.twelve99.net [62.115.137.107]
  7    56 ms    56 ms    56 ms  las-b22-link.ip.twelve99.net [62.115.118.247]
  8    87 ms    54 ms    54 ms  las-b24-link.ip.twelve99.net [62.115.125.163]
  9    58 ms    55 ms    56 ms  superloop348779-svc066166-ic348780.ip.twelve99-cust.net [62.115.179.17]
 10   204 ms   204 ms   203 ms  hundredgige0-0-1-2-120.bdr01-ipt-47bourke-syd.au.superloop.net.co [103.200.13.169]
 11   249 ms   230 ms   248 ms  27.122.122.95
 12     *        *        *     Request timed out.
 13   270 ms   269 ms   270 ms  180.189.25.6
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17   208 ms   209 ms   208 ms  au.testmy.net [45.32.189.44]

Trace complete.

 

Link to post
Share on other sites

From Dodge City ,Kansas

LTE atm, this is a laptop hitting the phones hotspot

traceroute to dallas.testmy.net (45.32.203.96), 30 hops max, 60 byte packets
 1  _gateway (172.20.10.1)  3.740 ms  5.916 ms  5.843 ms
 2  130.sub-66-174-67.myvzw.com (66.174.67.130)  61.470 ms  74.303 ms  74.270 ms
 3  * * *
 4  66.sub-69-83-132.myvzw.com (69.83.132.66)  77.846 ms  77.801 ms  77.763 ms
 5  * * *
 6  200.sub-69-83-130.myvzw.com (69.83.130.200)  85.975 ms  31.239 ms  37.750 ms
 7  136.sub-69-83-131.myvzw.com (69.83.131.136)  45.644 ms  50.517 ms  50.476 ms
 8  137.sub-69-83-131.myvzw.com (69.83.131.137)  50.409 ms  77.054 ms  50.276 ms
 9  0.ae3.BR3.CHI13.ALTER.NET (140.222.5.165)  61.268 ms  61.135 ms  61.059 ms
10  customer.alter.net (152.179.105.70)  45.062 ms  41.498 ms  53.552 ms
11  ae9.cr0-dal2.ip4.gtt.net (89.149.184.97)  73.244 ms  73.192 ms  73.153 ms
12  ip4.gtt.net (173.205.43.82)  67.023 ms  73.927 ms *
13  * * *
14  * * *
15  * * *
16  dallas.testmy.net (45.32.203.96)  58.835 ms !X  81.679 ms !X  87.254 ms !X

 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...