AS overview
Test target: 2a14:7584:4100::1 · static prefix probe · address space: unknown · prefixes announced: 5
prefix(es): 2a14:7584:41ee::/48, 2a0d:b287:dd00::/40, 2a14:7584:4100::/40, 2a14:7584:4100::/48, 2a14:7584:44ce::/48
Targets & per-vantage-point probe results (1 target(s) across 3 vantage point(s))
Source codes (hover any badge for full description): CUR=curated · NS/SOA/MX=DNS records · SPF=SPF TXT · DRV=holder-derived (www, ns1, mail, gw, …) · ATL=RIPE Atlas · PDB=PeeringDB · WHOIS=RIPE whois · RDAP=RIPE RDAP · HIT=IPv6 Hitlist · RTR=in-prefix path hop (router) · PRB=static prefix probe · SYN=synthetic prefix::1 fallback
| Target IP / hostname | Source | NL host (go6lab) | ITA host (Karsolink) | SLO host (6connect) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ping | 1500B | :80 | :443 | reached | ping | 1500B | :80 | :443 | reached | ping | 1500B | :80 | :443 | reached | ||
2a14:7584:4100::1 | prb | ✓ | ✓ | ? | ? | ✓ | ✓ | ✓ | refused | refused | ✓ | ✓ | ✓ | refused | refused | ✓ |
RPKI & ASPA
1 of 5 prefix(es) covered by a valid ROA, 4 not-found.
| Prefix | RPKI state | Reason | Covering VRP(s) |
|---|---|---|---|
2a14:7584:41ee::/48 | - not-found | no covering VRP | |
2a0d:b287:dd00::/40 | ✓ valid | matched VRP (correct origin, length within maxLength) | AS216309 /40 maxLen 40 (ripe); AS41720 /29 maxLen 29 (ripe) |
2a14:7584:4100::/40 | - not-found | no covering VRP | |
2a14:7584:4100::/48 | - not-found | no covering VRP | |
2a14:7584:44ce::/48 | - not-found | no covering VRP |
Random-IP probe (yarrp) into the AS' prefixes
At least one router inside AS216309's announced prefix replied during the random-target probe. Hop(s): 2a14:7584:41ff:102::1, 2a14:7584:41ff:102::2, 2a14:7584:41ff::2. These are candidate targets for direct testing.
ICMPv6 Type 2 (Packet Too Big) acceptance - active test
Vantage points disagree about Type 2 acceptance - transit ASes on one path may be filtering Type 2 even though the destination's stack accepts it on another path:
- NL host (go6lab): Type 2 honored. Forged PTB accepted; next response shrunk. (ICMPv6 Echo + forged PTB)
- ITA host (Karsolink): inconclusive: no Echo Reply to 1300-byte probe. (ICMPv6 Echo + forged PTB)
- SLO host (6connect): Type 2 honored. Forged PTB accepted; next response shrunk. (ICMPv6 Echo + forged PTB)
Why they disagree - reachability mismatch: One vantage couldn't drive a flow at all to this destination (no Echo Reply or no responding TCP port), so the active test had no behavioural change to observe. The other vantage's verdict is the only meaningful one here.
Failure detail — what to grep in your logs
| vantage | our source | your target | method | result | tested (UTC) |
|---|---|---|---|---|---|
| go6lab | 2a00:8642:42::75 | 2a14:7584:4100::1 | icmp6-echo | honored | 2026-05-30T12:48:58Z |
| karsolink | 2a12:d8c0:105a:9001::a154 | 2a14:7584:4100::1 | icmp6-echo | no_echo | 2026-05-30T13:00:25Z |
| odin | 2607:fae0:a000::42 | 2a14:7584:4100::1 | icmp6-echo | honored | 2026-05-30T12:48:37Z |
Attempt log (go6lab):
icmp6-echo→ honored (size_before=1460, size_after=None)dns-tcp→ no_tcp: connect failed: timed outtls→ no_tcp: TLS connect failedhttp→ no_tcp: tcp/80 not open
Attempt log (karsolink):
icmp6-echo→ no_echo: no Echo Reply to 1300-byte probedns-tcp→ no_tcp: connect failed: [Errno 111] Connection refusedtls→ no_tcp: TLS connect failedhttp→ no_tcp: tcp/80 not open
Attempt log (odin):
icmp6-echo→ honored (size_before=1460, size_after=None)dns-tcp→ no_tcp: connect failed: [Errno 111] Connection refusedtls→ no_tcp: TLS connect failedhttp→ 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.
Where the path divergence is
Per-vantage probe + verdict (headline):
- go6lab: probe
icmp6-echo→ verdicthonored - karsolink: probe
icmp6-echo→ verdictno_echo - odin: probe
icmp6-echo→ verdicthonored
Full per-method matrix (all four methods run at each vantage):
| vantage | icmp6-echo | dns-tcp | tls | http |
|---|---|---|---|---|
| go6lab | honored | no_tcp | no_tcp | no_tcp |
| karsolink | no_echo | no_tcp | no_tcp | no_tcp |
| odin | honored | no_tcp | no_tcp | no_tcp |
✓ All vantages agree on method(s): icmp6-echo — the headline-method spread above is dispatcher noise, not a real Type 2 disagreement.
These vantage-level disagreements are rooted somewhere in the forward paths. Joining each per-vantage traceroute against the IP→AS lookup from our global yarrp mesh, the first hop where the paths land in different ASes is the most likely site of the offending filter / unreachable AS / Type 2 drop.
Suspect transit ASes (ranked by how often they appear at the divergence point on the path of the worse-classifying vantage): AS6939, AS216309.
- From go6lab (open/Type-2=honored) the path enters AS6939 at hop 5; from karsolink (open/Type-2=no_echo) the same hop is in AS216309. Last common AS: AS216309. The disagreement is most likely rooted in one of those two transit ASes.
- From go6lab (open/Type-2=honored) the path enters AS6939 at hop 5; from odin (open/Type-2=honored) the same hop is in an opaque hop. Last common AS: AS216309. The disagreement is most likely rooted in one of those two transit ASes.
- From karsolink (open/Type-2=no_echo) the path enters an opaque hop at hop 8; from odin (open/Type-2=honored) the same hop is in AS216309. Last common AS: AS216309. The disagreement is most likely rooted in one of those two transit ASes.
Diagnosis is path-level, not packet-level: it tells you which transit AS is the prime suspect, not exactly which firewall rule is to blame. Use the tracepath6 output below (when available) for per-hop PMTU evidence on the same path.
✨ Diagnostic interpretation
Per-hop PTB acceptance walk
From the local vantage, we walk the forward path hop-by-hop, sending each hop a 1500-byte ICMPv6 Echo, then a forged PTB (MTU=1280) sourced from us, then another 1500-byte Echo. If the second reply arrives fragmented or smaller, that hop honoured the PTB. If unchanged, it didn't. The first ✗ in an otherwise-✓ path is the most likely filter location. Cross-country aggregation: see the global PTB filter atlas for transit ASes ranked by filter rate across all measurements.
| # | hop IP | AS | Holder | PTB acceptance |
|---|---|---|---|---|
| 1 | 2607:fae0:a000::2 | AS8038 | 6CONNECT - 6connect, Inc., US | - skipped (CoPP) |
| 2 | * | - | - (no IP) | |
| 3 | 2a03:a100:0:201:1::1 | AS56635 | XENYA - XENYA inzeniring, proizvodnja in | ✓ honored |
| 4 | 2001:470:1:5be::1 | AS6939 | HURRICANE - Hurricane Electric LLC, US | ? no_response |
| 5 | * | - | - (no IP) | |
| 6 | 2001:470:0:2ea::2 | AS6939 | HURRICANE - Hurricane Electric LLC, US | ? no_response |
| 7 | * | - | - (no IP) | |
| 8 | 2a14:7584:4100::1 | AS216309 | INVISIONTECH-GROUP-SRL - InvisionTech Gr | ✓ honored |
Tests host-mode PTB acceptance (PTBs aimed at the hop itself). A router that honours PTBs to itself can still be filtering PTBs transiting through it; this is one indicator, not proof of full PTB transparency. Hops in CoPP-rate-limit ranges are skipped to avoid false signals.
From NL host (go6lab) openRFC 4890 ✓
filter likely at: (none) · min PMTU on path: 1500
Path (traceroute + mtr + PTR)
| # | IP / PTR | RTT | mtr loss | AS | AS holder |
|---|---|---|---|---|---|
| 1 | 2a00:8642:42::3 | 1.6ms | 0% | AS203993 | STEFFANN-DC-AS - S.J.M. Steffann, NL |
| 2 | gw.friends.steffann.nl 2a00:8642:1000:f000::1 | 2.0ms | 0%* | AS203993 | STEFFANN-DC-AS - S.J.M. Steffann, NL |
| 3 | * | - | - | - | |
| 4 | be1.core3.ams1.he.net 2001:470:e:5e::1 | 6.6ms | 0% | AS6939 | HURRICANE - Hurricane Electric LLC, US |
| 5 | be2.core4.fra1.he.net 2001:470:e:38::2 | 11.3ms | 0% | AS6939 | HURRICANE - Hurricane Electric LLC, US |
| 6 | * | - | - | - | |
| 7 | * | - | - | - | |
| 8 | * | - | - | - | |
| 9 | 2a14:7584:4100::1 | 21.4ms | 0% | AS216309 | INVISIONTECH-GROUP-SRL - InvisionTech Group S.r.l., IT |
tracepath -6
1?: [LOCALHOST] 0.032ms pmtu 1500
1: 2a00:8642:42::3 1.299ms
1: 2a00:8642:42::3 1.652ms
2: gw.friends.steffann.nl 2.280ms
3: no reply
4: be1.core3.ams1.he.net 6.354ms
5: be2.core4.fra1.he.net 12.790ms
6: no reply
7: no reply
8: no reply
9: 2a14:7584:4100::1 21.632ms reached
Resume: pmtu 1500 hops 9 back 13 From ITA host (Karsolink) open
filter likely at: (none) · min PMTU on path: 1500
Path (traceroute + mtr + PTR)
| # | IP / PTR | RTT | mtr loss | AS | AS holder |
|---|---|---|---|---|---|
| 1 | * | - | 0%* | - | |
| 2 | 2a12:d8c0:109f:121::a1 | 0.4ms | 0%* | AS204471 | KARSOLINK - 2S Computers SRL, IT |
| 3 | 2a12:d8c0:101f:6::1 | 9.9ms | 70% | AS204471 | KARSOLINK - 2S Computers SRL, IT |
| 4 | * | - | - | - | |
| 5 | 2a14:7584:4100::1 | 10.2ms | 0% | AS216309 | INVISIONTECH-GROUP-SRL - InvisionTech Group S.r.l., IT |
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: karsolink-01.net.karsolink.com 0.570ms
1: karsolink-01.net.karsolink.com 0.626ms
2: 2a12:d8c0:109f:121::a1 0.918ms
3: 2a12:d8c0:101f:6::1 10.412ms
4: no reply
5: 2a14:7584:4100::1 10.671ms reached
Resume: pmtu 1500 hops 5 back 9 From SLO host (6connect) openRFC 4890 ✓
filter likely at: (none) · min PMTU on path: 1500
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 | * | - | 0%* | - | |
| 3 | 2a03:a100:0:201:1::1 | 0.8ms | 0% | AS56635 | XENYA - XENYA inzeniring, proizvodnja in trgovina, d.o.o. Ljubljana, SI |
| 4 | e0-1.core1.lju1.he.net 2001:470:1:5be::1 | 1.8ms | 0% | AS6939 | HURRICANE - Hurricane Electric LLC, US |
| 5 | * | - | - | - | |
| 6 | port-channel1.core1.zag2.he.net 2001:470:0:2ea::2 | 4.0ms | 10% | AS6939 | HURRICANE - Hurricane Electric LLC, US |
| 7 | * | - | - | - | |
| 8 | 2a14:7584:4100::1 | 18.4ms | 0% | AS216309 | INVISIONTECH-GROUP-SRL - InvisionTech Group S.r.l., IT |
Rate-limited ICMPv6: hop 6 (loss between 5% and 95% across mtr cycles - the router replies but only sometimes).
tracepath -6
1?: [LOCALHOST] 0.036ms pmtu 1500
1: fw1-lju.6connect.com 0.519ms
1: fw1-lju.6connect.com 0.380ms
2: no reply
3: 2a03:a100:0:201:1::1 0.862ms
4: e0-1.core1.lju1.he.net 2.075ms
5: no reply
6: port-channel1.core1.zag2.he.net 3.713ms
7: no reply
8: 2a14:7584:4100::1 18.421ms reached
Resume: pmtu 1500 hops 8 back 13