Earliar this afternoon, approx. 2:45pm est, a multihomed customer of ours introduced
thousands of routes to us as being behind them. Needless to say, this cause some major
routing instability. We immediately shut that connection and contacted the customer.
Yes it is true that we announced out incorrect routes through AGIS.
No, AGIS did not shut off the connection. I noticed
the problem within a few seconds,because I was on the offending router at
the time, and fixed the problem. My connection to AGIS
was not stopped until I reset it for the new filter some time later.
The only one of my connections to have this problem was AGIS. The problem
was caused by an internal routing protocol that decided it wanted to be
God.
I did not recieve a call from AGIS until over an hour after I had already
fixed the problem.
I have patched the broken filter on our routers so this won't happen
again.
We are in the process of switching from AS Path filters to prefix filters and this customer
was still on the AS Path filter.
No comment. I requested this when I turned up the connection.
Mark E Larson
Senior Engineer
The only one of my connections to have this problem was AGIS. The problem
was caused by an internal routing protocol that decided it wanted to be
God.
Thou shalt not redistribute into BGP sayeth the Lord... 
+------------------- H U R R I C A N E - E L E C T R I C -------------------+
You forgot the other commandment:
Thou shalt not redistribute BGP routes into any other routing protocol.