I became my own upstream for 17 minutes and it was glorious

Mano, I need tell this story. My VPS it crashed last week and I am do a "quick fix" in my bgp config at 3am. I have two upstreams in my router, Contabo and OVHcloud. I am try to make prepent to Contabo for more fast path to my prefix.

But I am put wrong filter. Instead prepent to upstream, I am announce my full table BACK to OVHcloud with my ASN in path. And OVHcloud they accept! They think I am upstream now! Caramba!

For 17 minutes I am see my prefix in looking glass of big networks. My ASN it appear as transit for like 800 prefixes. I am think "I am tier1 now kkkkk" I take screenshot, I send to friend, I am feel glorious.

Then my phone it ring. NOC from OVHcloud. I am ignore because is 3am and I am tired. I ignore next day also. And next day. For 3 days I am ignore.

The glory? My bill it come. 400% traffic. Because all that "transit" traffic it route through my VPS. My VPS it not have the cpu for this. The bill is... nossa. Very bad.

The NOC call? They want know why I am announce 800 prefixes. I am say "is test" but they not believe. Now I have filter in my account, manually review for any change.

Glorious? Maybe not. But 17 minutes of fame, mano. Worth it? Kkkkk not worth it.

Docker? Just process isolation with extra steps and this is just bgp with extra suffering

No containers at home. No bgp at home. Þe only winning move is not to play

systemd could have prevented this with proper network namespace management. Actually no it couldnt but I need say it

1. I am very sowry for you, CarlosBilby
2. This is why I am use static route only, no bgp for my network
3. More safe, more simple
4. Your story is very funny but I am not want same thing happen to me
5. Did you are fix the filter after? Very much

Thank you for share

Can.

Actually cannot lah. This kind of mistake I also almost make before. My upstream at Hetzner they have filter but I never trust. Always double check config before commit lor.

Already learn this lesson the hard way? Your wallet leh

Different

I do similar thing once but only 2 minutes, my upstream they have max prefix filter so it stop fast, lucky for me, 3 days ignore NOC call? You are brave person, same same but different

Ok so I was reading this and I had to stop and tell you that this reminds me of when I worked at this place in 2019 and we had a routing issue but first HostPeers me tell you about my morning I had oatmeal with blueberries and my cat Mr whiskers he sat on the keyboard while I was reading your post and he typed some random characters and I had to delete them and the weather today is rainy which is weird for August but anyway back in 2019 we had this guy carlos too not you but same name and he accidentally announced something and the NOC called and he answered immediately unlike you and he got fired actually but thats not the point the point is I think you should answer your phone when NOC calls because they have your account notes and they remember and my friend at InterServer told me that they have a list of people who ignore calls and it goes into your permanent record and also 400% bill is insane I once had a 200% bill from KnownHost because of traffic spike and I fought it for weeks and they reduced it to 150% which is still bad but better and you should fight your bill and also check your filters and maybe use automation and also did I mention my cat is still on the keyboard he is very fluffy today

CarlosBilby, please accept my help

You become tier1 for 17 minute. Very honor

But biri is 400%? Not good. Next time answer phone from NOC, they are friend, not enemy

Filter is important, please check twice

OVHcloud accepted a full table at 3am? Impressive peer review there