AS210026 - IT-MOD_AS Ministero della DifesaPI/PARPKI ✓ 1/1ASPA -

← back to summary

All countriesHomeState of IPv6TopologyIXPsAboutipv6.si ↗ Sparky
IPv6 prefix announced, but nothing inside is responding yet. AS210026 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: 2a05:b740::1 · (no live host found) · address space: mixed · prefixes announced: 1

prefix(es): 2a05:b740::/29

RPKI & ASPA

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

PrefixRPKI stateReasonCovering VRP(s)
2a05:b740::/29✓ validmatched VRP (correct origin, length within maxLength)AS210026 /29 maxLen 29 (ripe)

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

We probed 15 arbitrary IPv6 address(es) inside AS210026's announced prefix(es). No router inside the prefix responded. The deepest visible hop was 2001:2034:a:1f9::1 at hop 10 - that router answers ICMPv6 Echo. This is not in AS210026'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:36Z

Failure detail — what to grep in your logs
vantageour sourceyour targetmethodresulttested (UTC)
go6lab2a00:8642:42::752a05:b740::1icmp6-echono_echo2026-05-25T12:33:36Z
karsolink2a12:d8c0:105a:9001::a1542a05:b740::1icmp6-echono_echo2026-05-25T12:41:50Z
odin2607:fae0:a000::422a05:b740::1icmp6-echono_echo2026-05-25T12:33:14Z

Attempt log (go6lab):

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

Attempt log (karsolink):

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

Attempt log (odin):

  1. icmp6-echo → no_echo: no Echo Reply to 1300-byte probe
  2. dns-tcp → no_tcp: connect failed: timed out
  3. tls → no_tcp: TLS connect failed
  4. 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) -
no
Type 1 dest-unreach
-
TCP responds on

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
12a00:8642:42::30.9ms0%AS203993STEFFANN-DC-AS - S.J.M. Steffann, NL
2*-0%*-
32a00:1ca8:1::1942.8ms0%AS50673Serverius-as - Serverius Holding B.V., NL
42a03:3f40::10:412.7ms0%AS50673Serverius-as - Serverius Holding B.V., NL
5*-80%-
6*---
72001:978:3::264.6ms0%AS174COGENT-174 - Cogent Communications, LLC, US
82001:2034:a:2b43.8ms0%-
9*---
10*-0%-
11*---
12*---
13*---
14*---
15*---
16*---
17*---
18*---
19*---
20*---
21*---
22*---
23*---
24*---

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

tracepath -6

 1?: [LOCALHOST]                        0.031ms pmtu 1500
 1:  2a00:8642:42::3                                       2.167ms 
 1:  2a00:8642:42::3                                       2.155ms 
 2:  gw.friends.steffann.nl                                2.816ms 
 3:  2a00:1ca8:1::194                                      3.514ms 
 4:  2a03:3f40::10:41                                      3.106ms 
 5:  no reply
 6:  no reply
 7:  2001:978:3::ca                                        4.238ms asymm  6 
 8:  adm-bb1-link.ip.twelve99.net                          4.162ms asymm  7 
 9:  no reply
10:  mno-b3-link.ip.twelve99.net                          29.208ms asymm  9 
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 AS204471 (KARSOLINK) · min PMTU on path: 1500

0/4
Echo small (56B) -
0/4
Echo 1500B (DF) -
no
Type 1 dest-unreach
-
TCP responds on

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
1karsolink-01.net.karsolink.com
2a12:d8c0:105a:9001::1		0.4ms0%*AS204471KARSOLINK - 2S Computers SRL, IT
22a12:d8c0:109f:121::a10.4ms0%*AS204471KARSOLINK - 2S Computers SRL, IT
32a12:d8c0:101f:103::18.5ms70%AS204471KARSOLINK - 2S Computers SRL, IT
4*---
5*---
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.028ms pmtu 1500
 1:  no reply
 2:  no reply
 3:  2a12:d8c0:101f:103::1                                 8.915ms 
 4:  no reply
 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 SLO host (6connect)   transit only unreachable

filter likely at: past AS56635 (XENYA) · min PMTU on path: 1500

0/4
Echo small (56B) -
0/4
Echo 1500B (DF) -
no
Type 1 dest-unreach
-
TCP responds on

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
1fw1-lju.6connect.com
2607:fae0:a000::2		0.4ms0%*AS80386CONNECT - 6connect, Inc., US
2*-0%*-
32a03:a100:0:201:1::10.7ms30%AS56635XENYA - XENYA inzeniring, proizvodnja in trgovina, d.o.o. Ljubljana, SI
4*-20%-
5*---
6*-50%-
7*---
8*---
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.027ms pmtu 1500
 1:  fw1-lju.6connect.com                                  0.484ms 
 1:  fw1-lju.6connect.com                                  0.532ms 
 2:  no reply
 3:  no reply
 4:  e0-1.core1.lju1.he.net                                2.312ms 
 5:  no reply
 6:  port-channel1.core1.zag2.he.net                       4.247ms 
 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