Issues with prefix / help needed

Sat Mar 25 14:41:16 UTC 2023

yeah i see what you mean by, it doesn't work, then it starts working...

i traced to it, and it wasn't responding at first, then later it worked

C:\>tracert -w 1 86.104.228.1

Tracing route to 86.104.228.1 over a maximum of 30 hops

...

   9   118 ms     *      119 ms prs-bb1-link.ip.twelve99.net 
[62.115.112.243]
  10   125 ms   124 ms   126 ms  ffm-bb1-link.ip.twelve99.net 
[62.115.123.12]
  11     *        *        *     Request timed out.
  12     *        *        *     Request timed out.
  13   133 ms   133 ms   133 ms 
ipmax-ic340750-zch-b2.ip.twelve99-cust.net [62.115.168.201]
  14   130 ms     *      130 ms  po5.er01.zrh56.ch.ip-max.net [46.20.254.13]
  15   128 ms   129 ms   129 ms three-fourteen.cust.zrh56.ch.ip-max.net 
[46.20.240.71]
  16     *        *        *     Request timed out.
  17     *        *        *     Request timed out.
  18     *        *        *     Request timed out.
  19     *        *        *     Request timed out.
  20     *        *        *     Request timed out.
  21     *        *        *     Request timed out.
  22     *        *        *     Request timed out.
  23     *        *        *     Request timed out.
  24     *        *        *     Request timed out.
  25     *        *        *     Request timed out.
  26     *        *        *     Request timed out.
  27     *        *        *     Request timed out.
  28     *        *        *     Request timed out.
  29     *        *        *     Request timed out.
  30     *        *        *     Request timed out.

Trace complete.

C:\>tracert -w 1 86.104.228.1

Tracing route to 86.104.228.1 over a maximum of 30 hops

...

   9   119 ms   118 ms   118 ms prs-bb1-link.ip.twelve99.net 
[62.115.112.243]
  10     *      125 ms   124 ms  ffm-bb1-link.ip.twelve99.net 
[62.115.123.12]
  11     *        *        *     Request timed out.
  12     *        *        *     Request timed out.
  13   132 ms   132 ms   133 ms 
ipmax-ic340750-zch-b2.ip.twelve99-cust.net [62.115.168.201]
  14   129 ms     *      129 ms  po5.er01.zrh56.ch.ip-max.net [46.20.254.13]
  15   129 ms   129 ms   129 ms three-fourteen.cust.zrh56.ch.ip-max.net 
[46.20.240.71]
  16   129 ms     *      129 ms  86.104.228.1

Trace complete.

C:\>

On 3/25/2023 3:54 AM, ic 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
>
-- 
-Aaron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20230325/ed66cd8e/attachment.html>