<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font size="2" face="Courier New">yeah i see what you mean by, it
doesn't work, then it starts working...</font></p>
<p><font size="2" face="Courier New"><br>
</font></p>
<p><font size="2" face="Courier New">i traced to it, and it wasn't
responding at first, then later it worked<br>
</font></p>
<p><font size="2" face="Courier New"><br>
</font></p>
<p><font size="2" face="Courier New">C:\>tracert -w 1
86.104.228.1<br>
<br>
Tracing route to 86.104.228.1 over a maximum of 30 hops<br>
<br>
...</font></p>
<p><font size="2" face="Courier New"> 9 118 ms * 119 ms
prs-bb1-link.ip.twelve99.net [62.115.112.243]<br>
10 125 ms 124 ms 126 ms ffm-bb1-link.ip.twelve99.net
[62.115.123.12]<br>
11 * * * Request timed out.<br>
12 * * * Request timed out.<br>
13 133 ms 133 ms 133 ms
ipmax-ic340750-zch-b2.ip.twelve99-cust.net [62.115.168.201]<br>
14 130 ms * 130 ms po5.er01.zrh56.ch.ip-max.net
[46.20.254.13]<br>
15 128 ms 129 ms 129 ms
three-fourteen.cust.zrh56.ch.ip-max.net [46.20.240.71]<br>
16 * * * Request timed out.<br>
17 * * * Request timed out.<br>
18 * * * Request timed out.<br>
19 * * * Request timed out.<br>
20 * * * Request timed out.<br>
21 * * * Request timed out.<br>
22 * * * Request timed out.<br>
23 * * * Request timed out.<br>
24 * * * Request timed out.<br>
25 * * * Request timed out.<br>
26 * * * Request timed out.<br>
27 * * * Request timed out.<br>
28 * * * Request timed out.<br>
29 * * * Request timed out.<br>
30 * * * Request timed out.<br>
<br>
Trace complete.<br>
<br>
</font></p>
<p><font size="2" face="Courier New">C:\>tracert -w 1
86.104.228.1<br>
<br>
Tracing route to 86.104.228.1 over a maximum of 30 hops<br>
<br>
...</font></p>
<p><font size="2" face="Courier New"> 9 119 ms 118 ms 118 ms
prs-bb1-link.ip.twelve99.net [62.115.112.243]<br>
10 * 125 ms 124 ms ffm-bb1-link.ip.twelve99.net
[62.115.123.12]<br>
11 * * * Request timed out.<br>
12 * * * Request timed out.<br>
13 132 ms 132 ms 133 ms
ipmax-ic340750-zch-b2.ip.twelve99-cust.net [62.115.168.201]<br>
14 129 ms * 129 ms po5.er01.zrh56.ch.ip-max.net
[46.20.254.13]<br>
15 129 ms 129 ms 129 ms
three-fourteen.cust.zrh56.ch.ip-max.net [46.20.240.71]<br>
16 129 ms * 129 ms 86.104.228.1<br>
<br>
Trace complete.<br>
<br>
C:\><br>
</font></p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 3/25/2023 3:54 AM, ic wrote:<br>
</div>
<blockquote type="cite"
cite="mid:65FD55A8-53F2-47FB-958D-64328F91F8F6@benappy.com">
<pre class="moz-quote-pre" wrap="">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
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
-Aaron</pre>
</body>
</html>