[dns-operations] Routing loop in AS23033 for co.id - seems fishy

Seth Mattinen sethm at rollernet.us
Fri Apr 27 14:40:00 UTC 2018


On 4/27/18 3:28 AM, Stephane Bortzmeyer wrote:
> On Thu, Apr 26, 2018 at 08:24:34AM -0700,
>   Seth Mattinen<sethm at rollernet.us>  wrote
>   a message of 101 lines which said:
> 
>> Anyone happen to know if AS23033 Wowrack really supposed to be
>> announcing 103.19.177.0/24?
> May be:
> 
> % whois -h whois.radb.net 103.19.177.0/24
> route:      103.19.177.0/24
> descr:      Proxy route object #1808412
> origin:     AS23033
> mnt-by:     MAINT-AS23033
> changed:support at wowrack.com  20180403  #18:46:09Z
> source:     RADB
> 
> (Found thanks to the excellent "Prefix routing consistency" widget of
> RIPE Stat.)


It's working again. Got some direct responses overnight and this morning 
(in my timezone) those IPv4 prefixes are no longer being announced 
through AS23033. All four through AS23033 were looped, effectively 
causing a full outage from my perspective in the US, but I likely would 
have never known if I didn't have a customer using domains under .co.id.

IPv6 is still broken/looping, 2001:DF5:4000::/48 with path 7018 1299 
23033 132647.


~Seth



More information about the dns-operations mailing list