Miami-based "useast" AoS servers (for Latam and eastern US players)

Do you like this suggestion?
  • :+1: Yes
  • :thinking: Maybe
  • :-1: No

0 voters

:spiral_notepad: Summary

consider this a trial of a secondary location for our AoS servers, based in Miami, FL, USA, serving primarily our Latam-based players, and of course our players in the eastern parts of the USA!, USA!, USA!

also suggested by @Mile a yearish ago:

https://aloha.pk/t/latam-server-hosting/15788


:notebook_with_decorative_cover: Details

Click to expand

Miami, Florida, United States because it is Latam’s main hub to America, many hop options vs. our current very few. considering the number of lag complaints we’ve received from Latam players, and the fact that a portion of our playerbase is from the eastern parts of the United States, i think Miami is a strategic location that will be a satisfying experience for both those sets of players. and maybe other regions, Europe and Africa, would benefit as well. :man_shrugging:

this could be a paid, additional dedicated VPS service (adding ~$30/mo to our current expenses) to provide a secondary location of our most popular AoS game servers. the service could be provided by Vultr, the same provider of our website server, and it would be “optimized” for game servers. i estimate we could reasonably run 2-4 PySnip servers 24/7 on it.

in their words:

Our Miami Cloud Servers have great connectivity to Brasil, and all of Central and South America.

test IP

how does this IP do for you?

104.156.244.232

if you’ve got a moment, please run a ping on it in your terminal:

ping 104.156.244.232

…and report back your result here if you’d like to help research this location.

a traceroute would be good to know as well:

traceroute 104.156.244.232

…or even better, MTR! :smiley:
WinMTR download | SourceForge.net

or we use a different provider. suggestions welcome!

the next big question is: what should the 4 servers to be?

my suggestion:

  1. arena top 10
  2. arena cs
  3. 1v1
  4. babel

that list is just my opinion and may or may not be relative to Latam preference. we should consider everyone’s preference, with extra consideration for players from Latam. (to be voted on)


:file_folder: Media





:information_source: Sources


this location is way better. why r the servers in la to begin with. us west is like the worst for latam and eu, two hotspots where most aos players live in.
Heck, if this goes well would u consider entirely moving operations to florida if possible?

How would this affect the player base? Assuming both servers would be different aos servers (i.e. two Babels).

If you were able to get a good deal as you currently get in LA in east coast maybe it would make sense to just have one server over here (if it doesn’t screw over west coast people)

How is route from New York to LATAM and Europe?

Florida could be good but chances for natural disasters are higher in Southern Florida (esp during hurricane season)

As for servers

Babel
Arena
1x1
Hallway

(Or maybe have a server that can change game mode upon win so there’s always something new?)

1 Like
Tracing route to 104.156.244.232 over a maximum of 30 hops

  1     1 ms     1 ms    <1 ms  192.168.0.1 
  2     9 ms     9 ms    12 ms  072-031-137-085.res.spectrum.com [72.31.137.85] 
  3    11 ms     9 ms     8 ms  int-0-5-1-8.orld27-ser1.netops.charter.com [71.46.9.241] 
  4    14 ms    14 ms    11 ms  lag-27.orld31-car1.netops.charter.com [72.31.188.85] 
  5    13 ms    12 ms    13 ms  lag-12.orld71-car1.netops.charter.com [72.31.220.136] 
  6    15 ms    15 ms    15 ms  lag-415-10.orldfljo00w-bcr00.netops.charter.com [66.109.9.138] 
  7    14 ms    13 ms    13 ms  ae-10.bar3.Orlando1.Level3.net [4.68.111.185] 
  8    21 ms    18 ms    17 ms  4.69.141.37 
  9    23 ms    22 ms    22 ms  CHOOPA-LLC.ear2.Miami2.Level3.net [4.15.154.166] 
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13   129 ms    57 ms    61 ms  104.156.244.232 

Trace complete.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |   84 |   84 |    1 |    9 |  101 |    2 |
|        072-031-137-085.res.spectrum.com -    0 |   84 |   84 |    7 |   19 |  112 |   13 |
|int-0-5-1-8.orld27-ser1.netops.charter.com -    0 |   84 |   84 |    8 |   20 |  112 |   14 |
|   lag-27.orld31-car1.netops.charter.com -    0 |   84 |   84 |   10 |   22 |  116 |   15 |
|   lag-12.orld71-car1.netops.charter.com -    0 |   84 |   84 |   11 |   43 |  309 |   14 |
|lag-415-10.orldfljo00w-bcr00.netops.charter.com -    0 |   84 |   84 |   13 |   27 |  123 |   25 |
|          ae-10.bar3.Orlando1.Level3.net -    0 |   84 |   84 |   11 |   25 |  114 |   30 |
|                             4.69.141.37 -    5 |   72 |   69 |    0 |   21 |  110 |   19 |
|       CHOOPA-LLC.ear2.Miami2.Level3.net -    0 |   84 |   84 |   21 |   33 |  119 |   26 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                         104.156.244.232 -    0 |   84 |   84 |   53 |   65 |  155 |   59 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
1 Like

Current aloha servers (52.119.1.67) for me: Mostly ranging between 180 and 200ms.
Example IP (104.156.244.232): Mostly ranging between 140 and 150ms.

1 Like
--- 104.156.244.232 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 122.934/123.088/123.402/0.126 ms
--- 52.119.1.67 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 144.845/145.027/145.213/0.117 ms
2 Likes

this seems like a well-rounded balance of options

This looks good to me too! If we’re able to find a server location that fits our needs, these four deserve to have duplicates imo :+1:

1 Like
Pinging 52.119.1.67 with 32 bytes of data:
Reply from 52.119.1.67: bytes=32 time=75ms TTL=55
Reply from 52.119.1.67: bytes=32 time=76ms TTL=55
Reply from 52.119.1.67: bytes=32 time=75ms TTL=55
Reply from 52.119.1.67: bytes=32 time=75ms TTL=55

Ping statistics for 52.119.1.67:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 75ms, Maximum = 76ms, Average = 75ms

Pinging 104.156.244.232 with 32 bytes of data:
Reply from 104.156.244.232: bytes=32 time=55ms TTL=54
Reply from 104.156.244.232: bytes=32 time=53ms TTL=54
Reply from 104.156.244.232: bytes=32 time=54ms TTL=54
Reply from 104.156.244.232: bytes=32 time=55ms TTL=54

Ping statistics for 104.156.244.232:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 53ms, Maximum = 55ms, Average = 54ms
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |  100 |  100 |    2 |    3 |   34 |    3 |
|                   No response from host -  100 |   21 |    0 |    0 |    0 |    0 |    0 |
|     rc3sc-te0-1-0-28-6.wp.shawcable.net -    0 |  100 |  100 |    4 |    5 |   39 |    6 |
|           rc4ec-be25-1.il.shawcable.net -    0 |  100 |  100 |   20 |   21 |   67 |   21 |
|                   No response from host -  100 |   21 |    0 |    0 |    0 |    0 |    0 |
|    ae-11.r08.chcgil09.us.bb.gin.ntt.net -    0 |  100 |  100 |   63 |   64 |  110 |   64 |
|     ae-4.r23.chcgil09.us.bb.gin.ntt.net -    0 |  100 |  100 |   20 |   24 |   68 |   23 |
|     ae-1.r24.snjsca04.us.bb.gin.ntt.net -    3 |   92 |   90 |   64 |   66 |  112 |   64 |
|                   No response from host -  100 |   21 |    0 |    0 |    0 |    0 |    0 |
|     ae-2.r00.lsanca07.us.bb.gin.ntt.net -    0 |  100 |  100 |   74 |   75 |  121 |   75 |
|ae-0.profuse-solutions.lsanca07.us.bb.gin.ntt.net -    0 |  100 |  100 |   76 |   77 |  123 |   78 |
|                   No response from host -  100 |   21 |    0 |    0 |    0 |    0 |    0 |
|       67.1.119.52.ptr.fantomservers.com -    0 |  100 |  100 |   74 |   75 |  122 |   75 |
|________________________________________________|______|______|______|______|______|______|

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |  100 |  100 |    2 |    3 |    4 |    3 |
|                   No response from host -  100 |   20 |    0 |    0 |    0 |    0 |    0 |
|     rc3sc-te0-1-0-28-6.wp.shawcable.net -    0 |  100 |  100 |    4 |    5 |    9 |    6 |
|           rc4ec-be25-1.il.shawcable.net -    0 |  100 |  100 |   19 |   21 |   28 |   22 |
|               ae18.cr9-chi1.ip4.gtt.net -    0 |  100 |  100 |   19 |   24 |   75 |   31 |
|                ae7.cr7-mia1.ip4.gtt.net -    0 |  100 |  100 |   48 |   55 |  212 |   49 |
|            as20473-gw.mia12.ip4.gtt.net -    0 |  100 |  100 |   54 |   57 |  100 |   55 |
|                   No response from host -  100 |   20 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   20 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   20 |    0 |    0 |    0 |    0 |    0 |
|                         104.156.244.232 -    0 |  100 |  100 |   53 |   54 |   61 |   53 |
|________________________________________________|______|______|______|______|______|______|

Was not expecting that much of an improvement. Guess my ISP up here in Canada just routes better to Miami then to LA. One day I’ll be in the server room with sub-1ms and I’ll show everyone just how sick my flicks are lol

Solid yes from me

On a serious note. I’d be curious to know how well Vultr is at maintaining up time.
Server Status

From my quick 5 minutes of googling it looks like they haven’t really had any major outages for awhile now.

1 Like

west coast is where we originated because it’s Hawaii’s nearest major hub (Hawaii hosting was too expensive back then and too far for US players), and there are players who were/still are satisfied by the west coast location for a long time.

Miami would be better for Latam and Europe players, but worse for most anyone west of central US, including Hawaii, Asia, and Australia - west coast is generally better for them.

multiple locations would provide a better gameplay experience to more players from different regions. the regions with the most active players will typically be rewarded by populating their nearest location to us…

i think region-specific stable servers from us will help the playerbase grow organically within those regions due to an improved gameplay experience for them. less ragequitting more playing.

nothing would prevent a player from Asia, for example, from joining the Miami server, but uswest would be better for him. just as nothing would prevent a Latam player from joining uswest.

good to see from you here again, thanks for sharing. we’ll have to organize a LAN party one of these days so you can show off your sick flicks! :laughing:

i’ve been using them since ~2017 and can’t really recall any problems. they’ve been serving the new aloha.pk website well since publicly launching ~6 months ago (and before that). any recorded downtimes of the aloha.pk website were from our own doings, not theirs, due to forum migration and development stuff.

Vultr also owns Choopa and gameservers.com.

1 Like
WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
internetbox.home 0 101 101 1 1 40 1
1.64.107.92.dynamic.wline.res.cust.swisscom.ch 0 101 101 3 4 41 3
No response from host 100 21 0 0 0 0 0
i69lss-000-ae28.bb.ip-plus.net 0 71 71 4 787 3716 27
i69lss-015-ae22.bb.ip-plus.net 0 101 101 2 4 28 3
i64bei-015-ae0.bb.ip-plus.net 0 101 101 4 7 42 4
i73olt-005-ae0.bb.ip-plus.net 0 101 101 4 7 58 6
i62bsg-005-ae6.bb.ip-plus.net 0 101 101 5 8 59 6
i62bsw-015-ae11.bb.ip-plus.net 0 101 101 5 9 59 10
i00nye-015-ae3.bb.ip-plus.net 0 101 101 81 84 220 82
No response from host 100 21 0 0 0 0 0
4.69.146.77 0 101 101 119 119 144 119
CHOOPA-LLC.ear2.Miami2.Level3.net 0 101 101 116 118 205 117
No response from host 100 21 0 0 0 0 0
No response from host 100 21 0 0 0 0 0
No response from host 100 21 0 0 0 0 0
104.156.244.232 0 101 101 116 117 204 117
1 Like

image

1 Like

image

1 Like

Current aloha servers (52.119.1.67) for me, in South of Brazil:

average ping: 198;

current_aloha

Host % Sent Recv Best Avrg Wrst Last
192.168.18.1 0 594 594 0 0 14 1
10.250.250.19 0 594 594 1 2 19 2
10.200.200.41 0 594 594 2 12 162 3
172.19.15.218 0 594 594 3 8 159 5
172.19.15.181 0 594 594 4 8 86 37
172.19.15.122 1 591 590 5 8 105 5
172.19.15.249 1 590 589 6 11 120 6
10.200.200.10 1 590 589 5 8 108 7
172.19.15.210 2 561 552 10 11 22 12
r200-40-65-157.su-static.anteldata.net.uy 0 594 594 16 17 253 16
brpa51.pdp-be12.antel.net.uy 2 565 557 138 140 157 141
ibe2mlg1-be11.antel.net.uy 2 553 542 138 139 169 140
crsan1.gru-ae1038.antel.net.uy 3 537 522 138 141 168 140
brmi11.mia-be6.antel.net.uy 1 591 590 137 138 158 138
ce-0-3-0-3.r05.miamfl02.us.bb.gin.ntt.net 1 587 585 137 138 160 138
ae-4.r22.miamfl02.us.bb.gin.ntt.net 2 564 556 138 142 182 144
ae-8.r20.dllstx14.us.bb.gin.ntt.net 6 485 457 167 170 195 173
ae-2.r24.lsanca07.us.bb.gin.ntt.net 3 545 532 196 200 245 205
ae-1.r00.lsanca07.us.bb.gin.ntt.net 1 576 571 194 196 214 194
ae-0.profuse-solutions.lsanca07.us.bb.gin.ntt.net 2 572 566 196 198 223 199
No response from host 100 120 0 0 0 0 0
67.1.119.52.ptr.fantomservers.com 3 535 519 196 198 218 197

IP (104.156.244.232) for me, in South of Brazil:

average ping: 137;

new_aloha

Host % Sent Recv Best Avrg Wrst Last
192.168.18.1 0 599 599 0 0 32 1
10.250.250.19 0 599 599 1 2 25 2
10.200.200.41 1 595 594 2 15 412 17
172.19.15.218 1 595 594 3 8 281 4
172.19.15.181 0 599 599 4 9 80 6
172.19.15.122 0 599 599 5 7 119 23
172.19.15.249 1 595 594 5 11 124 64
10.200.200.10 1 592 590 5 8 33 7
172.19.15.210 2 577 571 10 12 94 13
r200-40-65-157.su-static.anteldata.net.uy 1 595 594 15 17 91 16
ibe2mln1-be21.antel.net.uy 2 574 567 138 140 447 138
brmi12.mia-be2.antel.net.uy 2 573 566 137 139 152 141
brmi11.mia-be3.antel.net.uy 2 569 561 138 139 168 138
ce-0-3-0-3.r05.miamfl02.us.bb.gin.ntt.net 1 595 594 136 137 166 137
ae-4.r22.miamfl02.us.bb.gin.ntt.net 1 588 585 137 142 192 140
ae-3.a01.miamfl02.us.bb.gin.ntt.net 2 573 566 137 143 245 149
xe-0-0-28-0.a01.miamfl02.us.ce.gin.ntt.net 56 188 84 0 141 162 140
No response from host 100 121 0 0 0 0 0
No response from host 100 121 0 0 0 0 0
No response from host 100 121 0 0 0 0 0
104.156.244.232 1 596 595 136 137 153 137
1 Like

Italy:

— 104.156.244.232 ping statistics —
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 126.041/126.599/126.918/0.281 ms

— 52.119.1.67 ping statistics —
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 162.230/162.696/163.089/0.254 ms

1 Like

:rotating_light: attention! this is a test. this is only a test! :rotating_light:

these 4 servers are now ready to be play tested:

  1. aloha.pk arena useast/latam:
aos://832589101:43887
  1. aloha.pk babel useast/latam:
aos://832589101:34887
  1. aloha.pk 1v1 useast/latam:
aos://832589101:22887
  1. aloha.pk hallway useast/latam:
aos://832589101:32887

please report back with your experiences… the good, the bad, and the ugly!

thanks everyone