AS210144 - ZADEASRL ZADEA SRLPARPKI ✓ 1/1ASPA -

← back to summary

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

prefix(es): 2a0d:e800::/29

RPKI & ASPA

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

PrefixRPKI stateReasonCovering VRP(s)
2a0d:e800::/29✓ validmatched VRP (correct origin, length within maxLength)AS210144 /29 maxLen 29 (ripe)

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

We probed 15 arbitrary IPv6 address(es) inside AS210144's announced prefix(es). No router inside the prefix responded. The deepest visible hop was 2001:470:0:2ea::2 at hop 6 - that router answers ICMPv6 Echo. This is not in AS210144'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:36:46Z

Failure detail — what to grep in your logs
vantageour sourceyour targetmethodresulttested (UTC)
go6lab2a00:8642:42::752a0d:e800::1icmp6-echono_echo2026-05-25T12:36:46Z
karsolink2a12:d8c0:105a:9001::a1542a0d:e800::1icmp6-echono_echo2026-05-25T12:47:53Z
odin2607:fae0:a000::422a0d:e800::1icmp6-echono_echo2026-05-25T12:36:17Z

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: past AS12779 (ITGATE) · 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::31.7ms0%AS203993STEFFANN-DC-AS - S.J.M. Steffann, NL
2gw.friends.steffann.nl
2a00:8642:1000:f000::1		1.8ms0%*AS203993STEFFANN-DC-AS - S.J.M. Steffann, NL
3ccr2-ccr1.dc1.nogalliance.org
2a00:8642:dc1:2::b		1.8ms0%AS203993STEFFANN-DC-AS - S.J.M. Steffann, NL
4ams-ix.ipv6.itgate.net
2001:7f8:1::a501:2779:1		5.7ms0%-NA
5be11.Jolly-Jumper.MIL3.ipv6.ITgate.net
2001:1418:1::102		19.0ms0%AS12779ITGATE - IT.Gate S.p.A., IT
6*---
7*---
8*---
9*---
10*---
11*---
12*---
13*---
14*---
15*---
16*---
17*---
18*---
19*---
20*---
21*---
22*---
23*---
24*---

tracepath -6

 1?: [LOCALHOST]                        0.030ms pmtu 1500
 1:  2a00:8642:42::3                                       1.588ms 
 1:  2a00:8642:42::3                                       1.863ms 
 2:  no reply
 3:  ccr2-ccr1.dc1.nogalliance.org                         2.577ms asymm  2 
 4:  ams-ix.ipv6.itgate.net                                5.200ms asymm  3 
 5:  be11.Jolly-Jumper.MIL3.ipv6.ITgate.net               19.916ms 
 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: 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
1*-0%*-
2*-0%*-
32a12:d8c0:109f:106::a23.1ms0%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*---

tracepath -6

 1?: [LOCALHOST]                        0.031ms pmtu 1500
 1:  no reply
 2:  no reply
 3:  2a12:d8c0:109f:106::a2                                3.733ms 
 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 AS6939 (HURRICANE) · 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.5ms0%*AS80386CONNECT - 6connect, Inc., US
2*---
32a03:a100:0:201:1::1122.9ms50%AS56635XENYA - XENYA inzeniring, proizvodnja in trgovina, d.o.o. Ljubljana, SI
4e0-1.core1.lju1.he.net
2001:470:1:5be::1		122.9ms80%AS6939HURRICANE - Hurricane Electric LLC, US
5*---
6port-channel1.core1.zag2.he.net
2001:470:0:2ea::2		3.9ms0%AS6939HURRICANE - Hurricane Electric LLC, US
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 (loss between 5% and 95% across mtr cycles - the router replies but only sometimes).

tracepath -6

 1?: [LOCALHOST]                        0.023ms pmtu 1500
 1:  fw1-lju.6connect.com                                  0.563ms 
 1:  fw1-lju.6connect.com                                  0.460ms 
 2:  no reply
 3:  2a03:a100:0:201:1::1                                  0.999ms 
 4:  e0-1.core1.lju1.he.net                                4.952ms 
 5:  no reply
 6:  port-channel1.core1.zag2.he.net                       4.058ms 
 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