trace from behind tata noam

a host in as4128, 198.180.152.15, is having problems getting to stuff
behind as6453 (tata). so i try to get an atlas traceroute toward
198.180.152.15 from as6453. but atlas whines

    Probes selection: Your selected ASN is not covered by our network

so not even one measly probe.

if anyone here is 'behind' 6453 en route 198.180.152.15, can you send
a trace, please?

thanks.

randy

Rather than letting ATLAS whine, everyone should become an ATLAS ambassador so as to increase the spread of ATLAS probes to exactly those ASNs which are under-represented:
https://atlas.ripe.net/get-involved/become-a-ripe-atlas-ambassador/

-Hank

They have a looking-glass : http://lg.as6453.net/lg/
which says :

Router: gin-pv0-thar1
Site: FR, Paris, PV0
Command: traceroute inet4 198.180.152.15 as-number-lookup

traceroute to 198.180.152.15 (198.180.152.15), 30 hops max, 52 byte packets
1 if-ae-6-4.tcore1.pg1-paris.as6453.net (80.231.111.25) 1.258 ms 1.726 ms 1.712 ms
     MPLS Label=334414 CoS=0 TTL=1 S=1
2 if-ae-7-2.tcore1.pvu-paris.as6453.net (80.231.111.6) 1.703 ms 1.516 ms if-ae-7-2.tcore1.pvu-paris.as6453.net (80.231.111.2) 1.360 ms
3 if-ae-11-2.tcore1.pvu-paris.as6453.net (80.231.153.49) 1.266 ms ae-7.r04.parsfr01.fr.bb.gin.ntt.net (129.250.8.1) [AS 2914] 1.126 ms if-ae-11-2.tcore1.pvu-paris.as6453.net (80.231.153.49) 1.246 ms
4 ae-23.r24.amstnl02.nl.bb.gin.ntt.net (129.250.4.137) [AS 2914] 16.599 ms 20.124 ms 13.608 ms
     MPLS Label=304689 CoS=0 TTL=1 S=1
5 ae-3.r25.amstnl02.nl.bb.gin.ntt.net (129.250.4.69) [AS 2914] 13.669 ms 13.672 ms 14.638 ms
     MPLS Label=434000 CoS=0 TTL=1 S=0
     MPLS Label=531024 CoS=0 TTL=1 S=1
6 ae-5.r23.asbnva02.us.bb.gin.ntt.net (129.250.6.162) [AS 2914] 86.304 ms 86.438 ms 101.443 ms
     MPLS Label=309569 CoS=0 TTL=1 S=0
     MPLS Label=531024 CoS=0 TTL=2 S=1
7 ae-0.r22.asbnva02.us.bb.gin.ntt.net (129.250.3.84) [AS 2914] 98.043 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net (129.250.6.162) [AS 2914] 115.804 ms ae-0.r22.asbnva02.us.bb.gin.ntt.net (129.250.3.84) [AS 2914] 91.169 ms
     MPLS Label=379041 CoS=0 TTL=1 S=0
     MPLS Label=531024 CoS=0 TTL=3 S=1
8 ae-0.r22.asbnva02.us.bb.gin.ntt.net (129.250.3.84) [AS 2914] 89.571 ms ae-6.r22.dllstx09.us.bb.gin.ntt.net (129.250.5.12) [AS 2914] 124.242 ms 130.316 ms
     MPLS Label=531024 CoS=0 TTL=1 S=1
9 ae-2.r11.dllstx09.us.bb.gin.ntt.net (129.250.5.14) [AS 2914] 130.781 ms 119.661 ms 132.269 ms
10 ae-2.r11.dllstx09.us.bb.gin.ntt.net (129.250.5.14) [AS 2914] 122.000 ms ge-102-0-0-29-53.r11.dllstx09.us.ce.gin.ntt.net (157.238.224.206) [AS 2914] 128.046 ms ae-2.r11.dllstx09.us.bb.gin.ntt.net (129.250.5.14) [AS 2914] 130.434 ms
11 netsrv.dfw.rg.net (198.180.152.15) [AS 4128] 129.176 ms 121.615 ms ge-102-0-0-29-53.r11.dllstx09.us.ce.gin.ntt.net (157.238.224.206) [AS 2914] 126.358 ms

{master}

Very similar results (going to NTT in very few hops) from their 2 NYC routers.

thanks all. now i have too much data and not enough insight

randy