- Posts: 21
- Thank you received: 8
Teamspeak IP Change
- {F4H}Femme{A}
- Topic Author
- Offline
- Administrator
Less
More
1 month 2 weeks ago #161
by {F4H}Femme{A}
Teamspeak IP Change was created by {F4H}Femme{A}
Bandwidth upgrade and IP renumbering
=6ptSep 23 2024 10:19:43 AM PT We have seen the old InterNAP/INAP (now called Unitas Global, owned by PacketFabric) bandwidth dropping in quality over time as this upstream shrinks its capacity, drops higher-cost upstream connections, reduces staffing, and switches to backhauling traffic through its own public peerings, all of which hurt its performance and capabilities -- to the point that it no longer meets our standards. By the end of the month, we will cease using this upstream at any location, and all current "InterNAP" locations will be upgraded to "Premium" status -- with upgraded capacity, as well. Each existing Premium location that currently uses the old InterNAP bandwidth will be receiving a replacement upstream, too, to supplement the remaining one(s).
Unfortunately, when this relationship is lost, we will also have to stop using any old InterNAP IP addresses and return them. Most of our voice (TeamSpeak and Murmur) servers have continued to use IP addresses that we have been using for decades, so those need to be changed over to IPs that we directly control. This includes your service. The good news is that (along with seeing bandwidth/capacity improvements) you will never have to change IPs again, as long as you stick with the same location.
We are currently planning to change the IP address of your service to 192.223.27.150 on Friday, September 27, between 9am and noon PDT (the port will remain the same). Sometime during that window, we will shut down the service, update the IP address in its configuration files/database, and start it back up. At the same time, we will update all DNS references to the old IP address on our end, including TSDNS. This means that if your clients use the standard DNS entry to connect to your service -- or your own 3rd-party DNS entry that syncs with ours -- then they should automatically reconnect to the new one.
We have always been extremely careful about not forcing IPs to be changed unless absolutely necessary. Though it is not as painful to switch IPs now as it once was, we recognize that it is still an invasive, manual process. Please accept our sincere apologies for this being unavoidable.
Update @ 12:31pm PDT on 9/27: We have postponed this adjustment until Monday, 9/30/24 between 9am and noon PDT.
Update @ 9:25am PDT on 9/30: This adjustment is now complete. If your TS3 server did not come back online automatically, please start it back up through the 'Server control' page of your control panel. All your files and settings have been retained and only the IP has been updated. If you have any trouble with the service on its new IP, please let us know ASAP!
=6ptSep 23 2024 10:19:43 AM PT We have seen the old InterNAP/INAP (now called Unitas Global, owned by PacketFabric) bandwidth dropping in quality over time as this upstream shrinks its capacity, drops higher-cost upstream connections, reduces staffing, and switches to backhauling traffic through its own public peerings, all of which hurt its performance and capabilities -- to the point that it no longer meets our standards. By the end of the month, we will cease using this upstream at any location, and all current "InterNAP" locations will be upgraded to "Premium" status -- with upgraded capacity, as well. Each existing Premium location that currently uses the old InterNAP bandwidth will be receiving a replacement upstream, too, to supplement the remaining one(s).
Unfortunately, when this relationship is lost, we will also have to stop using any old InterNAP IP addresses and return them. Most of our voice (TeamSpeak and Murmur) servers have continued to use IP addresses that we have been using for decades, so those need to be changed over to IPs that we directly control. This includes your service. The good news is that (along with seeing bandwidth/capacity improvements) you will never have to change IPs again, as long as you stick with the same location.
We are currently planning to change the IP address of your service to 192.223.27.150 on Friday, September 27, between 9am and noon PDT (the port will remain the same). Sometime during that window, we will shut down the service, update the IP address in its configuration files/database, and start it back up. At the same time, we will update all DNS references to the old IP address on our end, including TSDNS. This means that if your clients use the standard DNS entry to connect to your service -- or your own 3rd-party DNS entry that syncs with ours -- then they should automatically reconnect to the new one.
We have always been extremely careful about not forcing IPs to be changed unless absolutely necessary. Though it is not as painful to switch IPs now as it once was, we recognize that it is still an invasive, manual process. Please accept our sincere apologies for this being unavoidable.
Update @ 12:31pm PDT on 9/27: We have postponed this adjustment until Monday, 9/30/24 between 9am and noon PDT.
Update @ 9:25am PDT on 9/30: This adjustment is now complete. If your TS3 server did not come back online automatically, please start it back up through the 'Server control' page of your control panel. All your files and settings have been retained and only the IP has been updated. If you have any trouble with the service on its new IP, please let us know ASAP!
Please Log in or Create an account to join the conversation.
Time to create page: 2.129 seconds