I have shared about this leak with known contacts in their NOC.
Thanks.
On Fri, Nov 16, 2018 at 4:05 AM Tom Beecher wrote:
> I don't know what's less surprising, Tata making sure you see the entire
> internet (wink wink), or Airtel leaking routes... :)
>
> On Thu, Nov 15, 2018 at 4:13 PM
Airtel has acknowledged and is in the process of reverting. Thanks all for
your input.
-Marcus
From: Tom Beecher
Sent: Thursday, November 15, 2018 5:34 PM
To: pratik.lo...@charter.com
Cc: Marcus Josephson ; morrowc.li...@gmail.com;
stillwa...@gmail.com; NANOG
Subject: Re: Tata Scenic
I don't know what's less surprising, Tata making sure you see the entire
internet (wink wink), or Airtel leaking routes... :)
On Thu, Nov 15, 2018 at 4:13 PM Lotia, Pratik M
wrote:
> 9498/Airtel seems to be leaking a lot of routes.
>
>
>
> Source: https://bgpstream.com/
>
>
>
> All Events for
9498/Airtel seems to be leaking a lot of routes.
Source: https://bgpstream.com/
All Events for BGP Stream.
Event type
Country
ASN
Start time (UTC)
End time (UTC)
More info
BGP Leak
Origin AS: Etisalat Lanka (Pvt) Ltd. (AS 17470)
Leaker AS: BHARTI Airtel Ltd. (AS 9498)
2018-11-15 19:41:26
I have tried to reach out to Airtel, no response yet, but yah I could see my
issue being due to them leaking routes.
-Marcus
From: NANOG On Behalf Of Christopher Morrow
Sent: Thursday, November 15, 2018 3:30 PM
To: stillwa...@gmail.com
Cc: nanog list
Subject: Re: Tata Scenic routing in LAX
On Thu, Nov 15, 2018 at 3:21 PM Michael Still wrote:
> FYI 29791 isn't the only origin I'm seeing this on from one point of view:
> AS path: 3257 6453 9498 4637
> AS path: 3257 6453 9498 4637 10310 26085 14210
> AS path: 3257 6453
FYI 29791 isn't the only origin I'm seeing this on from one point of view:
AS path: 3257 6453 9498 4637
AS path: 3257 6453 9498 4637 10310 26085 14210
AS path: 3257 6453 9498 4637 20773 29066
AS path: 3257 6453
Marcus,
From route-views output, it looks like AS9498/airtel is probably
leaking your route between two of its upstreams (AS6453/Tata and
AS4637/Telstra) overseas, funneling some of your traffic through their
router.
route-views>sh ip bgp 23.92.178.22 | i 9498
3356 6453 9498 4637 29791
From East Coast:
root@dns1:~# traceroute 23.92.178.22
traceroute to 23.92.178.22 (23.92.178.22), 30 hops max, 60 byte packets
1 gw-128-254.phlapalo.quonix.net (208.82.128.254) 0.657 ms 0.657
ms 0.651 ms
2 te0-0-2-3.nr11.b002999-2.phl01.atlas.cogentco.com (38.104.111.121)
1.057 ms
Hey there!
In our environment we generally have ASR-1000X-2s everywhere peering via
iBGP/eBGP. These routers have no redundant RPs, hence cannot keep
forwarding traffic while the router reboots or crashes. As such, this is a
clear example of a router that's only NSF-aware (or
That's quite the tour...
>From Montreal, QC
traceroute to 23.92.178.22 (23.92.178.22), 30 hops max, 60 byte packets
1 67-221-x-x.ebox.net (67.221.x.x) 0.459 ms 0.431 ms 0.409 ms
2 ix-ae-10-190.tcore1.mtt-montreal.as6453.net (206.82.135.105) 5.637 ms 5.619
ms 5.588 ms
3
Anyone else seeing an odd Scenic routing in the LAX/SJE area for tata.
traceroute to 23.92.178.22 (23.92.178.22), 30 hops max, 52 byte packets
1 if-ae-13-2.tcore2.lvw-los-angeles.as6453.net (64.86.252.34) 180.698 ms
180.610 ms 181.712 ms
MPLS Label=344269 CoS=0 TTL=1 S=1
2
On 15 November 2018 01:51:28 GMT, Baldur Norddahl
wrote:
>Also not true that the management network is the last thing to boot. In
>contrary, everything else depends on that being ready first. And that
>would
>also be true if we used is-is.
It is when you out management in a VRF...
>ons. 14.
13 matches
Mail list logo
