Dedicated server near AWS us-east-2 (Columbus) — need ≤2ms TCP to a probe IP

Comments

• Obelous Member

  6:15PM

  ICMP is not open. https://globalping.io/?measurement=2iXnLLZQWtgBvJzoH001210D8
• oloke Member, Host Rep

  6:27PM

  Based on quick Globalping test (different IP in that range since the one you provided doesn't respond to ICMP pings).

  @Swiftnode - 5ms, in Lima/Ottoville, US
  @lnx - 11ms despite being in the same city you mention - from mtr test seems it's routed via Cleveland, US before reaching AWS in Columbus, US. Maybe they could work with Cogent to improve this route.

  Thanked by 1Swiftnode
• Swiftnode Member, Patron Provider, LIR

  7:29PM edited 7:31PM

  @oloke said:
  @Swiftnode - 5ms, in Lima/Ottoville, US

  Thanks for the mention!

  @Zzzzzigza said:
  Looking for a dedicated server as close as possible to AWS us-east-2 / us-east-2b.

  Must-have:

  TCP RTT ≤2ms to this probe: 3.133.102.213 (ICMP + TCP 443 open). Please post ping / MTR / TCP 443 from your rack.
  64GB+ RAM (128 nicer)
  1TB+ NVMe
  Ryzen 5950/7950/9950 or similar modern CPU
  Budget $150–400/mo
  IPMI a plus

  Please include DC address or hall name, looking glass, and current stock/SKU. Thanks.

  As close as possible is going to be an AWS instance in the same location. But we have servers in Ottoville, OH. (Microtronix DC at 349 Wayne St)

  The IP you posted doesn't respond to ICMP or TCP on 443, but another IP nearby responds to both and is in the same location. (3.133.102.21)

  hping3 -S -p 443 -c 20 3.133.102.21
  HPING 3.133.102.21 (eth0 3.133.102.21): S set, 40 headers + 0 data bytes
  len=46 ip=3.133.102.21 ttl=122 DF id=30069 sport=443 flags=SA seq=0 win=8192 rtt=7.5 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30070 sport=443 flags=SA seq=1 win=8192 rtt=6.4 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30071 sport=443 flags=SA seq=2 win=8192 rtt=7.4 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30072 sport=443 flags=SA seq=3 win=8192 rtt=7.3 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30073 sport=443 flags=SA seq=4 win=8192 rtt=6.5 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30074 sport=443 flags=SA seq=5 win=8192 rtt=7.3 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30075 sport=443 flags=SA seq=6 win=8192 rtt=7.2 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30076 sport=443 flags=SA seq=7 win=8192 rtt=7.2 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30077 sport=443 flags=SA seq=8 win=8192 rtt=7.1 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30078 sport=443 flags=SA seq=9 win=8192 rtt=7.1 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30079 sport=443 flags=SA seq=10 win=8192 rtt=7.0 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30080 sport=443 flags=SA seq=11 win=8192 rtt=6.8 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30081 sport=443 flags=SA seq=12 win=8192 rtt=6.8 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30082 sport=443 flags=SA seq=13 win=8192 rtt=7.7 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30083 sport=443 flags=SA seq=14 win=8192 rtt=6.6 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30084 sport=443 flags=SA seq=15 win=8192 rtt=6.5 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30085 sport=443 flags=SA seq=16 win=8192 rtt=7.5 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30086 sport=443 flags=SA seq=17 win=8192 rtt=6.4 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30087 sport=443 flags=SA seq=18 win=8192 rtt=7.4 ms
  len=46 ip=3.133.102.21 ttl=122 DF id=30088 sport=443 flags=SA seq=19 win=8192 rtt=6.4 ms
  
  --- 3.133.102.21 hping statistic ---
  20 packets transmitted, 20 packets received, 0% packet loss
  round-trip min/avg/max = 6.4/7.0/7.7 ms
  

  ---

  OTV-API (198.133.237.252) -> 3.133.102.21 (3.133.102.21)                                              2026-08-23T19:08:21+0000
  Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                                        Packets               Pings
   Host                                                                               Loss%   Snt   Last   Avg  Best  Wrst StDev
   1. ae-01.edge1.otv1.swiftnode.com                                                  65.8%   112    0.1   0.1   0.1   0.4   0.1
   2. 167.253.35.97                                                                   25.2%   112    0.3   0.2   0.1   0.5   0.1
   3. lima-microtronix-tech.com                                                        0.0%   112    2.3   2.5   2.3   3.7   0.2
   4. worth-core.bright.net                                                            0.0%   112    6.3   6.1   5.8   7.0   0.2
   5. (waiting for reply)
   6. 108.166.244.163                                                                  0.0%   112    7.4   7.6   7.3  14.9   0.7
   7. (waiting for reply)
   8. (waiting for reply)
   9. (waiting for reply)
  10. ec2-3-133-102-21.us-east-2.compute.amazonaws.com                                 0.0%   111    7.4   6.9   6.7   7.4   0.2
  

  We however don't have Ryzens in that location at the moment, we do have some somewhat comparable i9 servers though. And for most new customers we require KYC verification.

  Thanked by 1oloke
• Zzzzzigza Member

  8:01PM

  Thanks — you were right, ICMP (and 443) were closed on that box.

  New probe, same AZ (us-east-2b): 3.135.65.212
  ICMP and TCP 443 should be open now. Please retest ping / MTR / hping3 -S -p 443 from your rack.> @Zzzzzigza said:

  Looking for a dedicated server as close as possible to AWS us-east-2 / us-east-2b.

  Must-have:

  TCP RTT ≤2ms to this probe: 3.133.102.213 (ICMP + TCP 443 open). Please post ping / MTR / TCP 443 from your rack.
  64GB+ RAM (128 nicer)
  1TB+ NVMe
  Ryzen 5950/7950/9950 or similar modern CPU
  Budget $150–400/mo
  IPMI a plus
  Not looking for Ashburn (~19ms from this AZ) unless you can beat 2ms to that IP. Ottoville/OH1 custom is fine to quote if you actually measure the probe.

  Please include DC address or hall name, looking glass, and current stock/SKU. Thanks.

  Thanks — you were right, ICMP (and 443) were closed on that box.

  New probe, same AZ (us-east-2b): 3.135.65.212
  ICMP and TCP 443 should be open now. Please retest ping / MTR / hping3 -S -p 443 from your rack.

  @Swiftnode @oloke the ~5–7ms from Ottoville matches what we saw on the OH1 LG. Still looking for anything that can actually print ≤2ms to this IP. If that’s only same-AZ AWS, say so.

  Updated first post as well.
• Obelous Member

  8:03PM edited 8:03PM

  @Zzzzzigza said: New probe, same AZ (us-east-2b): 3.135.65.212
  ICMP and TCP 443 should be open now. Please retest ping / MTR / hping3 -S -p 443 from your rack.

  No. https://globalping.io/?measurement=29mlbzZeKIGzF9XNv001210Es
• Zzzzzigza Member

  8:18PM

  @Obelous said:

  @Zzzzzigza said: New probe, same AZ (us-east-2b): 3.135.65.212
  ICMP and TCP 443 should be open now. Please retest ping / MTR / hping3 -S -p 443 from your rack.

  No. https://globalping.io/?measurement=29mlbzZeKIGzF9XNv001210Es

  done, ICMP is open now on 3.135.65.212 — please retest. OH1 LG is ~7.2ms. Thanks.
• concept Member

  8:24PM

  Are you the same user?
  https://lowendtalk.com/discussion/218270/looking-for-10-dedicated-servers-near-aws-us-east-2-ohio-with-low-latency-and-good-pricing#latest

  Microtronix is the best you can get.
• Zzzzzigza Member

  8:34PM

  @concept said:
  Are you the same user?
  https://lowendtalk.com/discussion/218270/looking-for-10-dedicated-servers-near-aws-us-east-2-ohio-with-low-latency-and-good-pricing#latest

  Microtronix is the best you can get.

  Different thread. You’re welcome to send an offer. Please include DC/hall, SKU, price, and ping / MTR / TCP 443 to 3.135.65.212. We already see ~7ms from Ottoville/OH1; anything that can print closer than that is interesting.