AS202146 Alpaky A.R.C. Rete 101 S.r.l.

IPv6 prefix announced, but nothing inside is responding yet. AS202146 announces 1 IPv6 prefix(es) to the global routing table - that’s the part that BGP and our route-server scrape confirm. But our active discovery (curated hostnames, holder-derived domains, authoritative DNS NS/SOA/MX, certificate-transparency hostnames, RIPE Atlas, RDAP, IPv6 Hitlist) found no ICMPv6-responsive host inside the prefix on either vantage, and a yarrp pass against random addresses inside the prefix produced zero in-prefix hops (no router on the path through the AS replied with Time-Exceeded for any random target). That combination usually means the announcement is configured but the addresses inside aren’t in active use yet. The BGP route is there; the operational deployment is still ahead.

AS overview

Test target: 2a04:c500::1 · (no live host found) · address space: PA · prefixes announced: 1

prefix(es): 2a04:c500::/29

RPKI & ASPA

1 of 1 prefix(es) covered by a valid ROA.

Prefix	RPKI state	Reason	Covering VRP(s)
`2a04:c500::/29`	✓ valid	matched VRP (correct origin, length within maxLength)	AS202146 /29 maxLen 29 (ripe)

Random-IP probe (yarrp) into the AS' prefixes

We probed 15 arbitrary IPv6 address(es) inside AS202146's announced prefix(es). No router inside the prefix responded. The deepest visible hop was 2001:470:0:4d4::2 at hop 8 - that router answers ICMPv6 Echo. This is not in AS202146's announced prefix; operationally it's the AS-edge / peering interface (often on an IXP peering address or an upstream's /127 link). The traceroute boundary is the AS edge: ICMPv6 Time-Exceeded responses from anything inside this AS are filtered.

ICMPv6 Type 2 (Packet Too Big) acceptance - active test

Type 2 active test inconclusive: no Echo Reply to 1300-byte probe.
method: ICMPv6 Echo + forged PTB, tested 2026-05-25T12:33:00Z

Failure detail — what to grep in your logs

vantage	our source	your target	method	result	tested (UTC)
go6lab	`2a00:8642:42::75`	`2a04:c500::1`	`icmp6-echo`	no_echo	2026-05-25T12:33:00Z
karsolink	`2a12:d8c0:105a:9001::a154`	`2a04:c500::1`	`icmp6-echo`	no_echo	2026-05-25T12:41:17Z
odin	`2607:fae0:a000::42`	`2a04:c500::1`	`icmp6-echo`	no_echo	2026-05-25T12:32:43Z

Attempt log (go6lab):

icmp6-echo → no_echo: no Echo Reply to 1300-byte probe
dns-tcp → no_tcp: connect failed: timed out
tls → no_tcp: TLS connect failed
http → no_tcp: tcp/80 not open

Attempt log (karsolink):

icmp6-echo → no_echo: no Echo Reply to 1300-byte probe
dns-tcp → no_tcp: connect failed: timed out
tls → no_tcp: TLS connect failed
http → no_tcp: tcp/80 not open

Attempt log (odin):

icmp6-echo → no_echo: no Echo Reply to 1300-byte probe
dns-tcp → no_tcp: connect failed: timed out
tls → no_tcp: TLS connect failed
http → no_tcp: tcp/80 not open

To match the corresponding ICMPv6 packet on your side (host firewall, AS edge, or transit tap), look for our PTBs around the timestamps above:

sudo tcpdump -i any -n -e 'icmp6 and ip6[40] = 2 and (src host 2607:fae0:a000::42 or src host 2a00:8642:42::75 or src host 2a12:d8c0:105a:9001::a154)'

If you see our PTBs arriving but the destination's TCP/Echo flow does not shrink, the drop is in the destination kernel (cause 3 below). If you don't see them at all, drop is upstream of you (cause 2). If you only see them from one of our two source IPs, the drop is path-asymmetric — one transit on the asymmetric route is filtering, the other is not.

From NL host (go6lab) transit only unreachable

filter likely at: no path · min PMTU on path: 1500

0/4

Echo small (56B) -

0/4

Echo 1500B (DF) -

Type 1 dest-unreach

TCP responds on

Path (traceroute + mtr + PTR)

#	IP / PTR	RTT	mtr loss	AS	AS holder
1	2a00:8642:42::3	1.2ms	0%	AS203993	STEFFANN-DC-AS - S.J.M. Steffann, NL
2	*	-	0%*	-
3	*	-	-	-
4	2a01:a620:2:1	29.6ms	0%	-
5	*	-	-	-
6	*	-	-	-
7	*	-	-	-
8	*	-	-	-
9	*	-	-	-
10	*	-	-	-
11	*	-	-	-
12	*	-	-	-
13	*	-	-	-
14	*	-	-	-
15	*	-	-	-
16	*	-	-	-
17	*	-	-	-
18	*	-	-	-
19	*	-	-	-
20	*	-	-	-
21	*	-	-	-
22	*	-	-	-
23	*	-	-	-
24	*	-	-	-

tracepath -6

 1?: [LOCALHOST]                        0.034ms pmtu 1500
 1:  2a00:8642:42::3                                       1.379ms 
 1:  2a00:8642:42::3                                       1.870ms 
 2:  gw.friends.steffann.nl                                2.358ms 
 3:  no reply
 4:  2a01:a620:2:1::                                      30.865ms asymm 15 
 5:  no reply
 6:  no reply
 7:  no reply
 8:  no reply
 9:  no reply
10:  no reply
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500

From ITA host (Karsolink) transit only unreachable

filter likely at: no path · min PMTU on path: 1500

0/4

Echo small (56B) -

0/4

Echo 1500B (DF) -

Type 1 dest-unreach

TCP responds on

Path (traceroute + mtr + PTR)

#	IP / PTR	RTT	mtr loss	AS	AS holder
1	karsolink-01.net.karsolink.com 2a12:d8c0:105a:9001::1	0.3ms	0%*	AS204471	KARSOLINK - 2S Computers SRL, IT
2	2a12:d8c0:109f:121::a1	0.4ms	0%*	AS204471	KARSOLINK - 2S Computers SRL, IT
3	2a12:d8c0:101f:6::1	10.0ms	40%	AS204471	KARSOLINK - 2S Computers SRL, IT
4	warian.minap.it 2001:7f8:c5::a505:6911:1	9.2ms	0%	AS56911	Warian s.r.l.
5	2a01:a620:2:1	17.8ms	0%	-
6	*	-	-	-
7	*	-	-	-
8	*	-	-	-
9	*	-	-	-
10	*	-	-	-
11	*	-	-	-
12	*	-	-	-
13	*	-	-	-
14	*	-	-	-
15	*	-	-	-
16	*	-	-	-
17	*	-	-	-
18	*	-	-	-
19	*	-	-	-
20	*	-	-	-
21	*	-	-	-
22	*	-	-	-
23	*	-	-	-
24	*	-	-	-

Rate-limited ICMPv6: hop 3 (loss between 5% and 95% across mtr cycles - the router replies but only sometimes).

tracepath -6

 1?: [LOCALHOST]                        0.032ms pmtu 1500
 1:  no reply
 2:  no reply
 3:  2a12:d8c0:101f:6::1                                  10.930ms 
 4:  warian.minap.it                                       9.752ms asymm  6 
 5:  2a01:a620:2:1::                                      18.383ms asymm  7 
 6:  no reply
 7:  no reply
 8:  no reply
 9:  no reply
10:  no reply
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500

From SLO host (6connect) transit only unreachable

filter likely at: past AS6939 (HURRICANE) · min PMTU on path: 1500

0/4

Echo small (56B) -

0/4

Echo 1500B (DF) -

Type 1 dest-unreach

TCP responds on

Path (traceroute + mtr + PTR)

#	IP / PTR	RTT	mtr loss	AS	AS holder
1	fw1-lju.6connect.com 2607:fae0:a000::2	0.2ms	0%*	AS8038	6CONNECT - 6connect, Inc., US
2	*	-	-	-
3	*	-	30%	-
4	e0-1.core1.lju1.he.net 2001:470:1:5be::1	2.3ms	50%	AS6939	HURRICANE - Hurricane Electric LLC, US
5	*	-	-	-
6	port-channel1.core1.zag2.he.net 2001:470:0:2ea::2	4.3ms	50%	AS6939	HURRICANE - Hurricane Electric LLC, US
7	*	-	-	-
8	e0-36.core2.rom1.he.net 2001:470:0:4d4::2	21.3ms	0%	AS6939	HURRICANE - Hurricane Electric LLC, US
9	*	-	-	-
10	*	-	-	-
11	*	-	-	-
12	*	-	-	-
13	*	-	-	-
14	*	-	-	-
15	*	-	-	-
16	*	-	-	-
17	*	-	-	-
18	*	-	-	-
19	*	-	-	-
20	*	-	-	-
21	*	-	-	-
22	*	-	-	-
23	*	-	-	-
24	*	-	-	-

Rate-limited ICMPv6: hop 3, hop 4, hop 6 (loss between 5% and 95% across mtr cycles - the router replies but only sometimes).

tracepath -6

 1?: [LOCALHOST]                        0.032ms pmtu 1500
 1:  fw1-lju.6connect.com                                  1.569ms 
 1:  fw1-lju.6connect.com                                  0.559ms 
 2:  no reply
 3:  2a03:a100:0:201:1::1                                  0.731ms 
 4:  e0-1.core1.lju1.he.net                                4.000ms 
 5:  no reply
 6:  port-channel1.core1.zag2.he.net                       4.209ms 
 7:  no reply
 8:  e0-36.core2.rom1.he.net                              21.038ms 
 9:  no reply
10:  no reply
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500