Okay, everyone's getting moved who requested it for OKC. It's not ready yet but it's a beta and I also haven't got to tidying it up. This way you guys actually get to be there for some form of actual testing without me taking forever. And that way if server crashes I can be there while it happens.
Reinstalls won't work, you'll be stuck without an OS -- I can probably just sync this after I'm done
IPv6? What's that? Okay serious we have it I just haven't added it to SolusVM, I'm OCD about how it gets done (I guess I could just do something temporary.)
If anyone has too low RAM on their service and I noticed it, I added some more (like 128MB --> 512MB.) This won't be done for any future OKC migrations because I don't want it used as an upgrade memory hack.
Your bandwidth has been doubled! Okay no @tulipyun not yet give me a minute
High chance your IPv4 changes or the gateway changes if I decide to split everything up.
You're technically on a Windows node, it doesn't mean much usually, it might transition into being a Linux one. Anything weird let me know. But you might also get kicked off later.
Okay it's pretty cool how I recognize every username so far, one big family. This is just for Ryzens, not for anyone who wanted storage (one person.)
@VirMach said:
Okay, everyone's getting moved who requested it for OKC. It's not ready yet but it's a beta and I also haven't got to tidying it up. This way you guys actually get to be there for some form of actual testing without me taking forever. And that way if server crashes I can be there while it happens.
Has everyone moved?
It looks like Ticket #535004 Migrate to Oklahoma has not been approved.
@VirMach said:
Okay, everyone's getting moved who requested it for OKC. It's not ready yet but it's a beta and I also haven't got to tidying it up. This way you guys actually get to be there for some form of actual testing without me taking forever. And that way if server crashes I can be there while it happens.
Has everyone moved?
It looks like Ticket #535004 Migrate to Oklahoma has not been approved.
I started yours around the time when you made your comment.
@VirMach said:
Okay, everyone's getting moved who requested it for OKC. It's not ready yet but it's a beta and I also haven't got to tidying it up. This way you guys actually get to be there for some form of actual testing without me taking forever. And that way if server crashes I can be there while it happens.
Has everyone moved?
It looks like Ticket #535004 Migrate to Oklahoma has not been approved.
Okay yours is completing now. I'm adding the new IP.
UPDATE -- New IP has been added.
UPDATE -- It is now the main IP.
UPDATE -- Old IP has been removed.
UPDATE -- Bandwidth has been doubled to 20TB (wow nice plan)
UPDATE -- Memory changed from 128MB to 512MB
UPDATE -- Reconfiguring
UPDATE -- Added your ticket ID to the sheet
UPDATE -- Added your user ID to the sheet
UPDATE -- Added your IP to the sheet
UPDATE -- Added your username to the sheet
UPDATE -- Marked ticket as complete, done!
Alright let me know if you find any weird/bad routes and I'll see what can be done about it, or if you notice any surprisingly good ones let me know about them. If it's to your location you can private message it or make a ticket and provide the ID here.
Especially if you also have a server nearby like in Dallas to compare.
Worst route I've seen is probably 26ms to Kansas City, and it's Cogent, and geolocations for the hops are Michigan, Nebraska, Texas, Colorado. But based on Cogent's map, it'd be slightly off but I think it's actually somehow jumping up to Nebraska, Denver, to Dallas and back up.
I was curious what Lumen would do, it goes OKC --> Tulsa --> Dallas --> Kansas City in 13ms but this was a pretty unreliable test IP (the ping.pe looks like their router is about to melt, almost all red, so I couldn't get a comparison.) Found another one from a datacenter I recognized, and it goes through our Hurricane Electric IX, and I guess HE does it better for this, actually just goes to Kansas City in 7ms. And Dallas to this one is 11ms.
Lumen does this more than I'd like it to do (zero) and I've contacted them to see what the best approach would be to try to make it prefer sending everything to Dallas less since they do technically have lines going to Kansas/Denver/Chicago.
Lumen seems to be pretty solid from further away though, but we're paying so much for them it'd be nice if they're also able to connect to major cities around OKC without doing that. Funny enough I kind of wanted to tell them "we could've just done Cogent" except Cogent seems to always be one step ahead in picking a route that actually makes no sense.
TL;DR. Seems quite good overall. Ping from home is roughly 126ms which is basically what you would expect (my ISP directly peers with Lumen so it pretty much goes to Paris and then directly to Oklahoma)
I've also noticed latency to Kansas City is a bit over the place (26ms/30ms). One of my boxes goes to Chicago and then directly to Oklahoma. Not that bad, but roughly 13ms or so increase.
My other box goes directly though Cogent until it hits Lumen basically. (Omaha - Denver - Tulsa)
That one makes us look good, I like it. Time to figure out what's going on with Hivelocity Chicago (and T-Mobile Fiber Denver.)
Okay interesting, so Hivelocity Chicago is through Lumen, that's good. But I have to figure out how to make BGP to do that. I'm sure it'll be really easy. Wait, what's BGP? Ohhh... ohh... oh.
I haven't found a good route to Denver except that one, okay I've hacked the mainframe, I'm in. That one is Lumen as well. That's real good. Alright time to contact Lumen and see if they can make this easier.
@cybertech said:
wait what happened to virtfusion?
@cybertech said:
wait what happened to virtfusion?
I think VirtFusion was a "maybe" experiment
It's not for these Ryzen servers. I mean I suppose it could be... I guess I never thought of it that way. I'd just need to trick WHMCS into using it for one location as I don't really want to make an entire OKC duplicate for each plan. For another product line on different servers, it made more sense. Or we could have sub-versions for Ryzen nodes.
Orrr.... I could finally get one of the other nodes up, it's crazy how backwards all our plans ended up going, these Ryzen were supposed to probably be last. Same with IPv6.
@VirMach said: Worst route I've seen is probably 26ms to Kansas City, and it's Cogent, and geolocations for the hops are Michigan, Nebraska, Texas, Colorado. But based on Cogent's map, it'd be slightly off but I think it's actually somehow jumping up to Nebraska, Denver, to Dallas and back up.
To KC 24.756 ms
1 _gateway (193.58.147.1) 2.695 ms 2.667 ms 2.648 ms
2 23.136.108.50 (23.136.108.50) 0.384 ms 0.364 ms 0.421 ms
3 1-1-c17-2.ear2.Tulsa2.Level3.net (4.43.131.85) 3.003 ms 2.982 ms 3.006 ms
4 * * *
5 * * 1299-3356-dal.sp.lumen.tech (4.68.74.166) 8.541 ms
6 * * dls-bb2-link.ip.twelve99.net (62.115.138.64) 8.520 ms
7 kanc-bb2-link.ip.twelve99.net (62.115.139.188) 13.507 ms 13.487 ms 13.311 ms
8 kanc-b3-link.ip.twelve99.net (62.115.113.81) 13.440 ms 13.572 ms 13.500 ms
9 nocix-ic-372038.ip.twelve99-cust.net (80.239.132.187) 13.077 ms 13.089 ms nocix-ic-372039.ip.twelve99-cust.net (62.115.147.181) 13.060 ms
10 100ge-0-38.edge-1.clay.mci.us.as32097.net (69.30.209.201) 13.417 ms 13.559 ms 100ge-103.dist-1.101.swift.mci.us.as32097.net (69.30.209.225) 24.634 ms
11 100ge-53-1.edge-2.101.swift.mci.us.as32097.net (69.30.209.200) 12.991 ms 69.197.140.1 (69.197.140.1) 24.756 ms 24.771 ms
From KC 19.834 ms
1 _gateway (69.197.140.1) 0.167 ms 0.252 ms 0.244 ms
2 100ge-55-1.edge-2.101.swift.mci.us.as32097.net (69.30.209.224) 0.199 ms 0.213 ms 0.202 ms
3 kanc-b3-link.ip.twelve99.net (80.239.132.186) 0.598 ms 0.606 ms *
4 be5627.ccr22.mci01.atlas.cogentco.com (154.54.90.249) 1.370 ms 1.370 ms 1.611 ms
5 be5590.ccr31.oma02.atlas.cogentco.com (154.54.47.38) 4.576 ms * 4.843 ms
6 ae5.5.ear2.Tulsa2.net.lumen.tech (4.69.227.145) 10.317 ms be3802.ccr21.den01.atlas.cogentco.com (154.54.165.77) 15.064 ms ae5.5.ear2.Tulsa2.net.lumen.tech (4.69.227.145) 10.300 ms
7 be2766.ccr41.ord03.atlas.cogentco.com (154.54.46.178) 12.946 ms be2401.rcr21.b006467-6.den01.atlas.cogentco.com (154.54.88.42) 15.151 ms VIRTUAL-MAC.ear2.Tulsa2.Level3.net (4.43.131.86) 13.640 ms
8 orange.lax05.atlas.cogentco.com (154.54.10.2) 14.464 ms 14.429 ms 14.677 ms
9 193.58.147.1 (193.58.147.1) 19.861 ms 19.854 ms 19.834 ms
To Dallas 8.822 ms
1 _gateway (193.58.147.1) 4.330 ms 4.318 ms 4.314 ms
2 23.136.108.50 (23.136.108.50) 0.370 ms 0.394 ms 0.388 ms
3 1-1-c17-2.ear2.Tulsa2.Level3.net (4.43.131.85) 3.024 ms 3.016 ms 3.063 ms
4 ae1.3515.edge1.Dallas2.net.lumen.tech (4.69.209.114) 8.962 ms ae1.3509.edge2.Dallas2.net.lumen.tech (4.69.206.165) 8.244 ms 8.240 ms
5 * * *
6 be2763.ccr31.dfw01.atlas.cogentco.com (154.54.28.73) 8.877 ms 8.901 ms 8.941 ms
7 be8551.rcr71.b059724-0.dfw01.atlas.cogentco.com (154.54.92.105) 9.382 ms be8553.rcr71.b059724-0.dfw01.atlas.cogentco.com (154.54.95.29) 9.529 ms 9.632 ms
8 be4693.nr61.b059724-0.dfw01.atlas.cogentco.com (154.24.5.166) 9.591 ms 9.592 ms 9.465 ms
9 38.32.15.66 (38.32.15.66) 8.707 ms 15.827 ms 15.815 ms
10 64.44.158.1 (64.44.158.1) 8.882 ms 8.826 ms 8.822 ms
From Dallas 16.887 ms
1 1-148-44-64.reverse-dns (64.44.148.1) 0.172 ms 0.159 ms 0.176 ms
2 * * *
3 be4693.rcr71.b059724-0.dfw01.atlas.cogentco.com (154.24.5.165) 1.055 ms 1.170 ms 1.275 ms
4 be8553.ccr32.dfw01.atlas.cogentco.com (154.54.95.30) 1.249 ms 1.277 ms be8551.ccr31.dfw01.atlas.cogentco.com (154.54.92.106) 1.274 ms
5 be2763.ccr41.dfw03.atlas.cogentco.com (154.54.28.74) 1.242 ms be2764.ccr41.dfw03.atlas.cogentco.com (154.54.47.214) 1.144 ms 1.303 ms
6 lumen.dfw03.atlas.cogentco.com (154.54.10.18) 8.863 ms 1.620 ms 6.580 ms
7 ae2.13.ear2.Tulsa2.net.lumen.tech (4.69.136.210) 6.095 ms 6.112 ms 6.034 ms
8 VIRTUAL-MAC.ear2.Tulsa2.Level3.net (4.43.131.86) 8.885 ms 8.889 ms 8.900 ms
9 193.58.147.1 (193.58.147.1) 16.932 ms 16.910 ms 16.887 ms
@VirMach said: Worst route I've seen is probably 26ms to Kansas City, and it's Cogent, and geolocations for the hops are Michigan, Nebraska, Texas, Colorado. But based on Cogent's map, it'd be slightly off but I think it's actually somehow jumping up to Nebraska, Denver, to Dallas and back up.
To KC 24.756 ms
1 _gateway (193.58.147.1) 2.695 ms 2.667 ms 2.648 ms
2 23.136.108.50 (23.136.108.50) 0.384 ms 0.364 ms 0.421 ms
3 1-1-c17-2.ear2.Tulsa2.Level3.net (4.43.131.85) 3.003 ms 2.982 ms 3.006 ms
4 * * *
5 * * 1299-3356-dal.sp.lumen.tech (4.68.74.166) 8.541 ms
6 * * dls-bb2-link.ip.twelve99.net (62.115.138.64) 8.520 ms
7 kanc-bb2-link.ip.twelve99.net (62.115.139.188) 13.507 ms 13.487 ms 13.311 ms
8 kanc-b3-link.ip.twelve99.net (62.115.113.81) 13.440 ms 13.572 ms 13.500 ms
9 nocix-ic-372038.ip.twelve99-cust.net (80.239.132.187) 13.077 ms 13.089 ms nocix-ic-372039.ip.twelve99-cust.net (62.115.147.181) 13.060 ms
10 100ge-0-38.edge-1.clay.mci.us.as32097.net (69.30.209.201) 13.417 ms 13.559 ms 100ge-103.dist-1.101.swift.mci.us.as32097.net (69.30.209.225) 24.634 ms
11 100ge-53-1.edge-2.101.swift.mci.us.as32097.net (69.30.209.200) 12.991 ms 69.197.140.1 (69.197.140.1) 24.756 ms 24.771 ms
From KC 19.834 ms
1 _gateway (69.197.140.1) 0.167 ms 0.252 ms 0.244 ms
2 100ge-55-1.edge-2.101.swift.mci.us.as32097.net (69.30.209.224) 0.199 ms 0.213 ms 0.202 ms
3 kanc-b3-link.ip.twelve99.net (80.239.132.186) 0.598 ms 0.606 ms *
4 be5627.ccr22.mci01.atlas.cogentco.com (154.54.90.249) 1.370 ms 1.370 ms 1.611 ms
5 be5590.ccr31.oma02.atlas.cogentco.com (154.54.47.38) 4.576 ms * 4.843 ms
6 ae5.5.ear2.Tulsa2.net.lumen.tech (4.69.227.145) 10.317 ms be3802.ccr21.den01.atlas.cogentco.com (154.54.165.77) 15.064 ms ae5.5.ear2.Tulsa2.net.lumen.tech (4.69.227.145) 10.300 ms
7 be2766.ccr41.ord03.atlas.cogentco.com (154.54.46.178) 12.946 ms be2401.rcr21.b006467-6.den01.atlas.cogentco.com (154.54.88.42) 15.151 ms VIRTUAL-MAC.ear2.Tulsa2.Level3.net (4.43.131.86) 13.640 ms
8 orange.lax05.atlas.cogentco.com (154.54.10.2) 14.464 ms 14.429 ms 14.677 ms
9 193.58.147.1 (193.58.147.1) 19.861 ms 19.854 ms 19.834 ms
That's interesting, and confusing. So is that the same routes I described except Cogent going from Omaha --> Denver --> Dallas --> OKC ends up being better than... oh I see it now, they handed it over to Telia from Dallas. And the Cogent one improved because of Telia in that case.
In my comparison, Telia wasn't involved I guess, just Cogent. It would've probably been helpful if I posted it, luckily I have the tab up. Oh nope it's not because of the Telia, it went to "Chicago" instead of "LAX" or.. is it the "Michigan" -- okay whatever I'm done playing Cogent placeholder hostname shuffle because it also geolocates to the that incorrect hostname still and I don't feel like triangulating each IP address.
HOST: ulanqab-alibaba (Jining - Ulanqab is a common naming for datacenters in this region of Inner Mongolia, Jining being a city within Ulanqab league/prefecture)
NextTrace v1.4.0 2025-04-16T01:10:07Z dccc41b
[NextTrace API] preferred API IP - 45.88.193.28 - 133.59ms - 🐠 (Relay) → Misaka.LAX
IP Geo Data Provider: LeoMoeAPI
traceroute to 221.183.166.210, 30 hops max, 52 bytes payload, ICMP mode
1 193.58.147.1 AS25693 Oklahoma City Oklahoma United States IDC
2.21 ms / 9.61 ms / 8.84 ms
2 23.136.108.50 AS25693 Oklahoma City Oklahoma United States
0.44 ms / 0.37 ms / 0.45 ms
3 4.43.131.85 AS3356 Tulsa Oklahoma United States lumen.com
1-1-c17-2.ear2.Tulsa2.Level3.net 3.09 ms / 3.12 ms / 3.13 ms
4 *
5 4.68.75.218 AS3356 Los Angeles California United States lumen.com
58453-3356-lax.sp.lumen.tech 38.96 ms / 38.95 ms / 39.05 ms
6 223.120.6.217 AS58453 [CMI-INT] Los Angeles California United States cmi.chinamobile.com 移动
38.94 ms / 39.12 ms / 39.59 ms
7 223.120.12.214 AS58453 [CMI-INT] Shanghai China CMI-CM-Peer cmi.chinamobile.com 移动
223.64 ms / 236.04 ms / 223.60 ms
8 221.183.55.110 AS9808 [CMNET] Beijing China X-I chinamobileltd.com 移动
222.25 ms / 222.22 ms / 222.26 ms
9 221.183.25.201 AS9808 [CMNET] Beijing China I-C chinamobileltd.com 移动
222.29 ms / 222.27 ms / 222.27 ms
10 *
11 *
12 221.183.166.210 AS9808 [CMNET] Guangzhou Guangdong Province China chinamobileltd.com
227.61 ms / 227.52 ms / 227.54 ms
From NE Scotland:
3 ae50-ner001.msp.as13285.net (78.144.1.33) 13.928 ms 14.179 ms 14.436 ms
4 ae50-scr001-msp.as13285.net (78.144.1.32) 14.737 ms 15.337 ms 15.668 ms
5 ae60-scr101.thw.as13285.net (78.144.1.110) 21.508 ms 22.113 ms 29.658 ms
6 ae54.edge7.london1.level3.net (217.163.47.149) 30.129 ms 23.205 ms 28.596 ms
7 ae5.5.ear2.tulsa2.net.lumen.tech (4.69.227.145) 118.941 ms 119.222 ms 119.411 ms
8 virtual-mac.ear2.tulsa2.level3.net (4.43.131.86) 122.410 ms 122.703 ms 122.947 ms
9 23.136.108.51 (23.136.108.51) 123.682 ms 123.938 ms 131.552 ms
10 193.58.147.xxx (193.58.147.xxx) 123.228 ms 120.955 ms 121.567 ms
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural. It wisnae me! A big boy done it and ran away. || NVMe2G for life! until death (the end is nigh).
Some high quality Lumen (albeit loves to backhaul through DFW) from all tests I've done.
Do we need to play some sort of Saw type game to get that $25 dedi @VirMach ? This would be the perfect 'not just another DC in the tri-state area' for backups and I need one more bare metal server if it's possible. Let me know who / what I need to sacrifice to get in on that deal.
Comments
I see imok needs even moooooooooar
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
https://lowendspirit.com/discussion/comment/198835/#Comment_198835
Okay, everyone's getting moved who requested it for OKC. It's not ready yet but it's a beta and I also haven't got to tidying it up. This way you guys actually get to be there for some form of actual testing without me taking forever. And that way if server crashes I can be there while it happens.
Okay it's pretty cool how I recognize every username so far, one big family. This is just for Ryzens, not for anyone who wanted storage (one person.)
Has everyone moved?
It looks like Ticket #535004 Migrate to Oklahoma has not been approved.
Virtfuuuuuuuuuuuuuuuuuuuuuuusion
I bench YABS 24/7/365 unless it's a leap year.
I started yours around the time when you made your comment.
Okay yours is completing now. I'm adding the new IP.
UPDATE -- New IP has been added.
UPDATE -- It is now the main IP.
UPDATE -- Old IP has been removed.
UPDATE -- Bandwidth has been doubled to 20TB (wow nice plan)
UPDATE -- Memory changed from 128MB to 512MB
UPDATE -- Reconfiguring
UPDATE -- Added your ticket ID to the sheet
UPDATE -- Added your user ID to the sheet
UPDATE -- Added your IP to the sheet
UPDATE -- Added your username to the sheet
UPDATE -- Marked ticket as complete, done!
Alright let me know if you find any weird/bad routes and I'll see what can be done about it, or if you notice any surprisingly good ones let me know about them. If it's to your location you can private message it or make a ticket and provide the ID here.
Especially if you also have a server nearby like in Dallas to compare.
Any other feedback let me know.
Worst route I've seen is probably 26ms to Kansas City, and it's Cogent, and geolocations for the hops are Michigan, Nebraska, Texas, Colorado. But based on Cogent's map, it'd be slightly off but I think it's actually somehow jumping up to Nebraska, Denver, to Dallas and back up.
I was curious what Lumen would do, it goes OKC --> Tulsa --> Dallas --> Kansas City in 13ms but this was a pretty unreliable test IP (the ping.pe looks like their router is about to melt, almost all red, so I couldn't get a comparison.) Found another one from a datacenter I recognized, and it goes through our Hurricane Electric IX, and I guess HE does it better for this, actually just goes to Kansas City in 7ms. And Dallas to this one is 11ms.
Lumen does this more than I'd like it to do (zero) and I've contacted them to see what the best approach would be to try to make it prefer sending everything to Dallas less since they do technically have lines going to Kansas/Denver/Chicago.
Lumen seems to be pretty solid from further away though, but we're paying so much for them it'd be nice if they're also able to connect to major cities around OKC without doing that. Funny enough I kind of wanted to tell them "we could've just done Cogent" except Cogent seems to always be one step ahead in picking a route that actually makes no sense.
Had to run these...
yabs.sh
nws.sh
The control panel information has been updated!
VNC connection successful!
The gateway is configured correctly!
The gateway is globally accessible!
The main IP is set correctly!
Network configuration file is wrong, network interface should be ens3, auto-generated configuration is eth0, change it correctly!
Main IP is online!
Main IP is globally reachable!
wait what happened to virtfusion?
I bench YABS 24/7/365 unless it's a leap year.
This is a test from (almost) all my servers:
https://globalping.io/?measurement=zWFzj5EzGMeD2DTe
TL;DR. Seems quite good overall. Ping from home is roughly 126ms which is basically what you would expect (my ISP directly peers with Lumen so it pretty much goes to Paris and then directly to Oklahoma)
I've also noticed latency to Kansas City is a bit over the place (26ms/30ms). One of my boxes goes to Chicago and then directly to Oklahoma. Not that bad, but roughly 13ms or so increase.
My other box goes directly though Cogent until it hits Lumen basically. (Omaha - Denver - Tulsa)
EDIT: RIPE Atlas measurement (1000 US probes)
https://atlas.ripe.net/measurements/102150730/overview
MTR to Kuroit in Dallas, TX
MTR to ExtraVM in Dallas, TX
MTR to DartNode in Houston, TX
MTR to Kuroit in Ashburn, VA
MTR to LittleCreekHosting in Durham, NC
MTR to Crunchbits in Liberty Lake, WA
MTR to Crunchbits in Allentown, PA
MTR to GreenCloud in Chicago, IL
MTR to GreenCloud in Jacksonville, FL
MTR to HostHatch in Los Angeles, CA
MTR to HostCram in Salt Lake City, UT
I think VirtFusion was a "maybe" experiment
That one makes us look good, I like it. Time to figure out what's going on with Hivelocity Chicago (and T-Mobile Fiber Denver.)
Okay interesting, so Hivelocity Chicago is through Lumen, that's good. But I have to figure out how to make BGP to do that. I'm sure it'll be really easy. Wait, what's BGP? Ohhh... ohh... oh.
I haven't found a good route to Denver except that one, okay I've hacked the mainframe, I'm in. That one is Lumen as well. That's real good. Alright time to contact Lumen and see if they can make this easier.
You didn't say it enough.
It's not for these Ryzen servers. I mean I suppose it could be... I guess I never thought of it that way. I'd just need to trick WHMCS into using it for one location as I don't really want to make an entire OKC duplicate for each plan. For another product line on different servers, it made more sense. Or we could have sub-versions for Ryzen nodes.
Orrr.... I could finally get one of the other nodes up, it's crazy how backwards all our plans ended up going, these Ryzen were supposed to probably be last. Same with IPv6.
I'm sorry, what? I was not expecting that at all when opening that. Wow. How did you even... find that many cities in the world.
Okay I need to figure out a feasible way to use this data.
To KC 24.756 ms
1 _gateway (193.58.147.1) 2.695 ms 2.667 ms 2.648 ms
2 23.136.108.50 (23.136.108.50) 0.384 ms 0.364 ms 0.421 ms
3 1-1-c17-2.ear2.Tulsa2.Level3.net (4.43.131.85) 3.003 ms 2.982 ms 3.006 ms
4 * * *
5 * * 1299-3356-dal.sp.lumen.tech (4.68.74.166) 8.541 ms
6 * * dls-bb2-link.ip.twelve99.net (62.115.138.64) 8.520 ms
7 kanc-bb2-link.ip.twelve99.net (62.115.139.188) 13.507 ms 13.487 ms 13.311 ms
8 kanc-b3-link.ip.twelve99.net (62.115.113.81) 13.440 ms 13.572 ms 13.500 ms
9 nocix-ic-372038.ip.twelve99-cust.net (80.239.132.187) 13.077 ms 13.089 ms nocix-ic-372039.ip.twelve99-cust.net (62.115.147.181) 13.060 ms
10 100ge-0-38.edge-1.clay.mci.us.as32097.net (69.30.209.201) 13.417 ms 13.559 ms 100ge-103.dist-1.101.swift.mci.us.as32097.net (69.30.209.225) 24.634 ms
11 100ge-53-1.edge-2.101.swift.mci.us.as32097.net (69.30.209.200) 12.991 ms 69.197.140.1 (69.197.140.1) 24.756 ms 24.771 ms
From KC 19.834 ms
1 _gateway (69.197.140.1) 0.167 ms 0.252 ms 0.244 ms
2 100ge-55-1.edge-2.101.swift.mci.us.as32097.net (69.30.209.224) 0.199 ms 0.213 ms 0.202 ms
3 kanc-b3-link.ip.twelve99.net (80.239.132.186) 0.598 ms 0.606 ms *
4 be5627.ccr22.mci01.atlas.cogentco.com (154.54.90.249) 1.370 ms 1.370 ms 1.611 ms
5 be5590.ccr31.oma02.atlas.cogentco.com (154.54.47.38) 4.576 ms * 4.843 ms
6 ae5.5.ear2.Tulsa2.net.lumen.tech (4.69.227.145) 10.317 ms be3802.ccr21.den01.atlas.cogentco.com (154.54.165.77) 15.064 ms ae5.5.ear2.Tulsa2.net.lumen.tech (4.69.227.145) 10.300 ms
7 be2766.ccr41.ord03.atlas.cogentco.com (154.54.46.178) 12.946 ms be2401.rcr21.b006467-6.den01.atlas.cogentco.com (154.54.88.42) 15.151 ms VIRTUAL-MAC.ear2.Tulsa2.Level3.net (4.43.131.86) 13.640 ms
8 orange.lax05.atlas.cogentco.com (154.54.10.2) 14.464 ms 14.429 ms 14.677 ms
9 193.58.147.1 (193.58.147.1) 19.861 ms 19.854 ms 19.834 ms
To Dallas 8.822 ms
1 _gateway (193.58.147.1) 4.330 ms 4.318 ms 4.314 ms
2 23.136.108.50 (23.136.108.50) 0.370 ms 0.394 ms 0.388 ms
3 1-1-c17-2.ear2.Tulsa2.Level3.net (4.43.131.85) 3.024 ms 3.016 ms 3.063 ms
4 ae1.3515.edge1.Dallas2.net.lumen.tech (4.69.209.114) 8.962 ms ae1.3509.edge2.Dallas2.net.lumen.tech (4.69.206.165) 8.244 ms 8.240 ms
5 * * *
6 be2763.ccr31.dfw01.atlas.cogentco.com (154.54.28.73) 8.877 ms 8.901 ms 8.941 ms
7 be8551.rcr71.b059724-0.dfw01.atlas.cogentco.com (154.54.92.105) 9.382 ms be8553.rcr71.b059724-0.dfw01.atlas.cogentco.com (154.54.95.29) 9.529 ms 9.632 ms
8 be4693.nr61.b059724-0.dfw01.atlas.cogentco.com (154.24.5.166) 9.591 ms 9.592 ms 9.465 ms
9 38.32.15.66 (38.32.15.66) 8.707 ms 15.827 ms 15.815 ms
10 64.44.158.1 (64.44.158.1) 8.882 ms 8.826 ms 8.822 ms
From Dallas 16.887 ms
1 1-148-44-64.reverse-dns (64.44.148.1) 0.172 ms 0.159 ms 0.176 ms
2 * * *
3 be4693.rcr71.b059724-0.dfw01.atlas.cogentco.com (154.24.5.165) 1.055 ms 1.170 ms 1.275 ms
4 be8553.ccr32.dfw01.atlas.cogentco.com (154.54.95.30) 1.249 ms 1.277 ms be8551.ccr31.dfw01.atlas.cogentco.com (154.54.92.106) 1.274 ms
5 be2763.ccr41.dfw03.atlas.cogentco.com (154.54.28.74) 1.242 ms be2764.ccr41.dfw03.atlas.cogentco.com (154.54.47.214) 1.144 ms 1.303 ms
6 lumen.dfw03.atlas.cogentco.com (154.54.10.18) 8.863 ms 1.620 ms 6.580 ms
7 ae2.13.ear2.Tulsa2.net.lumen.tech (4.69.136.210) 6.095 ms 6.112 ms 6.034 ms
8 VIRTUAL-MAC.ear2.Tulsa2.Level3.net (4.43.131.86) 8.885 ms 8.889 ms 8.900 ms
9 193.58.147.1 (193.58.147.1) 16.932 ms 16.910 ms 16.887 ms
That's interesting, and confusing. So is that the same routes I described except Cogent going from Omaha --> Denver --> Dallas --> OKC ends up being better than... oh I see it now, they handed it over to Telia from Dallas. And the Cogent one improved because of Telia in that case.
In my comparison, Telia wasn't involved I guess, just Cogent. It would've probably been helpful if I posted it, luckily I have the tab up. Oh nope it's not because of the Telia, it went to "Chicago" instead of "LAX" or.. is it the "Michigan" -- okay whatever I'm done playing Cogent placeholder hostname shuffle because it also geolocates to the that incorrect hostname still and I don't feel like triangulating each IP address.
I hope this isn't the standard way Cogent hands things off to Lumen in Dallas.
Here's some MTR data for the geographic locations I'm more interested in:
China(12)
#### Asia, Qingdao
DC514, AS37963
| Hop | HOST | Loss% | Snt | Last | Avg | Best | Wrst | StDev |
|:----|:-----------------|------:|----:|------:|------:|------:|------:|------:|
| 1 | 11.247.239.22 | 0.0% | 2 | 0.9 | 0.8 | 0.7 | 0.9 | 0.1 |
| 2 | 11.73.5.129 | 0.0% | 2 | 2.2 | 3.1 | 2.2 | 4.0 | 1.3 |
| 3 | 10.54.143.237 | 0.0% | 2 | 6.3 | 3.5 | 0.7 | 6.3 | 4.0 |
| 4 | 116.251.117.222 | 0.0% | 2 | 1.1 | 1.1 | 1.1 | 1.2 | 0.0 |
| 5 | 116.251.113.45 | 0.0% | 2 | 0.8 | 0.9 | 0.8 | 0.9 | 0.0 |
| 6 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 7 | 140.249.132.73 | 0.0% | 2 | 2.0 | 2.0 | 2.0 | 2.0 | 0.0 |
| 8 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 9 | 202.97.99.161 | 50.0% | 2 | 13.9 | 13.9 | 13.9 | 13.9 | 0.0 |
| 10 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 11 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 12 | 202.97.92.74 | 0.0% | 2 | 147.7 | 147.7 | 147.7 | 147.7 | 0.0 |
| 13 | 4.15.125.53 | 0.0% | 2 | 146.9 | 146.9 | 146.8 | 146.9 | 0.1 |
| 14 | 4.69.227.145 | 0.0% | 2 | 185.4 | 186.9 | 185.4 | 188.5 | 2.2 |
| 15 | 4.43.131.86 | 0.0% | 2 | 191.6 | 191.5 | 191.3 | 191.6 | 0.2 |
| 16 | 193.58.147.1 | 0.0% | 2 | 239.4 | 223.1 | 206.8 | 239.4 | 23.1 |
HOST: qingdao-alibaba
#### Asia, Chengdu
DC523, AS37963
| Hop | HOST | Loss% | Snt | Last | Avg | Best | Wrst | StDev |
|:----|:-----------------|------:|----:|------:|------:|------:|------:|------:|
| 1 | 11.202.9.2 | 50.0% | 2 | 0.6 | 0.6 | 0.6 | 0.6 | 0.0 |
| 2 | 11.73.2.205 | 0.0% | 2 | 0.9 | 1.0 | 0.9 | 1.0 | 0.0 |
| 3 | 11.88.170.249 | 0.0% | 2 | 0.7 | 0.7 | 0.6 | 0.7 | 0.0 |
| 4 | 45.112.221.42 | 0.0% | 2 | 1.4 | 1.4 | 1.3 | 1.4 | 0.1 |
| 5 | 116.251.119.138 | 0.0% | 2 | 4.1 | 3.0 | 2.0 | 4.1 | 1.5 |
| 6 | 101.207.253.225 | 0.0% | 2 | 1.6 | 1.6 | 1.6 | 1.6 | 0.0 |
| 7 | 119.6.197.225 | 0.0% | 2 | 8.4 | 5.7 | 3.1 | 8.4 | 3.7 |
| 8 | 219.158.106.249 | 0.0% | 2 | 39.4 | 39.3 | 39.2 | 39.4 | 0.1 |
| 9 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 10 | 219.158.6.206 | 0.0% | 2 | 36.0 | 36.0 | 35.9 | 36.0 | 0.1 |
| 11 | 219.158.97.178 | 0.0% | 2 | 178.2 | 177.3 | 176.5 | 178.2 | 1.1 |
| 12 | 4.53.209.77 | 0.0% | 2 | 191.4 | 191.7 | 191.4 | 191.9 | 0.3 |
| 13 | 4.69.227.145 | 0.0% | 2 | 228.7 | 228.7 | 228.7 | 228.8 | 0.0 |
| 14 | 4.43.131.86 | 0.0% | 2 | 227.1 | 226.6 | 226.1 | 227.1 | 0.7 |
| 15 | 193.58.147.1 | 50.0% | 2 | 234.9 | 234.9 | 234.9 | 234.9 | 0.0 |
HOST: chengdu-alibaba
#### Asia, Guangzhou
DC522, AS37963
| Hop | HOST | Loss% | Snt | Last | Avg | Best | Wrst | StDev |
|:----|:-----------------|------:|----:|------:|------:|------:|------:|------:|
| 1 | 10.231.251.10 | 0.0% | 2 | 0.5 | 0.6 | 0.5 | 0.7 | 0.1 |
| 2 | 11.73.14.177 | 0.0% | 2 | 0.4 | 0.4 | 0.4 | 0.4 | 0.0 |
| 3 | 11.73.25.173 | 0.0% | 2 | 0.4 | 0.4 | 0.4 | 0.4 | 0.0 |
| 4 | 11.73.48.129 | 0.0% | 2 | 0.7 | 0.7 | 0.7 | 0.7 | 0.0 |
| 5 | 11.94.57.209 | 0.0% | 2 | 0.8 | 0.9 | 0.8 | 0.9 | 0.1 |
| 6 | 10.54.220.161 | 0.0% | 2 | 0.8 | 0.8 | 0.8 | 0.8 | 0.0 |
| 7 | 11.94.155.73 | 0.0% | 2 | 1.2 | 1.2 | 1.2 | 1.2 | 0.0 |
| 8 | 157.148.24.41 | 0.0% | 2 | 1.2 | 1.2 | 1.2 | 1.2 | 0.0 |
| 9 | 120.80.137.89 | 0.0% | 2 | 3.1 | 2.7 | 2.4 | 3.1 | 0.6 |
| 10 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 11 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 12 | 219.158.30.26 | 0.0% | 2 | 30.1 | 29.5 | 28.9 | 30.1 | 0.8 |
| 13 | 219.158.8.182 | 0.0% | 2 | 33.5 | 32.1 | 30.8 | 33.5 | 1.9 |
| 14 | 219.158.116.238 | 0.0% | 2 | 181.8 | 181.8 | 181.7 | 181.8 | 0.0 |
| 15 | 4.53.209.77 | 0.0% | 2 | 161.9 | 160.9 | 160.0 | 161.9 | 1.3 |
| 16 | 4.69.227.145 | 0.0% | 2 | 196.0 | 195.9 | 195.9 | 196.0 | 0.1 |
| 17 | 4.43.131.86 | 0.0% | 2 | 201.0 | 202.1 | 201.0 | 203.3 | 1.6 |
| 18 | 193.58.147.1 | 0.0% | 2 | 207.3 | 203.9 | 200.6 | 207.3 | 4.7 |
HOST: guangzhou-alibaba
#### Asia, Hangzhou
DC208, AS37963
| Hop | HOST | Loss% | Snt | Last | Avg | Best | Wrst | StDev |
|:----|:-----------------|------:|----:|------:|------:|------:|------:|------:|
| 1 | 10.12.208.214 | 0.0% | 2 | 1.8 | 1.8 | 1.8 | 1.8 | 0.0 |
| 2 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 3 | 10.255.101.109 | 0.0% | 2 | 1.6 | 2.6 | 1.6 | 3.7 | 1.4 |
| 4 | 11.94.128.130 | 0.0% | 2 | 3.1 | 8.5 | 3.1 | 13.9 | 7.7 |
| 5 | 10.102.42.37 | 0.0% | 2 | 3.5 | 3.6 | 3.5 | 3.6 | 0.0 |
| 6 | 115.236.101.74 | 0.0% | 2 | 3.8 | 3.8 | 3.8 | 3.8 | 0.0 |
| 7 | 220.191.200.57 | 0.0% | 2 | 4.1 | 4.1 | 4.1 | 4.1 | 0.0 |
| 8 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 9 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 10 | 202.97.39.185 | 50.0% | 2 | 9.8 | 9.8 | 9.8 | 9.8 | 0.0 |
| 11 | 202.97.51.190 | 0.0% | 2 | 153.4 | 153.5 | 153.4 | 153.6 | 0.1 |
| 12 | 4.15.125.53 | 50.0% | 2 | 269.0 | 269.0 | 269.0 | 269.0 | 0.0 |
| 13 | 4.69.227.145 | 0.0% | 2 | 224.6 | 224.5 | 224.5 | 224.6 | 0.0 |
| 14 | 4.43.131.86 | 0.0% | 2 | 266.4 | 267.0 | 266.4 | 267.6 | 0.8 |
| 15 | 193.58.147.1 | 50.0% | 2 | 246.2 | 246.2 | 246.2 | 246.2 | 0.0 |
HOST: hangzhou-alibaba
#### Asia, Heyuan
DC521, AS37963
| Hop | HOST | Loss% | Snt | Last | Avg | Best | Wrst | StDev |
|:----|:-----------------|------:|----:|------:|------:|------:|------:|------:|
| 1 | 10.4.144.118 | 0.0% | 2 | 0.8 | 0.9 | 0.8 | 0.9 | 0.0 |
| 2 | 10.4.144.1 | 0.0% | 2 | 1.4 | 1.3 | 1.2 | 1.4 | 0.1 |
| 3 | 10.54.231.153 | 0.0% | 2 | 0.9 | 0.8 | 0.7 | 0.9 | 0.1 |
| 4 | 10.54.230.158 | 0.0% | 2 | 1.2 | 1.2 | 1.2 | 1.2 | 0.0 |
| 5 | 157.119.193.54 | 0.0% | 2 | 6.8 | 6.8 | 6.7 | 6.8 | 0.0 |
| 6 | 11.94.143.130 | 0.0% | 2 | 9.1 | 8.8 | 8.6 | 9.1 | 0.3 |
| 7 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 8 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 9 | 119.147.220.129 | 0.0% | 2 | 11.6 | 11.6 | 11.6 | 11.6 | 0.0 |
| 10 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 11 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 12 | 202.97.27.238 | 0.0% | 2 | 161.9 | 191.5 | 161.9 | 221.2 | 41.9 |
| 13 | 4.15.125.53 | 0.0% | 2 | 165.1 | 164.7 | 164.3 | 165.1 | 0.6 |
| 14 | 4.69.227.145 | 0.0% | 2 | 201.6 | 200.0 | 198.4 | 201.6 | 2.2 |
| 15 | 4.43.131.86 | 0.0% | 2 | 208.3 | 217.6 | 208.3 | 226.9 | 13.2 |
| 16 | 193.58.147.1 | 0.0% | 2 | 211.1 | 209.3 | 207.5 | 211.1 | 2.6 |
HOST: heyuan-alibaba
#### Asia, Shenzhen
DC520, AS37963
| Hop | HOST | Loss% | Snt | Last | Avg | Best | Wrst | StDev |
|:----|:-----------------|------:|----:|------:|------:|------:|------:|------:|
| 1 | 10.12.24.18 | 0.0% | 2 | 2.1 | 2.1 | 2.1 | 2.2 | 0.1 |
| 2 | 10.12.24.73 | 50.0% | 2 | 2.6 | 2.6 | 2.6 | 2.6 | 0.0 |
| 3 | 11.57.13.57 | 0.0% | 2 | 1.9 | 2.0 | 1.9 | 2.2 | 0.2 |
| 4 | 103.41.141.206 | 0.0% | 2 | 3.3 | 3.3 | 3.3 | 3.4 | 0.1 |
| 5 | 11.94.143.122 | 0.0% | 2 | 3.3 | 3.3 | 3.3 | 3.3 | 0.0 |
| 6 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 7 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 8 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 9 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 10 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 11 | 202.97.22.122 | 0.0% | 2 | 422.5 | 292.1 | 161.8 | 422.5 | 184.3 |
| 12 | 4.15.125.53 | 0.0% | 2 | 161.6 | 165.4 | 161.6 | 169.2 | 5.4 |
| 13 | 4.69.227.145 | 0.0% | 2 | 205.3 | 205.1 | 204.9 | 205.3 | 0.3 |
| 14 | 4.43.131.86 | 0.0% | 2 | 204.9 | 205.5 | 204.9 | 206.1 | 0.9 |
| 15 | 193.58.147.1 | 0.0% | 2 | 208.4 | 242.1 | 208.4 | 275.7 | 47.6 |
HOST: shenzhen-alibaba
#### Asia, Shanghai
DC276, AS37963
| Hop | HOST | Loss% | Snt | Last | Avg | Best | Wrst | StDev |
|:----|:-----------------|------:|----:|------:|------:|------:|------:|------:|
| 1 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 2 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 3 | 10.222.227.113 | 0.0% | 2 | 2.2 | 3.1 | 2.2 | 4.1 | 1.4 |
| 4 | 11.94.199.229 | 0.0% | 2 | 4.5 | 215.4 | 4.5 | 426.4 | 298.4 |
| 5 | 10.54.37.230 | 0.0% | 2 | 3.3 | 7.5 | 3.3 | 11.8 | 6.0 |
| 6 | 101.95.211.125 | 0.0% | 2 | 4.5 | 7.3 | 4.5 | 10.2 | 4.1 |
| 7 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 8 | 101.95.218.41 | 0.0% | 2 | 7.1 | 7.2 | 7.1 | 7.4 | 0.2 |
| 9 | 202.97.71.30 | 50.0% | 2 | 10.4 | 10.4 | 10.4 | 10.4 | 0.0 |
| 10 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 11 | 202.97.52.250 | 50.0% | 2 | 146.9 | 146.9 | 146.9 | 146.9 | 0.0 |
| 12 | 4.15.125.53 | 0.0% | 2 | 213.6 | 213.8 | 213.6 | 214.1 | 0.3 |
| 13 | 4.69.227.145 | 0.0% | 2 | 226.4 | 226.4 | 226.4 | 226.4 | 0.0 |
| 14 | 4.43.131.86 | 0.0% | 2 | 219.0 | 218.9 | 218.7 | 219.0 | 0.2 |
| 15 | 193.58.147.1 | 0.0% | 2 | 259.4 | 259.0 | 258.5 | 259.4 | 0.6 |
HOST: shanghai-alibaba
#### Asia, Jining
DC517, AS37963
| Hop | HOST | Loss% | Snt | Last | Avg | Best | Wrst | StDev |
|:----|:-----------------|------:|----:|------:|------:|------:|------:|------:|
| 1 | 10.123.208.6 | 0.0% | 2 | 1.3 | 1.4 | 1.3 | 1.5 | 0.2 |
| 2 | 10.123.208.73 | 0.0% | 2 | 2.8 | 6.2 | 2.8 | 9.6 | 4.8 |
| 3 | 10.54.223.253 | 0.0% | 2 | 1.4 | 1.5 | 1.4 | 1.7 | 0.2 |
| 4 | 117.49.33.214 | 0.0% | 2 | 1.4 | 1.3 | 1.2 | 1.4 | 0.1 |
| 5 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 6 | 116.251.112.201 | 0.0% | 2 | 8.5 | 8.5 | 8.5 | 8.5 | 0.0 |
| 7 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 8 | 36.110.245.209 | 0.0% | 2 | 10.0 | 10.0 | 10.0 | 10.0 | 0.0 |
| 9 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 10 | 202.97.54.38 | 50.0% | 2 | 12.1 | 12.1 | 12.1 | 12.1 | 0.0 |
| 11 | 202.97.59.106 | 0.0% | 2 | 300.5 | 225.5 | 150.6 | 300.5 | 105.9 |
| 12 | 4.15.125.53 | 0.0% | 2 | 150.6 | 150.1 | 149.7 | 150.6 | 0.6 |
| 13 | 4.69.227.145 | 0.0% | 2 | 192.5 | 193.5 | 192.5 | 194.5 | 1.4 |
| 14 | 4.43.131.86 | 0.0% | 2 | 191.1 | 191.1 | 191.1 | 191.1 | 0.0 |
| 15 | 193.58.147.1 | 0.0% | 2 | 193.3 | 193.9 | 193.3 | 194.6 | 1.0 |
HOST: ulanqab-alibaba (Jining - Ulanqab is a common naming for datacenters in this region of Inner Mongolia, Jining being a city within Ulanqab league/prefecture)
#### Asia, Hohhot
DC329, AS37963
| Hop | HOST | Loss% | Snt | Last | Avg | Best | Wrst | StDev |
|:----|:-----------------|------:|----:|------:|------:|------:|------:|------:|
| 1 | 11.55.35.62 | 0.0% | 2 | 0.8 | 0.7 | 0.6 | 0.8 | 0.1 |
| 2 | 11.73.1.193 | 0.0% | 2 | 3.6 | 4.3 | 3.6 | 5.0 | 1.0 |
| 3 | 11.141.77.58 | 0.0% | 2 | 0.5 | 0.5 | 0.5 | 0.5 | 0.0 |
| 4 | 116.251.105.146 | 0.0% | 2 | 0.6 | 0.6 | 0.5 | 0.6 | 0.0 |
| 5 | 103.52.73.22 | 0.0% | 2 | 15.7 | 15.7 | 15.7 | 15.7 | 0.0 |
| 6 | 116.251.112.197 | 0.0% | 2 | 12.8 | 12.7 | 12.6 | 12.8 | 0.2 |
| 7 | 106.38.196.85 | 0.0% | 2 | 13.3 | 13.2 | 13.1 | 13.3 | 0.2 |
| 8 | 36.110.244.1 | 0.0% | 2 | 14.4 | 16.5 | 14.4 | 18.7 | 3.1 |
| 9 | 202.97.94.186 | 0.0% | 2 | 22.5 | 20.3 | 18.1 | 22.5 | 3.1 |
| 10 | 202.97.12.134 | 0.0% | 2 | 15.8 | 16.0 | 15.8 | 16.1 | 0.2 |
| 11 | 202.97.59.106 | 0.0% | 2 | 155.2 | 156.1 | 155.2 | 157.1 | 1.3 |
| 12 | 4.15.125.53 | 0.0% | 2 | 155.8 | 157.9 | 155.8 | 160.1 | 3.1 |
| 13 | 4.69.227.145 | 0.0% | 2 | 192.4 | 192.4 | 192.4 | 192.5 | 0.1 |
| 14 | 4.43.131.86 | 0.0% | 2 | 197.0 | 197.3 | 197.0 | 197.6 | 0.4 |
| 15 | 193.58.147.1 | 0.0% | 2 | 196.0 | 196.2 | 196.0 | 196.5 | 0.3 |
HOST: huhehaote-alibaba
#### Asia, Beijing
DC207, AS37963
| Hop | HOST | Loss% | Snt | Last | Avg | Best | Wrst | StDev |
|:----|:-----------------|------:|----:|------:|------:|------:|------:|------:|
| 1 | 10.36.68.38 | 50.0% | 2 | 2.2 | 2.2 | 2.2 | 2.2 | 0.0 |
| 2 | 11.73.8.170 | 0.0% | 2 | 2.3 | 2.3 | 2.3 | 2.4 | 0.1 |
| 3 | 10.102.252.66 | 0.0% | 2 | 2.3 | 2.3 | 2.2 | 2.3 | 0.0 |
| 4 | 10.102.251.190 | 50.0% | 2 | 4.3 | 4.3 | 4.3 | 4.3 | 0.0 |
| 5 | 45.112.216.138 | 0.0% | 2 | 4.6 | 4.7 | 4.6 | 4.7 | 0.1 |
| 6 | 36.110.217.9 | 50.0% | 2 | 4.9 | 4.9 | 4.9 | 4.9 | 0.0 |
| 7 | 36.110.245.189 | 0.0% | 2 | 5.8 | 5.9 | 5.8 | 6.0 | 0.2 |
| 8 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 9 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 10 | 202.97.51.193 | 0.0% | 2 | 145.4 | 145.4 | 145.3 | 145.4 | 0.1 |
| 11 | 4.15.125.53 | 0.0% | 2 | 144.2 | 151.9 | 144.2 | 159.6 | 10.9 |
| 12 | 4.69.227.145 | 0.0% | 2 | 182.6 | 182.7 | 182.6 | 182.8 | 0.1 |
| 13 | 4.43.131.86 | 0.0% | 2 | 187.2 | 187.3 | 187.2 | 187.3 | 0.1 |
| 14 | 193.58.147.1 | 0.0% | 2 | 189.4 | 204.8 | 189.4 | 220.2 | 21.8 |
HOST: beijing-alibaba.perfops.org
#### Asia, Nanjing
DC518, AS37963
| Hop | HOST | Loss% | Snt | Last | Avg | Best | Wrst | StDev |
|:----|:-----------------|------:|----:|------:|------:|------:|------:|------:|
| 1 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 2 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 3 | 11.73.1.65 | 50.0% | 2 | 0.7 | 0.7 | 0.7 | 0.7 | 0.0 |
| 4 | 11.94.208.225 | 0.0% | 2 | 0.7 | 0.5 | 0.4 | 0.7 | 0.2 |
| 5 | 10.54.132.102 | 0.0% | 2 | 9.7 | 9.6 | 9.6 | 9.7 | 0.1 |
| 6 | 116.251.113.217 | 0.0% | 2 | 8.3 | 18.6 | 8.3 | 28.9 | 14.6 |
| 7 | 180.163.38.81 | 0.0% | 2 | 9.6 | 9.7 | 9.6 | 9.8 | 0.1 |
| 8 | 101.95.209.69 | 50.0% | 2 | 20.6 | 20.6 | 20.6 | 20.6 | 0.0 |
| 9 | 101.95.218.73 | 0.0% | 2 | 10.5 | 10.6 | 10.5 | 10.7 | 0.1 |
| 10 | 202.97.94.237 | 0.0% | 2 | 24.9 | 25.5 | 24.9 | 26.1 | 0.8 |
| 11 | 202.97.12.186 | 0.0% | 2 | 13.6 | 13.7 | 13.6 | 13.8 | 0.1 |
| 12 | 202.97.51.190 | 0.0% | 2 | 184.7 | 184.7 | 184.7 | 184.7 | 0.0 |
| 13 | 4.15.125.53 | 50.0% | 2 | 183.1 | 183.1 | 183.1 | 183.1 | 0.0 |
| 14 | 4.69.227.145 | 0.0% | 2 | 222.6 | 222.5 | 222.4 | 222.6 | 0.1 |
| 15 | 4.43.131.86 | 50.0% | 2 | 230.6 | 230.6 | 230.6 | 230.6 | 0.0 |
| 16 | 193.58.147.1 | 0.0% | 2 | 230.2 | 230.4 | 230.2 | 230.7 | 0.3 |
HOST: nanjing-alibaba
#### Asia, Zhangjiakou
DC516, AS37963
| Hop | HOST | Loss% | Snt | Last | Avg | Best | Wrst | StDev |
|:----|:-----------------|------:|----:|------:|------:|------:|------:|------:|
| 1 | 10.130.116.42 | 0.0% | 2 | 1.1 | 1.1 | 1.1 | 1.2 | 0.1 |
| 2 | 11.73.30.66 | 50.0% | 2 | 0.9 | 0.9 | 0.9 | 0.9 | 0.0 |
| 3 | 10.216.175.206 | 0.0% | 2 | 1.5 | 1.6 | 1.5 | 1.8 | 0.2 |
| 4 | 10.255.161.134 | 0.0% | 2 | 1.2 | 1.3 | 1.2 | 1.4 | 0.1 |
| 5 | 10.54.111.174 | 0.0% | 2 | 5.7 | 5.9 | 5.7 | 6.0 | 0.2 |
| 6 | 10.102.155.34 | 0.0% | 2 | 5.7 | 5.7 | 5.7 | 5.7 | 0.0 |
| 7 | 106.38.196.177 | 0.0% | 2 | 7.5 | 7.5 | 7.5 | 7.6 | 0.1 |
| 8 | 36.110.245.201 | 0.0% | 2 | 7.6 | 7.6 | 7.6 | 7.7 | 0.1 |
| 9 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 10 | ??? | 100.0 | 2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| 11 | 202.97.51.193 | 0.0% | 2 | 146.7 | 158.9 | 146.7 | 171.1 | 17.2 |
| 12 | 4.15.125.53 | 0.0% | 2 | 153.3 | 149.8 | 146.2 | 153.3 | 5.0 |
| 13 | 4.69.227.145 | 0.0% | 2 | 187.1 | 187.3 | 187.1 | 187.6 | 0.4 |
| 14 | 4.43.131.86 | 0.0% | 2 | 190.5 | 190.0 | 189.5 | 190.5 | 0.7 |
| 15 | 193.58.147.1 | 0.0% | 2 | 194.4 | 192.0 | 189.5 | 194.4 | 3.4 |
HOST: zhangjiakou-alibaba
Japan(13)
#### Asia, Tokyo
DC409, AS36236
HOST: tokyo-netactuate.perfops.org
#### Asia, Osaka
DC368, AS396982
HOST: osaka-google
#### Asia, Tokyo
DC441, AS16509
HOST: tokyo-2-aws
#### Asia, Tokyo
DC315, AS25108
HOST: tokyo-dediserve.perfops.org
#### Asia, Osaka
DC498, AS20473
HOST: osaka-vultr
#### Asia, Tokyo
DC545, AS63949
HOST: jptyo02-mon02
#### Asia, Tokyo
DC565, AS36351
HOST: jptyo01-mon02
#### Asia, Tokyo
DC564, AS36351
HOST: jptyo01-mon01
#### Asia, Tokyo
DC6, AS20473
HOST: tokyo-vultr.perfops.org
#### Asia, Tokyo
DC367, AS396982
HOST: tokyo-google
#### Asia, Tokyo
DC544, AS63949
HOST: jptyo02-mon01
#### Asia, Tokyo
DC118, AS63949
HOST: tokyo-linode.perfops.org
#### Asia, Osaka
DC142, AS134835
HOST: osaka-starrydns
Singapore(10)
#### Singapore
DC440, AS16509
HOST: singapore-2-aws.perfops.org
#### Singapore
DC331, AS202053
HOST: singapore-upcloud.perfops.org
#### Singapore
DC411, AS36236
HOST: singapore-netactuate
#### Singapore
DC60, AS38001
HOST: singapore-dediserve.perfops.org
#### Singapore
DC370, AS396982
HOST: singapore-google
#### Singapore
DC29, AS7489
HOST: singapore-hostus
#### Singapore
DC546, AS63949
HOST: sgsin02-mon01
#### Singapore
DC332, AS14061
HOST: singapore-digitalocean
#### Singapore
DC547, AS63949
HOST: sgsin02-mon02
#### Singapore
DC163, AS20473
HOST: singapore-vultr.perfops.org
to guangzhou - china mobile
I'm uncertain if my ISP limited single-parallel speed to 8Mbps, as iperf reaches 50Mbps when using 8 parallels.
ignore the iperf, speedtest with single-thread is excellent
Europe(48)
Europe, Bratislava
DC104, AS201924
HOST: bratislava-enahost.perfops.org
Europe, Frankfurt am Main
DC137, AS9009
HOST: frankfurt-edis.perfops.org
Europe, Amsterdam
DC344, AS13213
HOST: amsterdam-vpsnet.perfops.org
Europe, Limassol
DC229, AS197648
HOST: limassol-onapp.perfops.org
Europe, Turin
DC528, AS396982
(empty response)
Europe, Vienna
DC538, AS57169
HOST: atvie01-mon02
Europe, Varna
DC171, AS56630
HOST: varna-edis.perfops.org
Europe, Luxembourg
DC295, AS202422
HOST: luxembourg-gcore.perfops.org
Europe, Paris
DC418, AS36236
HOST: paris-netactuate
Europe, Vienna
DC338, AS61098
HOST: vienna-exoscale
Europe, London
DC543, AS63949
HOST: gblon01-mon02
Europe, Amsterdam
DC25, AS43350
HOST: amsterdam-edis.perfops.org
Europe, Copenhagen
DC570, AS136258
HOST: dkcph01-mon01
Europe, Paris
DC5, AS20473
HOST: paris-vultr.perfops.org
Europe, Vienna
DC537, AS57169
HOST: atvie01-mon01
Europe, Zurich
DC300, AS61098
HOST: zurich-exoscale
Europe, Geneve
DC174, AS61098
HOST: geneva-exoscale
Europe, London
DC423, AS36236
HOST: london-netactuate.perfops.org
Europe, Belgrade
DC475, AS136258
HOST: belgrade-oneprovider.perfops.org
Europe, Budapest
DC180, AS62214
HOST: vm3302
Europe, Florence
DC474, AS49367
HOST: florence-oneprovider.perfops.org
Europe, Helsinki
DC477, AS51765
HOST: helsinki-oneprovider.perfops.org
Europe, London
DC19, AS59764
HOST: london-atlantic.perfops.org
Europe, Frankfurt am Main
DC374, AS396982
HOST: frankfurt-google
Europe, Brussels
DC476, AS9009
HOST: brussels-oneprovider.perfops.org
Europe, Riga
DC89, AS52173
HOST: riga-yourserver
Europe, Amsterdam
DC153, AS50673
HOST: amsterdam-dediserve
Europe, Dronten
DC252, AS208258
HOST: dronten-crowncloud
Europe, London
DC34, AS62240
HOST: london-hostus
Europe, Chisinau
DC200, AS39798
HOST: chisinau-mivocloud.perfops.org
Europe, London
DC4, AS20473
HOST: london-vultr.perfops.org
Europe, Amsterdam
DC532, AS14061
HOST: nlams02-testmon01
Europe, Frankfurt am Main
DC155, AS44066
HOST: frankfurt-dediserve.perfops.org
Europe, Marseille
DC525, AS138915
HOST: marseille-lightnode.perfops.org
Europe, Vilnius
DC76, AS212531
HOST: vilnius-time4vps.perfops.org
Europe, Sandefjord
DC169, AS56655
HOST: sandefjord-terrahost.perfops.org
Europe, Madrid
DC421, AS36236
HOST: madrid-netactuate
Europe, Amsterdam
DC533, AS14061
HOST: nlams02-testmon02
Europe, London
DC542, AS63949
HOST: gblon01-mon01
Europe, Zurich
DC376, AS396982
HOST: zurich-google
Europe, Frankfurt am Main
DC426, AS36236
HOST: frankfurt-netactuate
Europe, Madrid
DC45, AS136258
HOST: madrid-oneprovider.perfops.org
Europe, Manchester
DC500, AS20473
HOST: manchester-vultr
Europe, Vienna
DC26, AS57169
HOST: vienna-edis
Europe, Johvi
DC100, AS198068
HOST: johvi-fastvps.perfops.org
Europe, Stockholm
DC568, AS136258
HOST: sesto01-mon01
Europe, Vienna
DC154, AS203833
HOST: vienna-dediserve
Europe, Frankfurt am Main
DC461, AS61098
HOST: frankfurt-exoscale
Europe, Stockholm
DC569, AS136258
HOST: sesto01-mon02
I see you guys have been working. Nice.
DC Lat / Lng? So i can add this to NMS map :-)
From NE Scotland:
3 ae50-ner001.msp.as13285.net (78.144.1.33) 13.928 ms 14.179 ms 14.436 ms
4 ae50-scr001-msp.as13285.net (78.144.1.32) 14.737 ms 15.337 ms 15.668 ms
5 ae60-scr101.thw.as13285.net (78.144.1.110) 21.508 ms 22.113 ms 29.658 ms
6 ae54.edge7.london1.level3.net (217.163.47.149) 30.129 ms 23.205 ms 28.596 ms
7 ae5.5.ear2.tulsa2.net.lumen.tech (4.69.227.145) 118.941 ms 119.222 ms 119.411 ms
8 virtual-mac.ear2.tulsa2.level3.net (4.43.131.86) 122.410 ms 122.703 ms 122.947 ms
9 23.136.108.51 (23.136.108.51) 123.682 ms 123.938 ms 131.552 ms
10 193.58.147.xxx (193.58.147.xxx) 123.228 ms 120.955 ms 121.567 ms
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural.
It wisnae me! A big boy done it and ran away. || NVMe2G for life! until death (the end is nigh).
Some high quality Lumen (albeit loves to backhaul through DFW) from all tests I've done.
Do we need to play some sort of Saw type game to get that $25 dedi @VirMach ? This would be the perfect 'not just another DC in the tri-state area' for backups and I need one more bare metal server if it's possible. Let me know who / what I need to sacrifice to get in on that deal.
Ring the 308 buzzer every day until you get $25 dedi with 1200GB NVMe.
vps9hostname is available. affbrrI want my Virmach servers in Dallas please.