AS4788 Telecom Malaysia major route leak?

Fri Jun 12 10:05:16 UTC 2015

* Marty Strong via NANOG <nanog at nanog.org>

> It *looks* like GBLX stopped accepting the leak.

If so, it's a partial fix at best, I still see plenty of leaked routes,
both via 3356 and 3549, e.g.:

tore at cr1-osl3> show route 195.24.168.98 all 
Jun 12 12:03:54 +0200

inet.0: 544405 destinations, 1591203 routes (543086 active, 3 holddown, 526626 hidden)
+ = Active Route, - = Last Active, * = Both

195.24.160.0/19    *[BGP/170] 00:03:59, MED 2000, localpref 50, from 87.238.63.5
                      AS path: 3356 3549 4788 6939 39648 I, validation-state: unverified
                    > to 87.238.63.56 via ae0.0
                    [BGP/170] 00:05:24, MED 0, localpref 50, from 87.238.63.2
                      AS path: 3356 3549 4788 6939 39648 I, validation-state: unverified
                    > to 87.238.63.56 via ae0.0
                    [BGP ] 01:16:00, MED 25245, localpref 100
                      AS path: 3549 4788 6939 39648 I, validation-state: unverified
                    > to 64.210.69.85 via xe-1/1/0.0

It seems to have started around 08:47 UTC, that's when I got my first
alarm from ring-sqa at least.

Tore