Howdy, Stranger!

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

Sign In Register

Quick Links


Categories

In this Discussion

› › Cogent and TATA de-peer in Asia - Page 2
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.

Cogent and TATA de-peer in Asia

2»

Comments

  • SplitIceSplitIce Member, Host Rep

    Quickly falling to HE level

    Will likely end up (like HE) only good for hauling traffic between Cogent peers and dumping traffic in EU & US via Telia.

  • HarambeHarambe Member, Host Rep

    Had a few complaints in the last 24hrs about speeds from customers mostly in Indonesia. So this tracks...

  • kevindskevinds Member, LIR

    @jackb said:
    To be honest I think it's time we consider cogent a T2 like some people consider HE.

    Cogent customers don't have access to all of the internet, they never have. Cogent doesn't want them to.

    HE has access to everything except Cogent, but HE wants the issue fixed.

  • yoursunnyyoursunny Member, IPv6 Advocate

    Is Cogent even part of the Internet?

    Thanked by 1adly
  • conceptconcept Member
    edited May 18

    I am seeing my ReliableSite Los Angeles server routing traffic to Ashburn to France via Arelion/Telia to Tata.

    Seeing this for OVH Hillsboro

    traceroute to 203.196.202.225 (203.196.202.225), 30 hops max, 60 byte packets  -  Generated at 2024-05-18 01:15:01

 3 > 10.244.17.14                                  (10.244.17.14)    0.548      ms0.360    ms0.390    ms0.389   
 4 > 10.244.72.16                                  (10.244.72.16)    0.256      ms0.180    ms0.121    ms0.070   
 5 > 10.244.120.68                                 (10.244.120.68)   2.949      ms                              
 6 > be102.pdx-prt1-sbb1-8k.oregon.us              (142.44.208.228)  1.949      ms2.961    ms3.975    ms        
 7 > 10.200.1.5                                    (10.200.1.5)      0.986      ms0.981    ms0.735    ms0.764   
 8 >                                                                                                            
 9 > sea-b3-link.ip.twelve99.net                   (62.115.139.133)  4.278      ms4.177    ms4.187    ms4.163   
10 > sea-b1-link.ip.twelve99.net                   (62.115.132.157)  4.634      ms5.009    ms4.744    ms4.868   
11 > ix-be-16.ecore1.00s-seattle.as6453.net        (64.86.123.24)    4.604      ms4.623    ms4.659    ms4.572   
12 > if-ae-49-2.tcore2.00s-seattle.as6453.net      (63.243.226.5)    272.330    ms272.284  ms272.435  ms272.198 
13 > if-ae-25-2.tcore2.ct8-chicago.as6453.net      (207.45.206.1)    271.700    ms                              
14 > if-ae-22-2.tcore1.ct8-chicago.as6453.net      (64.86.79.2)      280.147    ms280.297  ms                   
15 > if-ae-26-2.tcore3.nto-newyork.as6453.net      (216.6.81.28)     280.690    ms280.343  ms                   
16 > if-ae-32-3.tcore2.ldn-london.as6453.net       (80.231.20.106)   275.158    ms                              
17 > if-ae-26-2.tcore1.ldn-london.as6453.net       (80.231.62.58)    271.153    ms                              
18 > 195.219.213.130                               (195.219.213.130) 274.036    ms                              
19 > if-bundle-29-2.qcore2.mlv-mumbai.as6453.net   (209.58.105.2)    269.968    ms269.360  ms269.914  ms        
20 > if-ae-22-2.tcore2.mlv-mumbai.as6453.net       (180.87.39.9)     273.563    ms274.208  ms                   
21 > if-ae-2-2.tcore1.mlv-mumbai.as6453.net        (180.87.38.1)     269.309    ms269.320  ms269.387  ms269.459 
22 > 180.87.38.6                                   (180.87.38.6)     269.732    ms269.691  ms269.830  ms269.927 
23 >                                                                                                            
24 > 121.244.40.161.static-mumbai.vsnl.net.in      (121.244.40.161)  276.820    ms276.768  ms276.852  ms276.972 
25 > 203.196.202.225                               (203.196.202.225) 269.809    ms269.854  ms269.850  ms269.842

    https://pdx1-hil.smokeping.ovh.net/smokeping?target=APAC.AS9238

  • SillyGooseSillyGoose Member

    Cogent's new peering solutions now includes sending everyone in apac a cable to connect their devices and network!

    Thanked by 2yoursunny BruhGamer12
  • SillyGooseSillyGoose Member
    edited May 18

    @concept said:
    I am seeing my ReliableSite @MrRadic Los Angeles server routing traffic to Ashburn to France via Arelion/Telia to Tata.

    Seeing this for OVH Hillsboro

    traceroute to 203.196.202.225 (203.196.202.225), 30 hops max, 60 byte packets  -  Generated at 2024-05-18 01:15:01

 3 > 10.244.17.14                                  (10.244.17.14)    0.548      ms0.360    ms0.390    ms0.389   
 4 > 10.244.72.16                                  (10.244.72.16)    0.256      ms0.180    ms0.121    ms0.070   
 5 > 10.244.120.68                                 (10.244.120.68)   2.949      ms                              
 6 > be102.pdx-prt1-sbb1-8k.oregon.us              (142.44.208.228)  1.949      ms2.961    ms3.975    ms        
 7 > 10.200.1.5                                    (10.200.1.5)      0.986      ms0.981    ms0.735    ms0.764   
 8 >                                                                                                            
 9 > sea-b3-link.ip.twelve99.net                   (62.115.139.133)  4.278      ms4.177    ms4.187    ms4.163   
10 > sea-b1-link.ip.twelve99.net                   (62.115.132.157)  4.634      ms5.009    ms4.744    ms4.868   
11 > ix-be-16.ecore1.00s-seattle.as6453.net        (64.86.123.24)    4.604      ms4.623    ms4.659    ms4.572   
12 > if-ae-49-2.tcore2.00s-seattle.as6453.net      (63.243.226.5)    272.330    ms272.284  ms272.435  ms272.198 
13 > if-ae-25-2.tcore2.ct8-chicago.as6453.net      (207.45.206.1)    271.700    ms                              
14 > if-ae-22-2.tcore1.ct8-chicago.as6453.net      (64.86.79.2)      280.147    ms280.297  ms                   
15 > if-ae-26-2.tcore3.nto-newyork.as6453.net      (216.6.81.28)     280.690    ms280.343  ms                   
16 > if-ae-32-3.tcore2.ldn-london.as6453.net       (80.231.20.106)   275.158    ms                              
17 > if-ae-26-2.tcore1.ldn-london.as6453.net       (80.231.62.58)    271.153    ms                              
18 > 195.219.213.130                               (195.219.213.130) 274.036    ms                              
19 > if-bundle-29-2.qcore2.mlv-mumbai.as6453.net   (209.58.105.2)    269.968    ms269.360  ms269.914  ms        
20 > if-ae-22-2.tcore2.mlv-mumbai.as6453.net       (180.87.39.9)     273.563    ms274.208  ms                   
21 > if-ae-2-2.tcore1.mlv-mumbai.as6453.net        (180.87.38.1)     269.309    ms269.320  ms269.387  ms269.459 
22 > 180.87.38.6                                   (180.87.38.6)     269.732    ms269.691  ms269.830  ms269.927 
23 >                                                                                                            
24 > 121.244.40.161.static-mumbai.vsnl.net.in      (121.244.40.161)  276.820    ms276.768  ms276.852  ms276.972 
25 > 203.196.202.225                               (203.196.202.225) 269.809    ms269.854  ms269.850  ms269.842

    https://pdx1-hil.smokeping.ovh.net/smokeping?target=APAC.AS9238

    I think reliablesite have tata communications as upstream

    Thanked by 1concept
  • vpn2024vpn2024 Member
    edited May 18

    What do they want from TATA? That they peer with them in India so Cogent can stop paying for TATA transit there, is that the game plan?

    Isn't this pretty common though, NTT doesn't let people peer with them in Hong Kong (or is it Japan, memory segault), SingTel don't in Singapore, Telstra dont in Australia? Also CU/CT will peer with people in LA but not in HK from what I remember. Seems established that you don't get to peer with people in their backyard..

    Not defending TATA or Cogent, just wondering if I got the right idea here.

    Thanked by 1stefeman
  • kevindskevinds Member, LIR

    @yoursunny said:
    Is Cogent even part of the Internet?

    They are walled-garden pretending to be the internet.

    Thanked by 1yoursunny
  • conceptconcept Member

    @SillyGoose said:
    I think reliablesite have tata communications as upstream

    oh they do. Good that more hosts have them as upstream.

  • trewqtrewq Administrator, Patron Provider

    This is just incumbents (NTT/Tata) not wanting to peering in their home market so Cogent isn’t peering in theirs. Over the last few years Cogent has build out a lot in APAC so they probably do fit the peering requirements of these incumbents (at least for peering in the region, probably not in country).

    Cogent being seen as the bad guy here only because they’re telling their customers what’s happening. NTT/Tata are protecting their profits, Cogent is trying to make it cost more not to do it.

    It’s just business.

    Thanked by 4Maounique fluffernutter dann00 Abd
  • trewqtrewq Administrator, Patron Provider

    @vpn2024 said:
    What do they want from TATA? That they peer with them in India so Cogent can stop paying for TATA transit there, is that the game plan?

    Isn't this pretty common though, NTT doesn't let people peer with them in Hong Kong (or is it Japan, memory segault), SingTel don't in Singapore, Telstra dont in Australia? Also CU/CT will peer with people in LA but not in HK from what I remember. Seems established that you don't get to peer with people in their backyard..

    Not defending TATA or Cogent, just wondering if I got the right idea here.

    They want them to peer in region properly. In country is a bit of a push as you stated.

  • BruhGamer12BruhGamer12 Member

    @SillyGoose said: Cogent's new peering solutions now includes sending everyone in apac a cable to connect their devices and network!

    This sounds like an onion headline lol.

  • MrRadicMrRadic Member, Host Rep, Veteran

    @concept said:
    I am seeing my ReliableSite Los Angeles server routing traffic to Ashburn to France via Arelion/Telia to Tata.

    Seeing this for OVH Hillsboro

    traceroute to 203.196.202.225 (203.196.202.225), 30 hops max, 60 byte packets  -  Generated at 2024-05-18 01:15:01

 3 > 10.244.17.14                                  (10.244.17.14)    0.548      ms0.360    ms0.390    ms0.389   
 4 > 10.244.72.16                                  (10.244.72.16)    0.256      ms0.180    ms0.121    ms0.070   
 5 > 10.244.120.68                                 (10.244.120.68)   2.949      ms                              
 6 > be102.pdx-prt1-sbb1-8k.oregon.us              (142.44.208.228)  1.949      ms2.961    ms3.975    ms        
 7 > 10.200.1.5                                    (10.200.1.5)      0.986      ms0.981    ms0.735    ms0.764   
 8 >                                                                                                            
 9 > sea-b3-link.ip.twelve99.net                   (62.115.139.133)  4.278      ms4.177    ms4.187    ms4.163   
10 > sea-b1-link.ip.twelve99.net                   (62.115.132.157)  4.634      ms5.009    ms4.744    ms4.868   
11 > ix-be-16.ecore1.00s-seattle.as6453.net        (64.86.123.24)    4.604      ms4.623    ms4.659    ms4.572   
12 > if-ae-49-2.tcore2.00s-seattle.as6453.net      (63.243.226.5)    272.330    ms272.284  ms272.435  ms272.198 
13 > if-ae-25-2.tcore2.ct8-chicago.as6453.net      (207.45.206.1)    271.700    ms                              
14 > if-ae-22-2.tcore1.ct8-chicago.as6453.net      (64.86.79.2)      280.147    ms280.297  ms                   
15 > if-ae-26-2.tcore3.nto-newyork.as6453.net      (216.6.81.28)     280.690    ms280.343  ms                   
16 > if-ae-32-3.tcore2.ldn-london.as6453.net       (80.231.20.106)   275.158    ms                              
17 > if-ae-26-2.tcore1.ldn-london.as6453.net       (80.231.62.58)    271.153    ms                              
18 > 195.219.213.130                               (195.219.213.130) 274.036    ms                              
19 > if-bundle-29-2.qcore2.mlv-mumbai.as6453.net   (209.58.105.2)    269.968    ms269.360  ms269.914  ms        
20 > if-ae-22-2.tcore2.mlv-mumbai.as6453.net       (180.87.39.9)     273.563    ms274.208  ms                   
21 > if-ae-2-2.tcore1.mlv-mumbai.as6453.net        (180.87.38.1)     269.309    ms269.320  ms269.387  ms269.459 
22 > 180.87.38.6                                   (180.87.38.6)     269.732    ms269.691  ms269.830  ms269.927 
23 >                                                                                                            
24 > 121.244.40.161.static-mumbai.vsnl.net.in      (121.244.40.161)  276.820    ms276.768  ms276.852  ms276.972 
25 > 203.196.202.225                               (203.196.202.225) 269.809    ms269.854  ms269.850  ms269.842

    https://pdx1-hil.smokeping.ovh.net/smokeping?target=APAC.AS9238

    We have TATA on net.

  • lothoslothos Member

    Who hasn't Cogent had a peering spat with lol

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    @lothos said:
    Who hasn't Cogent had a peering spat with lol

    Cogent Europe, but I'm sure Cogent NA is working on that too.

    Francisco

    Thanked by 2lothos adly
Sign In or Register to comment.