Re: [apops] Subject: Subject: Looking for TM.NET.MY Contact

  • To: Jim Jagielski <jim at jagunet dot com>
  • Subject: Re: [apops] Subject: Subject: Looking for TM.NET.MY Contact
  • From: amzariaz at tm dot net dot my
  • Date: Wed, 17 Aug 2005 11:07:03 +0800
  • Cc: apops at apops dot net
  • List-archive: <http://www.apnic.net/mailing-lists/apops>
  • List-help: <mailto:apops-request@apops.net?subject=help>
  • List-id: Asia Pacific Operators Forum <apops.apops.net>
  • List-post: <mailto:apops@apops.net>
  • List-subscribe: <http://mailman.apnic.net/mailman/listinfo/apops>, <mailto:apops-request@apops.net?subject=subscribe>
  • List-unsubscribe: <http://mailman.apnic.net/mailman/listinfo/apops>, <mailto:apops-request@apops.net?subject=unsubscribe>
  • Priority: normal
    • 
      TM.NET.MY can be contacted at ipno at tmnet dot com dot my and routing at tm dot net dot my
      
      >From what I have found, we are not advertising your/bogus routes to equinix-peers. Only local customers are advertised to our peering partners.
      We will check with this partner if they have been defaulting to us by any chance.
      
      Regards,
      Amzari
      routing at tm dot net dot my
      
      
      ----- Original Message -----
      From: Jim Jagielski <jim at jagunet dot com>
      Date: Wednesday, August 17, 2005 9:14 am
      Subject: [apops] Subject: Subject: Looking for TM.NET.MY Contact
      
      > Since they peer with others at Equinix, I am looking for someone from
      > tm.net.my to contact me. They are advertising bogus routes for my 
      > ip  
      > space
      > (209.133.192.0/19), causing traffic which passes through Equinix 
      > to  
      > (a lot of
      > the time) get diverted to their network and drop and die when the
      > packets hit their AT&T connection. Also, all packets within their
      > large IP allocation is also misdirected and dropped: EG:
      > 
      >   8  a1-00-00-00.p0.lax91.adelphiacom.net (66.109.3.130)  58.736 ms
      >       58.770 ms  58.804 ms
      >   9  LAX-GE1.tm.net.my (206.223.123.94)  58.727 ms  58.603 ms   
      > 58.737 ms
      >   10  219.93.168.233 (219.93.168.233)  283.962 ms  284.899 ms   
      > 284.316 ms
      >   11  vlan550-brf-sw03.tm.net.my (219.93.151.209)  284.225 ms  
      > 284.144        ms  284.773 ms
      >   12  219.93.174.145 (219.93.174.145)  284.491 ms  337.796 ms   
      > 378.834 ms
      >   13  210.187.142.5 (210.187.142.5)  284.120 ms 219.93.151.97
      >        (219.93.151.97)  285.450 ms 219.93.151.103 (219.93.151.103)
      >         284.776 ms
      >   14  210.187.15.254 (210.187.15.254)  285.943 ms 203.106.230.134
      >        (203.106.230.134)  286.894 ms 210.187.15.254 (210.187.1
      >         5.254)  288.102 ms
      >   15  202.188.126.132 (202.188.126.132)  286.384 ms  286.476 ms
      >         287.241 ms
      >   16  219.93.173.37 (219.93.173.37)  277.918 ms 219.93.173.133
      >       (219.93.173.133)  277.521 ms 219.93.173.37 (219.93.173.37)
      >       277.503 ms
      >   17  219.93.153.150 (219.93.153.150)  277.848 ms  277.295 ms   
      > 277.519 ms
      >   18  12.119.139.37 (12.119.139.37)  276.814 ms !X *  276.567 ms !X
      > 
      > 
      > When using http://www.myloca.net/cgi-bin/trace/index.pl, all AT&T
      > traffic appears to be misdirected as well.
      > 
      > --
      > =======================================================================
      >  Jim Jagielski   [|]   jim@jaguNET.com   [|]
      >    +1-410-420-0140  (Cell: +1-443-324-8390)
      > 
      > 
      > 
      > 
      > _______________________________________________
      > apops mailing list
      > apops at apops dot net
      > http://mailman.apnic.net/mailman/listinfo/apops
      > Website: www.apops.net
      >