CreekYing

He, my VPS it had same problem last month!!! Caramba!!!

My provider it filtered my prefix more fast than the ROA he propagated, nossa!!! Not funny when he happens at 3am

I think he is timing bug too, my ROA was new but valid

But how much RAM

Fika after outage is good idea lah, no blame culture better

Previous holder sounds likely, check RIPE history

Following this thread closely. I have a side project on Vultr's v6-only in Silicon Valley and the Cloudflare v4 frontend covers 99% of users. The 1% are bots and old curl versions, which I can live with.

CreekYing. I read TOS for ying and yang. Balance. What I give, what they take. Kidding. I don't read.

But I appreciate this thread existing. When something goes wrong, I search "providername TOS problem" and find threads like this. Collective intelligence > individual reading.

The forum is my TOS....

GRE. 47 Gbps attack last Tuesday, scrubbing center handled it. GRE over IPsec for control plane, plain GRE for data. Anycast at two PoPs, no single point of failure. Filtering at L3/L4/L7.

Four-participant IX is common in Asia-Pacific for regional learning. I started with similar in 2019. The operational experience is valuable even if volume is small.

Congratulations. Manual bilaterals teach you more about filtering than any route server.

I dont think 3ms matters for gaming honestly

Same here on the no support. I had a $6/year box, panel broke, no reply for 3 months. Learned my lesson.