AS199653 ARUBAFR-AS Aruba S.p.A.

IPv6 prefix announced, but nothing inside is responding yet. AS199653 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: 2a03:2c40::1 · (no live host found) · address space: PA · prefixes announced: 1

prefix(es): 2a03:2c40::/32

RPKI & ASPA

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

Prefix	RPKI state	Reason	Covering VRP(s)
`2a03:2c40::/32`	✓ valid	matched VRP (correct origin, length within maxLength)	AS199653 /32 maxLen 48 (ripe)

ASPA: this AS has published an ASPA record listing 4 upstream provider(s) that are authorized to propagate routes from it: AS174, AS1299, AS3356, AS19905. Routes from this AS that arrive via any other upstream are considered ASPA-invalid by validators that enforce ASPA.

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

We probed 15 arbitrary IPv6 address(es) inside AS199653's announced prefix(es). No router inside the prefix responded. The deepest visible hop was 2001:978:2:84::2:2 at hop 12 - that router does not answer ICMPv6 Echo. This is not in AS199653'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:32:06Z

Failure detail — what to grep in your logs

vantage	our source	your target	method	result	tested (UTC)
go6lab	`2a00:8642:42::75`	`2a03:2c40::1`	`icmp6-echo`	no_echo	2026-05-25T12:32:06Z
karsolink	`2a12:d8c0:105a:9001::a154`	`2a03:2c40::1`	`icmp6-echo`	no_echo	2026-05-25T12:40:24Z
odin	`2607:fae0:a000::42`	`2a03:2c40::1`	`icmp6-echo`	no_echo	2026-05-25T12:31:51Z

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: past AS174 (COGENT-174) · 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	0.7ms	0%	AS203993	STEFFANN-DC-AS - S.J.M. Steffann, NL
2	*	-	0%*	-
3	2a00:1ca8:1::194	3.4ms	0%	AS50673	Serverius-as - Serverius Holding B.V., NL
4	2a03:3f40::10:41	2.9ms	0%	AS50673	Serverius-as - Serverius Holding B.V., NL
5	*	-	-	-
6	*	-	-	-
7	*	-	-	-
8	be2922.rcr21.b032899-0.par01.atlas.cogentco.com 2001:550:0:1000::8275:1a2	14.2ms	10%	AS174	COGENT-174 - Cogent Communications, LLC, US
9	2001:978:2:84::2:2	78.9ms	0%	AS174	COGENT-174 - Cogent Communications, LLC, US
10	*	-	-	-
11	*	-	-	-
12	*	-	-	-
13	*	-	-	-
14	*	-	-	-
15	*	-	-	-
16	*	-	-	-
17	*	-	-	-
18	*	-	-	-
19	*	-	-	-
20	*	-	-	-
21	*	-	-	-
22	*	-	-	-
23	*	-	-	-
24	*	-	-	-

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

tracepath -6

 1?: [LOCALHOST]                        0.030ms pmtu 1500
 1:  2a00:8642:42::3                                       1.573ms 
 1:  2a00:8642:42::3                                       1.601ms 
 2:  gw.friends.steffann.nl                                2.351ms 
 3:  2a00:1ca8:1::194                                      2.727ms 
 4:  2a03:3f40::10:41                                      2.804ms 
 5:  2001:978:2:40::3:1                                    4.608ms 
 6:  no reply
 7:  be12265.ccr41.par01.atlas.cogentco.com               14.316ms 
 8:  be2922.rcr21.b032899-0.par01.atlas.cogentco.com      14.217ms 
 9:  2001:978:2:84::2:2                                   15.368ms 
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: past AS174 (COGENT-174) · 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	*	-	0%*	-
2	*	-	0%*	-
3	2a12:d8c0:101f:6::1	10.0ms	30%	AS204471	KARSOLINK - 2S Computers SRL, IT
4	2a03:b020:1:51::a	10.4ms	0%	AS41327	FIBERTELECOM-AS - Fiber Telecom S.p.A., IT
5	2a03:b020::246	10.1ms	0%	AS41327	FIBERTELECOM-AS - Fiber Telecom S.p.A., IT
6	2001:978:2:2a::e7:1	10.8ms	0%	AS174	COGENT-174 - Cogent Communications, LLC, US
7	be4823.agr61.mil02.atlas.cogentco.com 2001:550:0:1000::9a19:8c5	10.8ms	0%	AS174	COGENT-174 - Cogent Communications, LLC, US
8	port-channel4690.ccr92.mil02.atlas.cogentco.com 2001:550:0:1000::9a36:3f3e	10.4ms	0%	AS174	COGENT-174 - Cogent Communications, LLC, US
9	*	-	70%	-
10	*	-	-	-
11	be2921.rcr21.b032899-0.par01.atlas.cogentco.com 2001:550:0:1000::8275:22	30.6ms	0%	AS174	COGENT-174 - Cogent Communications, LLC, US
12	2001:978:2:84::2:2	31.4ms	0%	AS174	COGENT-174 - Cogent Communications, LLC, US
13	*	-	-	-
14	*	-	-	-
15	*	-	-	-
16	*	-	-	-
17	*	-	-	-
18	*	-	-	-
19	*	-	-	-
20	*	-	-	-
21	*	-	-	-
22	*	-	-	-
23	*	-	-	-
24	*	-	-	-

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

tracepath -6

 1?: [LOCALHOST]                        0.034ms pmtu 1500
 1:  karsolink-01.net.karsolink.com                        0.622ms 
 2:  no reply
 3:  2a12:d8c0:101f:6::1                                  10.361ms 
 4:  2a03:b020:1:51::a                                    11.281ms 
 5:  2a03:b020::246                                       10.965ms asymm  6 
 6:  2001:978:2:2a::e7:1                                  11.364ms asymm  7 
 7:  be4823.agr61.mil02.atlas.cogentco.com                11.353ms asymm  8 
 8:  port-channel3336.ccr92.mil02.atlas.cogentco.com      11.074ms asymm  9 
 9:  no reply
10:  be2780.ccr42.par01.atlas.cogentco.com                45.976ms asymm 11 
11:  be2922.rcr21.b032899-0.par01.atlas.cogentco.com      31.379ms asymm 12 
12:  2001:978:2:84::2:2                                   32.030ms asymm  8 
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 AS3356 (LEVEL3) · 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.3ms	0%*	AS8038	6CONNECT - 6connect, Inc., US
2	*	-	-	-
3	*	-	30%	-
4	2a00:ee0:1:15::2	0.9ms	0%	AS5603	SIOL-NET - Telekom Slovenije, d.d., SI
5	2001:1900:5:2:2:0:11c:d49	16.5ms	0%	AS3356	LEVEL3 - Level 3 Parent, LLC, US
6	*	-	0%	-
7	2001:1900:5:2:2::4f42	23.2ms	0%	AS3356	LEVEL3 - Level 3 Parent, LLC, US
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.029ms pmtu 1500
 1:  fw1-lju.6connect.com                                  0.593ms 
 1:  fw1-lju.6connect.com                                  0.403ms 
 2:  no reply
 3:  2a00:ee1:800:9::1                                     3.228ms 
 4:  2a00:ee0:1:10::2                                      1.124ms asymm  3 
 5:  2001:1900:5:2:2:0:11c:d49                             8.790ms asymm  7 
 6:  no reply
 7:  2001:1900:5:2:2::3c06                                26.964ms asymm  9 
 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