Selfhosted

Peering is actually a complex issue. The ISP you're currently using might not have a good peering with your data center operator.

One way to force a different peering is by complaining to your ISP. Include the server's IP address in the complain, and their sysadmin might take a look and alter their routing table so traffics going to your data center will go through different route (assuming the ISP is not shitty and have multiple high quality peering AND actually looking at your support request).

Another way is by using a VPN. By using a VPN, you'll bypass your ISP's network routing. Your traffic will go through your VPN provider's data center instead, which have completely different peering partners than your ISP. Try connecting to different country (e.g. Singapore, Hong Kong, Japan, Europe) to see which one is the fastest. For example, your ISP might have a good peering to Hong Kong, so by connecting to a Hong Kong VPN server, you'll bypass your ISP's shitty peering to Europe.

Finger cross though. In general, connection between this part of Asia and Europe is not great because there is no direct route. Connection to US is a lot faster in comparison because there are many direct undersea fiber optics links.

Okay, so I have actually lived in Korea for 15 years, and am into self hosting, servers for media, etc.

What I can tell you is, you are fucked. Peering to anywhere other than Japan is a nightmare.

Give up and build your own server in your own home. No amount of peering tricks or CDNs will help you.

The best you'll get in terms of connections to major service providers is hosting in Dallas, which should get you around 100mbps.

Welcome to the reason why a competitor to YouTube is almost impossible. Network routing is extremely complicated and short of laying your own cables or having multiple points of presence there's not much you can do about it.

You're probably limited by your TCP window sizes and congestion control algorithm. Look up a TCP throughput calculator and adjust your window size/congestion control as needed.

If your hosting provider doesn't grant access to this level, you could try various tunnels, like a UDP VPN that might be more resiliant. Again, not sure how limited you are with your provider. Worst case you could UDP VPN into a server in the same city as your host

I know it sounds funny, but look up the "long, fat pipe problem." Latency matters to TCP network connections and signals can only move so fast through a wire.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

5 acronyms in this thread; the most compressed thread commented on today has 13 acronyms.

[Thread #160 for this sub, first seen 24th Sep 2023, 08:15] [FAQ] [Full list] [Contact] [Source code]

They are limited to 50mbps, as far as I remember, and considering your distance, I would say the ping speeds should be somewhere between 170ms and 250ms.

I've only ever used Oracle cloud in an enterprise environment, so I don't know what features you have available. I'm also much more familiar with AWS. But you should be able to create a proxy endpoint in your present region, and traverse the cloud providers internal network. That would likely improve your streaming. You could also create a VPN endpoint in your current region and terminate your traffic inside your cloud providers network, but that would add protocol overhead.

I would look at tools like iperf to look at your packet loss because being further from your server will increase latency, but shouldn't impact the streaming unless you also have packet loss.

My PeerTube server https://tube.jeena.net is in Germany and I'm also in Korea, but I don't really feel any speed problems.