One more thing: it seems that no matter what, the prefix is always reachable from AS3257 which makes the whole thing even weirder.
> On 25 Mar 2023, at 09:54, ic <li...@benappy.com> wrote: > > Hi there, > > I’m contacting you because after spending 2 days troubleshooting I can’t seem > to find a solution to the following. > > We (AS45021) bought/transffered the 86.104.228.0/24 prefix a few months back > because we couldn’t wait longer on the RIPE waiting list. > > Before you ask, yes, AS45021 is currently single homed, this will change in a > week (it requires travelling a few hundred miles and I couldn’t do it before). > > Since we started announcing this prefix, things have been spotty, at best. > While it seems visible in all the looking glasses I tried, it spends > sometimes hours, sometimes days, being unreachable (you can try for ex. > 86.104.228.1 or 86.104.228.26). > > I have full access (up to packet capture) on the AS and its upstream. When I > ping one of the IPs from various ISPs, I see the ICMP Echo Request and Reply > on the wire, going where it’s supposed to go, but it doesn’t reach the > pinging host. Pinging any IP of the upstream (AS42275 / 85.208.69.0/24 in > this location) works. > > ROAs and RPKI seem fine to me. > > I’m starting to suspect that maybe the previous user of the prefix is still > announcing it somewhere and “shouting louder” than me. It seems when I clear > sessions, it immediately works for a while, then stops. > > Do you all have any idea what I should check / try next? > > BR, Michel >
