Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


[OVH] Routing issues Singapore -> Indonesia, Singapore -> Philippines
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

[OVH] Routing issues Singapore -> Indonesia, Singapore -> Philippines

jordynegen11jordynegen11 Member
edited July 2021 in General

Oh yes it's OVH time again :# After the recent Ipv6 issues (I still have), we now got a new problem.

We had a lot customers from indonesia (also philippines) complain about high latency between OVH Singapore and their provider in indonesia. Using MTR we found out that traffic from and to AS7713 is routed over NTT US.

The route now is: Singapore -> Japan -> us -> indonesia. Which causes extremely high latency of course. It does not make sense since singapore and indonesia are litterly neighbours. The exact same thing is happing for providers in the philippines.

When I asked OVH to fix it, they fixed it for a while. Good job OVH! But after half an hour they revert the changes. This was their answer:

Solution proposed says the ticket: :D

From OVH Support
Hello Jordy,

thanks for replying.

After we force the traffic via Equinix IX Singapore, we have a lot of packet loss (customers are saying that the network is unusable or the server is down), 
and After talking  with our customers, they prefer no packet loss, so we have to maintain traffic over NTT.

Best Regards,

Ok their changes caused packetloss. Understandable, shit happends but they wont fix that, instead maintain traffic over NTT and I will have to deal with the 200ms ping, which should be 30.. uhh... @OVH_APAC you watching?

Since PT TELKOM INDONESIA is like the biggest ISP in indonesia you might want to fix it? LOL
If your support keeps giving me these shitty answers I will post it here.

MTR result:

 Host                                                                     Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 51.79.228.252                                                          0.0%    20    0.6   0.5   0.4   0.8   0.1
 2. 10.161.49.125                                                          0.0%    19    0.2   0.2   0.1   0.2   0.0
 3. 10.133.3.58                                                            0.0%    19    0.6   0.6   0.5   0.8   0.1
 4. 10.75.0.32                                                             0.0%    19    0.2   0.2   0.1   0.2   0.0
 5. 10.75.248.2                                                            0.0%    19    0.8   1.0   0.6   2.2   0.4
 6. sin-sg1-sbb1-nc5.sgp.asia                                              0.0%    19    0.9   0.9   0.8   1.1   0.1
 7. 10.200.0.192                                                           0.0%    19    0.8  29.7   0.8 234.8  61.8
 8. ???
 9. ae-0.r23.sngpsi07.sg.bb.gin.ntt.net                                    0.0%    19    1.4   2.6   0.8  18.7   4.2
10. ae-1.r22.sngpsi07.sg.bb.gin.ntt.net                                    0.0%    19    1.8   3.2   1.0   8.6   2.5
11. ae-4.r27.osakjp02.jp.bb.gin.ntt.net                                    0.0%    19   65.8  66.6  65.2  72.0   1.9
12. ae-3.r24.lsanca07.us.bb.gin.ntt.net                                    0.0%    19  175.7 173.6 172.7 175.7   0.8
13. ae-8.r25.lsanca07.us.bb.gin.ntt.net                                    0.0%    19  174.6 176.2 174.6 184.8   2.8
14. ae-2.r00.lsanca07.us.bb.gin.ntt.net                                    0.0%    19  172.8 173.0 172.8 173.2   0.1
15. ???
16. 38.142.236.2                                                           0.0%    19  185.5 185.5 185.2 185.8   0.2
17. 180.240.192.73                                                         0.0%    19  175.9 176.7 175.7 184.2   2.6
18. 180.240.190.130                                                        0.0%    19  176.3 176.5 176.2 176.8   0.2
19. ???

Anyone else having the same issues? Test IP: 180.249.145.5

«1

Comments

  • I think the issue is TELKOM network itself.. this is traceroute from Jakarta using Balifiber (AS136119)

    Thanked by 2jordynegen11 ariq01
  • jordynegen11jordynegen11 Member
    edited July 2021

    @chocolateshirt said:
    I think the issue is TELKOM network itself.. this is traceroute from Jakarta using Balifiber (AS136119)

    I'm not a BGP/routing expert at all but OVH did manage to fix it for 30 minutes, but reverted the changes after packet loss occur.

    It only happends when using the OVH network. I have no issues with my servers at PhoenixNAP singapore.

  • This is using same TELKOM Selular network

  • This is from Philippines Converge ICT

    $ traceroute 180.249.145.5
     1?: [LOCALHOST]                      pmtu 1500
     1:  no reply
     2:  10.154.80.1                                          22.450ms
     3:  172.20.28.41                                          8.026ms
     4:  93.2.49.161-rev.convergeict.com                       5.088ms
     5:  145.1.49.161-rev.convergeict.com                      5.134ms
     6:  62.3.49.161-rev.convergeict.com                      32.560ms
     7:  7713.sgw.equinix.com                                 32.780ms
     8:  no reply
     9:  180.240.204.14                                       44.195ms
    10:  180.240.190.58                                       35.706ms asymm  9
    11:  180.252.2.117                                       106.620ms asymm 10
    12:  180.252.2.118                                       202.038ms asymm 11
    13:  180.252.3.58                                         77.456ms pmtu 1492
    13:  180.249.145.5                                       125.193ms reached
    
    Thanked by 1jordynegen11
  • Can > @chocolateshirt said:

    This is using same TELKOM Selular network

    Can you do a traceroute to 51.79.228.107 ?

  • shellshell Member

    @jordynegen11 said:
    Can you do a traceroute to 51.79.228.107 ?

    from AS7713 PT Telekomunikasi Indonesia Location: Jakarta, Indonesia

    # ADDRESS                          LOSS SENT    LAST     AVG    BEST   WORST STD-DEV STATUS
    1 gpon.net                           0%    5   0.6ms     0.5     0.3     0.7     0.2
    2 125.166.100.1                      0%    5     3ms     4.5     1.6    12.4       4
    3 180.252.1.101                      0%    5   1.6ms     1.6     1.2     2.1     0.4
    4 180.240.190.54                     0%    5    17ms    16.9    16.3    17.3     0.3
    5 180.240.190.53                     0%    5  16.9ms    19.2    16.7    27.1       4
    6                                  100%    5 timeout
    7 180.240.204.84                     0%    5  17.3ms    16.8    16.3    17.3     0.4
    8 103.5.15.20                        0%    5 219.3ms   197.5   190.4   219.3    11.1
    9                                  100%    5 timeout
    10                                  100%    5 timeout
    11                                  100%    5 timeout
    12 sin1-sgcs2-g1-nc5.sgp.asia         0%    5   194ms   193.4   192.1   194.5     0.8
    13 sin1-sgcs2-vac1-a75.sgp.asia       0%    5 182.4ms   183.4   182.4   185.2       1
    14 sin1-sgcs2-vac1-a75-1.sgp.asia     0%    5 186.8ms   186.7   186.5   186.8     0.1
    15 sin1-sgcs2-vac1-a75-2.sgp.asia     0%    5 186.9ms     187   186.8   187.1     0.1
    16 sin1-sgcs2-vac1-a75.sgp.asia       0%    5 187.3ms   187.4   187.1   188.3     0.4
    17                                  100%    5 timeout
    18                                  100%    5 timeout
    19                                  100%    5 timeout
    20                                  100%    5 timeout
    21 ns5005249.ip-51-79-228.net         0%    5 196.5ms     197   196.5   197.4     0.4
    

    from AS7713 PT Telekomunikasi Indonesia Location: Central Java, Indonesia

    # ADDRESS                          LOSS SENT    LAST     AVG    BEST   WORST STD-DEV STATUS
    1 gpon.net                           0%    5   0.3ms     0.4     0.3     0.5     0.1
    2 10.45.240.1                        0%    5   7.9ms     7.1     4.2    11.6     2.6
    3 125.160.0.29                       0%    5   1.9ms     1.9     1.2     2.9     0.5
    4 180.240.190.194                    0%    5    27ms    26.9    26.8    27.1     0.1
    5 180.240.190.193                    0%    5  27.6ms    27.9    27.1    29.9       1
    6 180.240.204.104                    0%    5  27.5ms    27.7    27.3    28.2     0.4
    7                                  100%    5 timeout
    8                                  100%    5 timeout
    9                                  100%    5 timeout
    10                                  100%    5 timeout
    11 sin-sgcs2-g2-nc5.sgp.asia         40%    5 timeout      29    28.8    29.3     0.2
    12 sin1-sgcs2-vac1-a75.sgp.asia      20%    5  28.7ms    28.3    28.1    28.7     0.2
    13 sin1-sgcs2-vac1-a75-1.sgp.asia    40%    5  28.4ms    28.1    27.8    28.4     0.2
    14 sin1-sgcs2-vac1-a75-2.sgp.asia    60%    5 timeout    28.5    28.1    28.8     0.4
    15 sin1-sgcs2-vac1-a75.sgp.asia       0%    5  28.2ms    28.3    27.9    28.9     0.3
    16                                  100%    5 timeout
    17                                  100%    5 timeout
    18                                  100%    5 timeout
    19                                  100%    5 timeout
    20 ns5005249.ip-51-79-228.net        20%    5 timeout    28.5    28.1    28.8     0.3
    

    from AS17451 BiznetNetworks Location: Jakarta, Indonesia

    # ADDRESS                          LOSS SENT    LAST     AVG    BEST   WORST STD-DEV STATUS
    1 112.78.160.xxx                     0%    2   6.7ms     4.3     1.8     6.7     2.5
    2 182.253.100.233                    0%    2     6ms     5.6     5.2       6     0.4
    3 equx-1.biznetnetworks.com          0%    2  16.5ms    16.5    16.5    16.5       0
    4 v111.core1.sin1.he.net             0%    2  20.4ms    18.1    15.7    20.4     2.4
    5 16276.sgw.equinix.com              0%    2  17.2ms      18    17.2    18.7     0.8
    6                                  100%    2 timeout
    7                                  100%    2 timeout
    8                                  100%    2 timeout
    9 sin1-sgcs2-g1-nc5.sgp.asia         0%    2  17.5ms    17.7    17.5    17.8     0.2
    10 sin1-sgcs2-vac1-a75.sgp.asia       0%    2  16.4ms    16.5    16.4    16.5     0.1
    11 sin1-sgcs2-vac1-a75-1.sgp.asia     0%    2  15.8ms    15.8    15.7    15.8     0.1
    12 sin1-sgcs2-vac1-a75-2.sgp.asia     0%    2  17.4ms    17.3    17.2    17.4     0.1
    13 sin1-sgcs2-vac1-a75.sgp.asia       0%    2    16ms    15.9    15.8      16     0.1
    14                                  100%    2 timeout
    15                                  100%    2 timeout
    16                                  100%    2 timeout
    17                                  100%    1 timeout
    18 ns5005249.ip-51-79-228.net         0%    1  17.8ms    17.8    17.8    17.8       0
    

    from AS17670 PT. MNC Kabel Mediacom Location: West Java, Indonesia

    |------------------------------------------------------------------------------------------|
    |                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
    |------------------------------------------------|------|------|------|------|------|------|
    |                            192.168.16.1 -    0 |   13 |   13 |    2 |    2 |    4 |    3 |
    |                           local.Network -    0 |   13 |   13 |    3 |    4 |    6 |    3 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |                ip-84-1.mncplaymedia.com -    0 |   13 |   13 |    5 |    8 |   13 |    8 |
    |                           202.80.208.97 -    0 |   13 |   13 |    6 |    7 |   13 |    6 |
    |                         103.129.216.125 -    0 |   13 |   13 |    5 |    6 |   10 |    6 |
    |      ip-103-83-6-106.moratelindo.net.id -    0 |   13 |   13 |    7 |    8 |   13 |    8 |
    |        ip-103-83-6-2.moratelindo.net.id -    0 |   13 |   13 |   23 |   24 |   31 |   23 |
    |                             ovh.sgix.sg -   25 |    4 |    3 |   25 |   25 |   27 |   25 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |                             103.5.15.17 -   40 |    5 |    3 |    0 |   24 |   26 |   26 |
    |            sin1-sgcs2-vac1-a75.sgp.asia -    0 |   13 |   13 |   22 |   24 |   29 |   29 |
    |          sin1-sgcs2-vac1-a75-1.sgp.asia -    0 |   13 |   13 |   24 |   27 |   32 |   31 |
    |          sin1-sgcs2-vac1-a75-2.sgp.asia -    0 |   13 |   13 |   21 |   23 |   27 |   23 |
    |            sin1-sgcs2-vac1-a75.sgp.asia -    0 |   13 |   13 |   25 |   26 |   32 |   31 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |              ns5005249.ip-51-79-228.net -    0 |   13 |   13 |   22 |   24 |   30 |   30 |
    |________________________________________________|______|______|______|______|______|______|
    

    from AS24203 PT XL Axiata (cellular) Location: Indonesia

    |------------------------------------------------------------------------------------------|
    |                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
    |------------------------------------------------|------|------|------|------|------|------|
    |                          192.168.182.92 -    0 |   12 |   12 |    2 |    4 |    5 |    5 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |                          10.195.173.194 -    0 |   12 |   12 |   36 |   49 |   97 |   47 |
    |                           10.195.32.206 -    0 |   12 |   12 |   27 |   51 |   89 |   48 |
    |                   24203.sgw.equinix.com -    0 |   12 |   12 |   56 |   70 |  110 |   70 |
    |                   16276.sgw.equinix.com -    0 |   12 |   12 |   43 |   64 |  109 |   63 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |              sin1-sgcs2-g1-nc5.sgp.asia -    0 |   12 |   12 |   50 |   67 |  110 |   54 |
    |            sin1-sgcs2-vac1-a75.sgp.asia -    0 |   12 |   12 |   49 |   63 |  103 |   56 |
    |          sin1-sgcs2-vac1-a75-1.sgp.asia -    0 |   12 |   12 |   53 |   66 |  109 |   63 |
    |          sin1-sgcs2-vac1-a75-2.sgp.asia -    0 |   12 |   12 |   55 |   69 |  110 |   70 |
    |            sin1-sgcs2-vac1-a75.sgp.asia -    0 |   12 |   12 |   42 |   61 |   99 |   71 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
    |              ns5005249.ip-51-79-228.net -    0 |   12 |   12 |   43 |   62 |   99 |   70 |
    |________________________________________________|______|______|______|______|______|______|
    
    Thanked by 2ariq01 jordynegen11
  • Welcome to routing in south east asia!

    In all seriousness, in general there's nothing you can do, just pray they fix it and if they don't, you'll need to find another way :(

    Thanked by 1bdl
  • fazarfazar Member

    telkom is sucks. they keep add more customers, but seems did not improving their networks. as far as I know, this issue also affected connections to digitalocean, vultr, cloudflare, etc.

    Thanked by 1jordynegen11
  • edited July 2021

    This is not OVH fault and do not blame OVH for this issue.

    OVH have **many **capacity in IX & upstream (they recently upgraded to 200G, Equinix SG), you can see the usage here: http://weathermap.ovh.net/#apac

    The issue is with Telkom Indonesia itself, they have limited capacity in IXs & traffic shaping system, which limits hosting/cloud traffic to go inside Telkom Indonesia's network.

    The solution? OVH & Telkom Indonesia must establish mutual partnership so that they can have their own PNI (private connection, not over IX).

    Why other providers like PhoenixNAP are not affected, eventhough same routing/exchange? Because they do not carry as much traffic as OVH does to Telkom Indonesia's network, so for Telkom it's okay. But if it reaches OVH-level traffic, then they will start limiting the traffic coming in.

    For Telkom, their mindset is "do you need us? or we need you?"

    Thanked by 2jordynegen11 umzak
  • It's always Telkom fault. If you don't have private peering (aka pay them), then never expect anything. They hate public peering as they cannot generate revenue from it. Even with local provider and ISP, they don't play nicely. They only have 50 Gbps port in the biggest public IX in Jakarta (OpenIXP).

    You can check OVH latency with here http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS7713

  • @nanankcornering said:
    This is not OVH fault and do not blame OVH for this issue.

    OVH have **many **capacity in IX & upstream (they recently upgraded to 200G, Equinix SG), you can see the usage here: http://weathermap.ovh.net/#apac

    The issue is with Telkom Indonesia itself, they have limited capacity in IXs & traffic shaping system, which limits hosting/cloud traffic to go inside Telkom Indonesia's network.

    The solution? OVH & Telkom Indonesia must establish mutual partnership so that they can have their own PNI (private connection, not over IX).

    Why other providers like PhoenixNAP are not affected, eventhough same routing/exchange? Because they do not carry as much traffic as OVH does to Telkom Indonesia's network, so for Telkom it's okay. But if it reaches OVH-level traffic, then they will start limiting the traffic coming in.

    For Telkom, their mindset is "do you need us? or we need you?"

    Thanks for this. In that case it isn't OVH their fault, I understand. The question I have then, why does the OVH support not telling me this...

  • OVH_APACOVH_APAC Member, Patron Provider
    edited July 2021

    Hello @jordynegen11 , our network team is always trying to look for solutions to solve networking issues including with telecom providers in a specific geography, however this is true the fault is not always seating 100% at OVHcloud.
    For info, here is a list of the main providers in Indonesia that we are peering with: http://sgp.smokeping.ovh.net/smokeping?filter=ID+

  • fazarfazar Member
    edited July 2021

    @OVH_APAC said:
    Hello @jordynegen11 , our network team is always trying to look for solutions to solve networking issues including with telecom providers in a specific geography, however this is true the fault is not always seating 100% at OVHcloud.
    For info, here is a list of the main providers in Indonesia that we are peering with: http://sgp.smokeping.ovh.net/smokeping?filter=ID+

    as we can see here, all ISP has acceptable performance. but not for Telkom. trully shown bad case of monopoly. 🤪

    Thanked by 2OVH_APAC danninov
  • in telkom case, temporary solution is ... don't buy ovh

    i know it is not 100% ovh fault

  • indonesia
    right or wrong is my country
    since telkom is state-owned enterprise
    :D :D :D :D :D

  • jordynegen11jordynegen11 Member
    edited July 2021

    @OVH_APAC said:
    Hello @jordynegen11 , our network team is always trying to look for solutions to solve networking issues including with telecom providers in a specific geography, however this is true the fault is not always seating 100% at OVHcloud.
    For info, here is a list of the main providers in Indonesia that we are peering with: http://sgp.smokeping.ovh.net/smokeping?filter=ID+

    I totally understand. If your support does communicate this too me in the open ticket I wouldn't be crying on this forum right know. A response that the issue is on the Telkom side and they are working on a solution would be more then fine.

    Instead they offer me a "solution" that is not a solution. As a customer, I be kept in the dark and then I come here to find answers.

    For me its also clear now, Im gonna stalk Telkom untill they fix their peering 😎

    Thanked by 1pedagang
  • @jordynegen11 said:

    @OVH_APAC said:
    Hello @jordynegen11 , our network team is always trying to look for solutions to solve networking issues including with telecom providers in a specific geography, however this is true the fault is not always seating 100% at OVHcloud.
    For info, here is a list of the main providers in Indonesia that we are peering with: http://sgp.smokeping.ovh.net/smokeping?filter=ID+

    I totally understand. If your support does communicate this too me in the open ticket I wouldn't be crying on this forum right know. A response that the issue is on the Telkom side and they are working on a solution would be more then fine.

    Instead they offer me a "solution" that is not a solution. As a customer, I be kept in the dark and then I come here to find answers.

    For me its also clear now, Im gonna stalk Telkom untill they fix their peering 😎

    You're gonna have lots of fun with that. I'm not from Indonesia, but knowing the antics of even ISPs in North America (Cogent vs HE ipv6, etc.) it's gonna be a very long time before things change.

    You really can't expect much from South East Asia in terms of routing, I've been looking at MTRs for a while from the region and holy shit is it a mess. Overcongested routes (hey what's 40 percent packet loss anyway?), transcontinental routes for neighboring countries (like we see here) and just random jumps in latency between two supposedly close locations. It's all there and it's all a mess.

    Good luck.

    Thanked by 1jordynegen11
  • @ehhthing said:

    @jordynegen11 said:

    @OVH_APAC said:
    Hello @jordynegen11 , our network team is always trying to look for solutions to solve networking issues including with telecom providers in a specific geography, however this is true the fault is not always seating 100% at OVHcloud.
    For info, here is a list of the main providers in Indonesia that we are peering with: http://sgp.smokeping.ovh.net/smokeping?filter=ID+

    I totally understand. If your support does communicate this too me in the open ticket I wouldn't be crying on this forum right know. A response that the issue is on the Telkom side and they are working on a solution would be more then fine.

    Instead they offer me a "solution" that is not a solution. As a customer, I be kept in the dark and then I come here to find answers.

    For me its also clear now, Im gonna stalk Telkom untill they fix their peering 😎

    You're gonna have lots of fun with that. I'm not from Indonesia, but knowing the antics of even ISPs in North America (Cogent vs HE ipv6, etc.) it's gonna be a very long time before things change.

    You really can't expect much from South East Asia in terms of routing, I've been looking at MTRs for a while from the region and holy shit is it a mess. Overcongested routes (hey what's 40 percent packet loss anyway?), transcontinental routes for neighboring countries (like we see here) and just random jumps in latency between two supposedly close locations. It's all there and it's all a mess.

    Good luck.

    Thanks I gonna need it.

    Fact is that OVH is missing a lot of indonesian customers. Daily we get multiple request from TELKOM users and they always ask: "Are you servers located at OVH, because they have bad latency". So would be good for OVH to push themselfs also.

  • JioJio Member
    edited July 2021

    @jordynegen11 said: Fact is that OVH is missing a lot of indonesian customers. Daily we get multiple request from TELKOM users and they always ask: "Are you servers located at OVH, because they have bad latency". So would be good for OVH to push themselfs also.

    It doesn't matter. Telkom MUCH bigger than OVH, does not give a fuck, government enforced monopoly.

    Same thing happen in Philippines with PLDT. Does not give a fuck about you no matter how big you are.

    image

    Guaranteed the answer from telkom will be is "maybe those customers should just host on TELKOM DC then" and give middle finger.

    This kind of situation is like a 1 person minecraft host trying to ask foreign billionaire for a handout. They won't even reply

  • @jordynegen11 said:

    .... "Are you servers located at OVH, because they have bad latency". ...

    noted

  • fazarfazar Member

    Personally, I have similar issue to digitalocean. I managed database for warehouse app, and its hosted on DO droplet. 3 remote sites access it 24/7, and app synced to indocement server (one of the biggest cement producer in Indonesia).

    I escalate this issue to Telkom support. Their tech support cynically reply my question by simply saying "there is a lot free VPN provider out there. ask your client to use it instead of directly using our connection". wtf. 😡

    Last time, their capacity is running out. They utilise maximum capacity of their 40G bandwidth on largest Indonesian IX, then they upgrade to 50G, but not really helps to cover the problem.

    seems they have no good will to resolve their customer problems. There is also other problems exist: intercepting DNS request, forcing adverts to customers, not respect customers privacy, etc.

  • I'm not a BGP expert but isn't OVH already peering directly with TELKOM?

    Source: https://bgp.he.net/AS7713#_peers

  • shellshell Member

    @jordynegen11 said:
    I'm not a BGP expert but isn't OVH already peering directly with TELKOM?

    Source: https://bgp.he.net/AS7713#_peers

    AFAIK
    ovh peering with telkom indonesia / telin 4x10G in los angeles CA

    Thanked by 1jordynegen11
  • shellshell Member

    @fazar said:
    Last time, their capacity is running out. They utilise maximum capacity of their 40G bandwidth on largest Indonesian IX, then they upgrade to 50G, but not really helps to cover the problem.

    telkom indonesia stuck with 40G to openIXP for many years and saturated their port everyday. this make problem for many indonesian isp
    good to know telkom add more capacity to openixp
    from mrtg, telkom port on openixp not saturated anymore

    @fazar said:
    seems they have no good will to resolve their customer problems. There is also other problems exist: intercepting DNS request, forcing adverts to customers, not respect customers privacy, etc.

    haha, it's true
    i have to use another dns server (opendns, clouflare, etc)

  • @shell said:

    @jordynegen11 said:
    I'm not a BGP expert but isn't OVH already peering directly with TELKOM?

    Source: https://bgp.he.net/AS7713#_peers

    AFAIK
    ovh peering with telkom indonesia / telin 4x10G in los angeles CA

    Yes, that's why OVH is now moving their traffic to Telkom Indonesia from LA.

  • jordynegen11jordynegen11 Member
    edited July 2021

    @shell said:

    @fazar said:
    Last time, their capacity is running out. They utilise maximum capacity of their 40G bandwidth on largest Indonesian IX, then they upgrade to 50G, but not really helps to cover the problem.

    telkom indonesia stuck with 40G to openIXP for many years and saturated their port everyday. this make problem for many indonesian isp
    good to know telkom add more capacity to openixp
    from mrtg, telkom port on openixp not saturated anymore

    @fazar said:
    seems they have no good will to resolve their customer problems. There is also other problems exist: intercepting DNS request, forcing adverts to customers, not respect customers privacy, etc.

    haha, it's true
    i have to use another dns server (opendns, clouflare, etc)

    It's scary too see the biggest provider of indonesia is using 48/50Gbit on the largest IX in indonesia. :'(

  • in 2020
    telkom indonesia
    telkom indihome 8,3 million customer / 85% marketshare broadband

    telkomsel (mobile/cellular) 169,5 million customer

    ... :D still alive

  • wpyogawpyoga Member
    edited July 2021

    Wow, so that's confirmed then. Telkom only has a 40 Gbps connection to OpenIXP. It was a bit unbelievable, since my home connection is "up to" 30 Mbps, and I often get 3 MB/s downloads, which also means that 1300 people like me can saturate the whole connection.

    Biznet even has an "up to" 150 Mbps home Internet service, so that means 300 customers would already saturate Telkom's connection... Too bad I can't get Biznet now, it's almost impossible to get their service in apartments.

    @jordynegen11 I don't know about your application, but you might want to take a look at self-hosting some kind of load balancer on a local datacenter with good connection to OVH. As for me, I don't do much with my VPSes, but sometimes I use my OVH VPS as a jump-box when I try to SSH to my other overseas VPSes, and it seems to help with latency.

    Thanked by 1jordynegen11
  • shellshell Member

    @jordynegen11 said:
    It's scary too see the biggest provider of indonesia is using 48/50Gbit on the largest IX in indonesia. :'(

    telkom indonesia, try to put "everything" inside their network.
    that's why 50G on Openixp enough for telkom, at least for now

  • Seems Indian Networks are far better 😌

Sign In or Register to comment.