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
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

sh97sh97 Member
edited May 17 in News

Just came across this.
Looks like Indian routes are the most affected ones.

https://x.com/bgptools/status/1791470879697752258

https://www.reddit.com/r/networking/comments/1cu13bv/cogent_depeering_tata/

First NTT, now TATA.

Thanked by 1Not_Oles
«1

Comments

  • ehhthingehhthing Member

    Why does Cogent constantly pick fights with other T1s? Is this just greed?

  • kevindskevinds Member, LIR

    @ehhthing said:
    Why does Cogent constantly pick fights with other T1s? Is this just greed?

    Greed combined with being a bully..

  • davidedavide Member
    edited May 17

    No amount of good will and good faith augments on Cogent’s part has brought TATA any closer to the negotiating table for a resolution to the lack of connectivity in Asia

    Diversity hiring got a primadonna right there at PR

  • MrRadicMrRadic Member, Host Rep, Veteran

    Ouch, I can't imagine this is helping Cogent at all.

    Thanked by 2host_c tentor
  • sh97sh97 Member

    Tried pinging @LittleCreek (Single Home Cogent) from my Indian ISP, its unreachable.

    ping 38.45.64.1

Pinging 38.45.64.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 38.45.64.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    Thanked by 1Not_Oles
  • emghemgh Member

    @sh97 said:
    Tried pinging @LittleCreek (Single Home Cogent) from my Indian ISP, its unreachable.

    ping 38.45.64.1

Pinging 38.45.64.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 38.45.64.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    m y i m no respond pings sorry

    Thanked by 3sh97 anubhavhirani sasslik
  • balrammbalramm Member, Host Rep

    @sh97 said:
    Tried pinging @LittleCreek (Single Home Cogent) from my Indian ISP, its unreachable.

    ping 38.45.64.1

Pinging 38.45.64.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 38.45.64.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    Which ISP?

  • sh97sh97 Member

    @emgh said:

    @sh97 said:
    Tried pinging @LittleCreek (Single Home Cogent) from my Indian ISP, its unreachable.

    ping 38.45.64.1

Pinging 38.45.64.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 38.45.64.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    m y i m no respond pings sorry

    hello,
    it s possible yu respond my DM?
    Regards

    Thanked by 1emgh
  • sh97sh97 Member
    edited May 17

    @balramm said:

    @sh97 said:
    Tried pinging @LittleCreek (Single Home Cogent) from my Indian ISP, its unreachable.

    ping 38.45.64.1

Pinging 38.45.64.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 38.45.64.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    Which ISP?

    Local ISP, upstreamed by TATA and Airtel. I think most ISPs use that combination.

    Thanked by 1balramm
  • zGatozGato Member
    edited May 17

    My SG VPS with Contabo (Cogent) has seen a huge impact actually. Apart from huge latency (+500ms from Spain) I have a lot of packet loss (I'm getting routed through HE now)

  • IvanIvan Member

    @emgh said:

    @sh97 said:
    Tried pinging @LittleCreek (Single Home Cogent) from my Indian ISP, its unreachable.

    ping 38.45.64.1

Pinging 38.45.64.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 38.45.64.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    m y i m no respond pings sorry

    my i m pings r depereeding by cogen probelm, route r no work now sorry. we will fix asap have new tiire 1 coming soon 2gbps we make bgp. sorry plz and no refund updte soon

    Thanked by 2sh97 emgh
  • host_chost_c Member, Patron Provider

    I think somebody is running out of $ to pay it's invoices...???

    Thanked by 1Calin
  • tentortentor Member, Host Rep

    Cogent becomes T2 soon?

    Thanked by 2host_c yoursunny
  • FranciscoFrancisco Top Host, Host Rep, Veteran

    @tentor said:
    Cogent becomes T2 soon?

    Going to become an island soon at this rate.

    Francisco

    Thanked by 10kevinds sillycat adly host_c jackb maverickp breached fluffernutter shelfchair fart
  • zmeuzmeu Member

    @tentor said:
    Cogent becomes T2 soon?

    It wasn't already?

  • host_chost_c Member, Patron Provider

    as it seems, we got hit by this too

    https://ping.pe/193.32.87.1

    @zmeu said: It wasn't already?

    true :smiley:

    Thanked by 1zmeu
  • DataIdeas-JoshDataIdeas-Josh Member, Patron Provider

    I've been noticing a lot of "filled pipes" moving traffic through Cogent -> Arelion (Telia)

  • jackbjackb Member, Host Rep

    @ehhthing said:
    Why does Cogent constantly pick fights with other T1s? Is this just greed?

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

  • emghemgh Member

    @sh97 said:

    @emgh said:

    @sh97 said:
    Tried pinging @LittleCreek (Single Home Cogent) from my Indian ISP, its unreachable.

    ping 38.45.64.1

Pinging 38.45.64.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 38.45.64.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    m y i m no respond pings sorry

    hello,
    it s possible yu respond my DM?
    Regards

    no

    Regards

    @Ivan said: my i m pings r depereeding by cogen probelm, route r no work now sorry. we will fix asap have new tiire 1 coming soon 2gbps we make bgp. sorry plz and no refund updte soon

    cogen still problem? i s possible offer prize match , dm

    Thanked by 1sasslik
  • LeviLevi Member
    edited May 17

    Cogent lays down everything on the table. Who’s bigger?

  • sh97sh97 Member

    @zGato said:
    My SG VPS with Contabo (Cogent) has seen a huge impact actually. Apart from huge latency (+500ms from Spain) I have a lot of packet loss (I'm getting routed through HE now)

    Noticing impact in other places too. My BuyVM Luxembourg was usually routed via Cogent to DE and came via Airtel to India. 160ms.

    Now it's going via HE, 1299 and TATA to London, heavy packet loss and 300ms+ ping.

  • sh97sh97 Member

    @emgh said:

    @sh97 said:

    @emgh said:

    @sh97 said:
    Tried pinging @LittleCreek (Single Home Cogent) from my Indian ISP, its unreachable.

    ping 38.45.64.1

Pinging 38.45.64.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 38.45.64.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    m y i m no respond pings sorry

    hello,
    it s possible yu respond my DM?
    Regards

    no

    Regards

    @Ivan said: my i m pings r depereeding by cogen probelm, route r no work now sorry. we will fix asap have new tiire 1 coming soon 2gbps we make bgp. sorry plz and no refund updte soon

    cogen still problem? i s possible offer prize match , dm

    im want give yu dmca ignor and free speaks. that it s possible also petabytes of porn.

    Thanked by 2emgh Deepak_leb
  • breachedbreached Member

    @sh97 said: https://x.com/bgptools/status/1791470879697752258

    On the reddit post, this is 'parentally the email they sent out to customers, which implies that Cogent used the SAME template as the depeering with NTT. I thought this was a copypasta at first, but turns out it's not.

    Oof.

  • JosephFJosephF Member

    @jackb said:

    @ehhthing said:
    Why does Cogent constantly pick fights with other T1s? Is this just greed?

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

    Who consider HE to be a T2?

  • yoursunnyyoursunny Member, IPv6 Advocate

    @Francisco said:

    @tentor said:
    Cogent becomes T2 soon?

    Going to become an island soon at this rate.

    53667 depeer with 174 when?
    (peer with 701 instead)

  • dfroedfroe Member, Host Rep
    edited May 17

    @JosephF said: Who consider HE to be a T2?

    Those who consider a T1 being able to reach every other network on the internet without purchasing transit.

    Thanked by 1yoursunny
  • stefemanstefeman Member

    Its just hearsay still but..

    Apparently its drama related to the upcoming RIPE meeting where arguments are made for and against taxing/pricing members based on subnet sizes.

  • adlyadly Veteran

    @breached said:

    @sh97 said: https://x.com/bgptools/status/1791470879697752258

    On the reddit post, this is 'parentally the email they sent out to customers, which implies that Cogent used the SAME template as the depeering with NTT. I thought this was a copypasta at first, but turns out it's not.

    Oof.

    Not surprising they have the whole process templated - it's a regular occurrence for them now.

  • MaouniqueMaounique Host Rep, Veteran

    @stefeman said: Apparently its drama related to the upcoming RIPE meeting where arguments are made for and against taxing/pricing members based on subnet sizes.

    I don't think so, given the history of peering in India and some other places in Asia.
    That being said, Cogent is almost certainly not blameless, given how they offer bulk traffic between cogent peered locations, becoming an island is probably not something that is happening to them, but might be in the cards for some reason I am unable to figure out atm.

  • DediRockDediRock Member, Patron Provider

    @stefeman said:
    Its just hearsay still but..

    Apparently its drama related to the upcoming RIPE meeting where arguments are made for and against taxing/pricing members based on subnet sizes.

    Very interesting

Sign In or Register to comment.