AS overview
Test target: 2a07:2e80::1 · static prefix probe · address space: PA · prefixes announced: 1
prefix(es): 2a07:2e80::/29
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 | ||
2a07:2e80::1 | prb | ✓ | ✓ | ? | ? | ✓ | ✓ | ✓ | refused | refused | ✓ | ✓ | ✓ | refused | refused | ✓ |
MIX-IT / NAMEX / MINAP / TOP-IX / VSIX / EQUINIX-MILAN / BGPX-ROME / NAMEX-BARI / PCIX / DECIX-PALERMO peering
MIX-IT / NAMEX / MINAP / TOP-IX / VSIX / EQUINIX-MILAN / BGPX-ROME / NAMEX-BARI / PCIX / DECIX-PALERMO member - Selective peering, peering member, since 2017-03-03. IPv6 LAN: 2001:7f8:b:100:1d1:a520:3201:218. Locations: -.
RPKI & ASPA
1 of 1 prefix(es) covered by a valid ROA.
| Prefix | RPKI state | Reason | Covering VRP(s) |
|---|---|---|---|
2a07:2e80::/29 | ✓ valid | matched VRP (correct origin, length within maxLength) | AS203201 /29 maxLen 29 (ripe) |
Random-IP probe (yarrp) into the AS' prefixes
We probed 15 arbitrary IPv6 address(es) inside AS203201's announced prefix(es). No router inside the prefix responded. The deepest visible hop was 2001:2034:a:1d3::1 at hop 10 - that router answers ICMPv6 Echo. This is not in AS203201'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 not honored. Forged ICMPv6 PTB (MTU=1280) had no effect: the next 1500-byte Echo Reply still arrived whole (1460 B, no Fragment Header). PMTUD does not work toward this address from us.
method: ICMPv6 Echo + forged PTB, tested 2026-05-30T12:46:11Z
Failure detail — what to grep in your logs
| vantage | our source | your target | method | result | tested (UTC) |
|---|---|---|---|---|---|
| go6lab | 2a00:8642:42::75 | 2a07:2e80::1 | icmp6-echo | not_honored | 2026-05-30T12:46:11Z |
| karsolink | 2a12:d8c0:105a:9001::a154 | 2a07:2e80::1 | icmp6-echo | not_honored | 2026-05-30T12:54:53Z |
| odin | 2607:fae0:a000::42 | 2a07:2e80::1 | icmp6-echo | not_honored | 2026-05-30T12:45:56Z |
Attempt log (go6lab):
icmp6-echo→ not_honored (size_before=1460, size_after=1460)dns-tcp→ no_tcp: connect failed: timed outtls→ no_tcp: TLS connect failedhttp→ no_tcp: tcp/80 not open
Attempt log (karsolink):
icmp6-echo→ not_honored (size_before=1460, size_after=1460)dns-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→ not_honored (size_before=1460, size_after=1460)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.
What does "Type 2 not honored" actually mean? — click to expand
What this test does
Using the icmp6-echo method, we send a 1500-byte ICMPv6 Echo Request, then a forged ICMPv6 Type 2 (Packet Too Big) declaring path MTU=1280, and observe whether the next Echo Reply arrives split into IPv6 fragments. RFC 4890 requires hosts and intermediate networks not to filter ICMPv6 Type 2; the destination's TCP/UDP stack must act on a received PTB by lowering its Path MTU cache for that destination, which makes subsequent segments smaller.
What we measured
The TCP segment size your server emitted before our forged Type 2 was 1460 B; after, it was 1460 B. No change. RFC 4890 ("Type 2 messages MUST NOT be filtered") expects subsequent segments to shrink to fit a Path MTU of 1280 B.
Three plausible causes
- Your host firewall is dropping ICMPv6 Type 2 inbound. Many default firewall rule sets only allow Echo Request/Reply and Neighbor Discovery, silently dropping all other ICMPv6 types - including Packet Too Big.
- An upstream / transit network is dropping ICMPv6 Type 2 before it reaches you. Some transit ASes filter ICMPv6 messages other than Echo at the edge. The forged PTB never arrives, so your stack never has a chance to act on it.
- Your kernel is ignoring the PTB. Linux / BSD stacks normally accept ICMPv6 PTB and update the route cache, but a few sysctls (or a hardened kernel) can be configured to ignore PMTU updates - typically as part of an over-aggressive anti-spoofing or uRPF policy.
How to check & fix (Linux examples)
1. Confirm Type 2 is not blocked at the host firewall:
sudo ip6tables -L INPUT -nv | grep -iE 'icmpv6|packet-too-big' sudo nft list ruleset 2>/dev/null | grep -A1 'icmpv6'
If you see rules dropping ICMPv6 unconditionally, change them to permit at least icmpv6 type packet-too-big (and destination-unreachable, time-exceeded, parameter-problem per RFC 4890).
2. Confirm the kernel accepts incoming PTB:
sudo sysctl net.ipv6.conf.all.accept_redirects net.ipv4.ip_no_pmtu_disc net.ipv6.route.mtu_expires
The defaults (accept_redirects=1, ip_no_pmtu_disc=0) are the right values for honoring PTB.
3. Live trace: while we have an open TCP flow with a small MSS (we run our test from 2607:fae0:a000::42 on odin, 2a00:8642:42::75 on go6lab and 2a12:d8c0:105a:9001::a154 on karsolink), watch for our forged Type 2 arriving on your interface:
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 TCP segments still stay big, the drop is in your kernel or NIC offload (cause 3). If you don't see them at all, the drop is upstream of you (cause 2) - ask your upstream(s) to permit ICMPv6 Type 2.
4. If your test target above (2026-05-30T12:46:11Z) is a host that you don't own (e.g. a third-party DNS / TLS server you happen to operate prefixes for), the verdict reflects that specific host's behaviour - try the test against a server you do own and we'll happily re-run.
RFC 4890 references: §4.3.1 (Packet Too Big - MUST NOT be dropped), and RFC 8201 for the broader PMTUD requirement.
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.5ms | 0% | AS203993 | STEFFANN-DC-AS - S.J.M. Steffann, NL |
| 2 | gw.friends.steffann.nl 2a00:8642:1000:f000::1 | 2.4ms | 0%* | AS203993 | STEFFANN-DC-AS - S.J.M. Steffann, NL |
| 3 | 2a00:1ca8:1::194 | 2.4ms | 20% | AS50673 | Serverius-as - Serverius Holding B.V., NL |
| 4 | 2a03:3f40::10:41 | 2.8ms | 0% | AS50673 | Serverius-as - Serverius Holding B.V., NL |
| 5 | * | - | - | - | |
| 6 | * | - | - | - | |
| 7 | 2001:978:3::ca | 3.9ms | 0% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 8 | 2001:2034:a:69 | 4.0ms | 10% | - | |
| 9 | * | - | - | - | |
| 10 | mno-b8-link.ip.twelve99.net 2001:2034:a:272::1 | 31.2ms | 0% | AS1299 | TWELVE99 - Arelion Sweden AB, SE |
| 11 | 2a07:2e80::1 | 28.9ms | 0% | AS203201 | IT-SUPERNAP - INFRASTRUCTURE ITALIA COLO S.R.L., IT |
Rate-limited ICMPv6: hop 3, hop 8 (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.332ms
1: 2a00:8642:42::3 1.798ms
2: gw.friends.steffann.nl 3.031ms
3: 2a00:1ca8:1::194 3.424ms
4: 2a03:3f40::10:41 3.136ms
5: no reply
6: no reply
7: 2001:978:3::26 4.220ms asymm 6
8: adm-bb2-link.ip.twelve99.net 3.771ms asymm 7
9: no reply
10: mno-b3-link.ip.twelve99.net 29.697ms asymm 9
11: 2a07:2e80::1 28.511ms reached
Resume: pmtu 1500 hops 11 back 12 From ITA host (Karsolink) openRFC 4890 ✗
filter likely at: (none) · min PMTU on path: 1500
Path (traceroute + mtr + PTR)
| # | IP / PTR | RTT | mtr loss | AS | AS holder |
|---|---|---|---|---|---|
| 1 | * | - | 0%* | - | |
| 2 | * | - | - | - | |
| 3 | * | - | 0% | - | |
| 4 | 2a07:2e80::1 | 9.9ms | 0% | AS203201 | IT-SUPERNAP - INFRASTRUCTURE ITALIA COLO S.R.L., IT |
tracepath -6
1?: [LOCALHOST] 0.049ms pmtu 1500
1: karsolink-01.net.karsolink.com 0.667ms
1: karsolink-01.net.karsolink.com 0.755ms
2: 2a12:d8c0:109f:121::a1 1.287ms
3: 2a12:d8c0:101f:103::1 8.911ms
4: 2a07:2e80::1 10.250ms reached
Resume: pmtu 1500 hops 4 back 5 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 | * | - | - | - | |
| 3 | 2a03:a100:0:201:1::1 | 0.7ms | 10% | AS56635 | XENYA - XENYA inzeniring, proizvodnja in trgovina, d.o.o. Ljubljana, SI |
| 4 | e0-1.core1.lju1.he.net 2001:470:1:5be::1 | 2.3ms | 20% | AS6939 | HURRICANE - Hurricane Electric LLC, US |
| 5 | * | - | - | - | |
| 6 | port-channel1.core1.zag2.he.net 2001:470:0:2ea::2 | 4.1ms | 0% | AS6939 | HURRICANE - Hurricane Electric LLC, US |
| 7 | * | - | - | - | |
| 8 | 2a07:2e80::1 | 11.2ms | 0% | AS203201 | IT-SUPERNAP - INFRASTRUCTURE ITALIA COLO S.R.L., IT |
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.037ms pmtu 1500
1: fw1-lju.6connect.com 2.163ms
1: fw1-lju.6connect.com 0.972ms
2: no reply
3: 2a03:a100:0:201:1::1 0.815ms
4: e0-1.core1.lju1.he.net 2.041ms
5: no reply
6: port-channel1.core1.zag2.he.net 4.314ms
7: no reply
8: 2a07:2e80::1 11.520ms reached
Resume: pmtu 1500 hops 8 back 8