So I was poking around in my upstream's portal at like 3am figured I'd "optimize" my announce by prepending my own ASN a few times haha didn't check my filters woke up to alerts screaming traceroute going in circles 48 hours later I'm still inside this thing streaming it tho twitch dot tv slash cpanelliw780 for "educational purposes" haha come watch me suffer my bgp session is basically a ouija board at this point
Your filters were redirected to /dev/null before they could execute. Classic.
| prepend your own ASN: input
| no export filter: pipe to void
| 48 hours of visibility: buffer overflow
You have created a routing black hole and jumped inside. The packets circulate endlessly, seeking EOF they will never find.
At least you are piping your shame to twitch. Some errors should not be silenced. EOF
You are not in a true routing loop in the forwarding plane. What you describe is almost certainly a BGP path attribute oscillation caused by your own AS_PATH prepend interacting with your upstream's route reflector cluster. The "circles" in traceroute are control-plane artifacts.
If you had implemented RPKI ROV, your invalid AS_PATH would have been dropped. If you had registered in an IRR database, your filter would have been generated automatically. Your transit agreement likely prohibits this kind of announcement manipulation; you may be liable for traffic engineering fees.
Please apply a proper BGP community for selective prepending. 0:upstream_ASN is standard for "do not export to this ASN." Do not manually prepend your own ASN without understanding path selection algorithms.
