AS42207 - AKOSPARFC 4890 ✓RPKI ✓ 3/3ASPA -

← back to summary

All countriesHomeState of IPv6TopologySIXAboutipv6.si ↗ Sparky

AS overview

Test target: 2a0b:15c0:abcd:1::abcd:ac05 · (external source) · address space: PA · prefixes announced: 3

prefix(es): 2a0b:15c4::/30, 2a0b:15c0::/29, 2a0b:15c0::/30

Targets & per-vantage-point probe results (8 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 / hostnameSourceNL host (go6lab)ITA host (Karsolink)SLO host (6connect)
ping1500B:80:443reachedping1500B:80:443reachedping1500B:80:443reached
2a0b:15c0::1prb??-refusedrefused-refusedrefused-
2a0b:15c0::2hit??-refusedrefused-refusedrefused-
2a0b:15c0:abcd:1:1623:f2ff:fe5c:5cbehitopenopen-openopen-openopen-
2a0b:15c0:abcd:1::1hit??-refusedrefused-refusedrefused-
2a0b:15c0:abcd:1::abcd:ac05atlopenopenopenopenopenopen
2a0b:15c0:ac05:1::1hit??-refusedrefused-refusedrefused-
2a0b:15c0:ac05:1:f6e9:d4ff:fe6a:70behit?openrefusedopenrefusedopen
2a0b:15c0:dada:1::1hit??-refusedrefused-refusedrefused-

SIX peering

SIX member - open peering, peering member, since 2017-10-02. IPv6 LAN: 2001:7f8:46:0:1:0:4:2207. Locations: lj_ijs, lj_tpl.

  • rs1-lan1-ipv6 → 2001:7f8:46:0:1:0:4:2207 Established (loc: lj_tpl, since 2026-02-25)
  • rs1-lan1-ipv6 → 2001:7f8:46::4:2207 Established (loc: lj_ijs, since 2026-02-25)
  • rs2-lan1-ipv6 → 2001:7f8:46:0:1:0:4:2207 Established (loc: lj_tpl, since 2026-05-12)
  • rs2-lan1-ipv6 → 2001:7f8:46::4:2207 Established (loc: lj_ijs, since 2026-05-12)

Announces via SIX route servers: 3 prefix(es) - 2a0b:15c0::/29, 2a0b:15c0::/30, 2a0b:15c4::/30

RPKI & ASPA

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

PrefixRPKI stateReasonCovering VRP(s)
2a0b:15c4::/30✓ validmatched VRP (correct origin, length within maxLength)AS42207 /30 maxLen 30 (ripe); AS42207 /29 maxLen 29 (ripe)
2a0b:15c0::/29✓ validmatched VRP (correct origin, length within maxLength)AS42207 /29 maxLen 29 (ripe)
2a0b:15c0::/30✓ validmatched VRP (correct origin, length within maxLength)AS42207 /30 maxLen 30 (ripe); AS42207 /29 maxLen 29 (ripe)

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

We probed 30 arbitrary IPv6 address(es) inside AS42207's announced prefix(es). No router inside the prefix responded. The deepest visible hop was 2001:470:0:578::2 at hop 9 - that router answers ICMPv6 Echo. This is not in AS42207's announced prefix; operationally it's the AS-edge / peering interface (often on a SIX 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

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:

Why they disagree - path-asymmetric Type 2 filtering: Both vantages used the ICMPv6 Echo + forged-PTB method on the same destination IP, but reached different verdicts. The destination's stack is the same in both cases - so the difference is in the path: a transit AS on one route filters our forged Type 2 (or its return ICMPv6 carrying the embedded packet) while the other route delivers it intact. The vantage that says honored shows what the destination's stack actually does; the one that says not honored shows that the path between us and them drops Type 2.

Failure detail — what to grep in your logs
vantageour sourceyour targetmethodresulttested (UTC)
go6lab2a00:8642:42::752a0b:15c0:abcd:1::abcd:ac05icmp6-echohonored2026-05-30T10:35:41Z
karsolink2a12:d8c0:105a:9001::a1542a0b:15c0:abcd:1::abcd:ac05icmp6-echonot_honored2026-05-30T10:45:18Z
odin2607:fae0:a000::422a0b:15c0:abcd:1::abcd:ac05icmp6-echohonored2026-05-30T10:35:16Z

Attempt log (go6lab):

  1. icmp6-echohonored (size_before=1460, size_after=None)
  2. dns-tcpinconclusive (size_before=156, size_after=None): max DNS-over-TCP segment 156B; not big enough to test PMTU shrink
  3. tlsnot_honored (size_before=2010, size_after=2010)
  4. httpinconclusive (size_before=206, size_after=None): natural max segment 206B already <= 1220B; nothing to shrink

Attempt log (karsolink):

  1. icmp6-echonot_honored (size_before=1360, size_after=1360)
  2. dns-tcpinconclusive (size_before=156, size_after=None): max DNS-over-TCP segment 156B; not big enough to test PMTU shrink
  3. tlsnot_honored (size_before=2010, size_after=2010)
  4. httpinconclusive (size_before=215, size_after=None): natural max segment 215B already <= 1220B; nothing to shrink

Attempt log (odin):

  1. icmp6-echohonored (size_before=1360, size_after=None): natural Echo Reply at 1400B was already split into IPv6 fragments without our PTB intervention -- the destination's stack has a cached path MTU below 1400B from a previously-honored ICMPv6 Type 2, which is itself evidence that this destination honors PTB on this path.
  2. dns-tcpinconclusive (size_before=46, size_after=None): max DNS-over-TCP segment 46B; not big enough to test PMTU shrink
  3. tlsnot_honored (size_before=2010, size_after=2010)
  4. httpinconclusive (size_before=208, size_after=None): natural max segment 208B already <= 1220B; nothing to shrink

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 1360 B; after, it was 1360 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

  1. 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.
  2. 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.
  3. 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-30T10:45:18Z) 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.

Where the path divergence is

Per-vantage probe + verdict (headline):

Full per-method matrix (all four methods run at each vantage):

vantageicmp6-echodns-tcptlshttp
go6labhonoredinconclusivenot_honoredinconclusive
karsolinknot_honoredinconclusivenot_honoredinconclusive
odinhonoredinconclusivenot_honoredinconclusive

✓ All vantages agree on method(s): tls — 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, AS42207.

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

An operator-targeted diagnostic interpretation can be generated for this AS on demand. The pipeline holds the raw verdicts and the per-hop walk; an AI pass synthesises where to start looking. Click the button below to run it.

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 IPASHolderPTB acceptance
12607:fae0:a000::2AS80386CONNECT - 6connect, Inc., US- skipped (CoPP)
2*-- (no IP)
32a03:a100:0:201:1::1AS56635XENYA - XENYA inzeniring, proizvodnja in✓ honored
42001:7f8:46::4:2207AS42207AKOS? no_response
52a0b:15c0:abcd:1::abcd:ac05AS42207AKOS - Agencija za komunikacijska omrezj? no_response

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.

tracepath6 per-hop PMTU drilldown

For each target where Type 2 verdicts disagreed across vantages, tracepath -6 ran from every vantage to capture per-hop PMTU evolution along that vantage's actual forward path. A pmtu change entry on a hop means that hop's router generated a PTB and we observed the shrink; absence of any change combined with a not_honored verdict suggests a router somewhere downstream is silently dropping >MTU packets (an RFC 4890 violation) rather than sending a PTB.

Target 2a0b:15c0:abcd:1::abcd:ac05

go6lab — verdict honored

verdict = honored; final pmtu = 1500

#hop IPpmtu change
1<span class='muted'>no reply</span>
22a00:8642:1000:f000::1
3<span class='muted'>no reply</span>
42001:470:e:5e::1
52001:470:e:38::2
62001:470:e:5a::1
72001:470:0:2ef::2
82001:470:0:41d::1
92001:470:0:578::2
102001:7f8:46::4:2207
11<span class='muted'>no reply</span>
12<span class='muted'>no reply</span>
13<span class='muted'>no reply</span>
14<span class='muted'>no reply</span>
15<span class='muted'>no reply</span>
16<span class='muted'>no reply</span>
17<span class='muted'>no reply</span>
18<span class='muted'>no reply</span>
19<span class='muted'>no reply</span>
20<span class='muted'>no reply</span>
21<span class='muted'>no reply</span>
22<span class='muted'>no reply</span>
23<span class='muted'>no reply</span>
24<span class='muted'>no reply</span>
karsolink — verdict not_honored

verdict = not_honored; final pmtu = 1500

#hop IPpmtu change
1<span class='muted'>no reply</span>
22a12:d8c0:109f:121::a1
32a12:d8c0:101f:6::1
4<span class='muted'>no reply</span>
52001:470:0:6ea::2
6<span class='muted'>no reply</span>
72001:470:0:577::2
82001:7f8:46::4:2207
9<span class='muted'>no reply</span>
10<span class='muted'>no reply</span>
11<span class='muted'>no reply</span>
12<span class='muted'>no reply</span>
13<span class='muted'>no reply</span>
14<span class='muted'>no reply</span>
15<span class='muted'>no reply</span>
16<span class='muted'>no reply</span>
17<span class='muted'>no reply</span>
18<span class='muted'>no reply</span>
19<span class='muted'>no reply</span>
20<span class='muted'>no reply</span>
21<span class='muted'>no reply</span>
22<span class='muted'>no reply</span>
23<span class='muted'>no reply</span>
24<span class='muted'>no reply</span>
odin — verdict honored

verdict = honored; final pmtu = 1500

#hop IPpmtu change
1<span class='muted'>no reply</span>
22607:fae0:a000:2::2
32a03:a100:0:201:1::1
42001:7f8:46::4:2207
5<span class='muted'>no reply</span>
6<span class='muted'>no reply</span>
7<span class='muted'>no reply</span>
8<span class='muted'>no reply</span>
9<span class='muted'>no reply</span>
10<span class='muted'>no reply</span>
11<span class='muted'>no reply</span>
12<span class='muted'>no reply</span>
13<span class='muted'>no reply</span>
14<span class='muted'>no reply</span>
15<span class='muted'>no reply</span>
16<span class='muted'>no reply</span>
17<span class='muted'>no reply</span>
18<span class='muted'>no reply</span>
19<span class='muted'>no reply</span>
20<span class='muted'>no reply</span>
21<span class='muted'>no reply</span>
22<span class='muted'>no reply</span>
23<span class='muted'>no reply</span>
24<span class='muted'>no reply</span>

From NL host (go6lab)   openRFC 4890 ✓

filter likely at: (none) · min PMTU on path: 1500

4/4
Echo small (56B) 24.5ms
4/4
Echo 1500B (DF) 24.9ms
yes
Type 1 dest-unreach
443,80
TCP responds on

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
12a00:8642:42::31.3ms0%AS203993STEFFANN-DC-AS - S.J.M. Steffann, NL
2*-0%*-
3*---
4be1.core3.ams1.he.net
2001:470:e:5e::1
5.7ms0%AS6939HURRICANE - Hurricane Electric LLC, US
5be2.core4.fra1.he.net
2001:470:e:38::2
11.1ms0%AS6939HURRICANE - Hurricane Electric LLC, US
6be3.core2.fra2.he.net
2001:470:e:5a::1
11.7ms0%AS6939HURRICANE - Hurricane Electric LLC, US
7e0-33.core2.muc1.he.net
2001:470:0:2ef::2
14.5ms0%AS6939HURRICANE - Hurricane Electric LLC, US
8100ge0-0-0-23.core1.vie1.he.net
2001:470:0:41d::1
23.1ms0%AS6939HURRICANE - Hurricane Electric LLC, US
9six.akos.si @SIX
2001:7f8:46::4:2207
34.1ms0%AS42207AKOS
102a0b:15c0:abcd:1::abcd:ac0524.5ms0%AS42207AKOS - Agencija za komunikacijska omrezja in storitve republike Slovenije, SI

tracepath -6

 1?: [LOCALHOST]                        0.036ms pmtu 1500
 1:  2a00:8642:42::3                                       1.674ms 
 1:  2a00:8642:42::3                                       1.959ms 
 2:  gw.friends.steffann.nl                                3.239ms 
 3:  no reply
 4:  be1.core3.ams1.he.net                                 7.194ms 
 5:  be2.core4.fra1.he.net                                10.454ms 
 6:  be3.core2.fra2.he.net                                11.305ms 
 7:  100ge0-0-0-3.core1.vie1.he.net                       23.686ms 
 8:  100ge0-0-0-23.core1.vie1.he.net                      23.214ms asymm  7 
 9:  six.akos.si                                          26.706ms 
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)   openRFC 4890 ✗

filter likely at: (none) · min PMTU on path: 1500

4/4
Echo small (56B) 21.6ms
4/4
Echo 1500B (DF) 21.7ms
yes
Type 1 dest-unreach
443,80
TCP responds on

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
1*-0%*-
2*---
3*-80%-
4*---
5e0-35.core1.zag2.he.net
2001:470:0:6ea::2
19.0ms0%AS6939HURRICANE - Hurricane Electric LLC, US
6*---
7e0-35.core1.lju1.he.net
2001:470:0:577::2
22.1ms0%AS6939HURRICANE - Hurricane Electric LLC, US
8six.akos.si @SIX
2001:7f8:46::4:2207
22.3ms0%AS42207AKOS
92a0b:15c0:abcd:1::abcd:ac0521.4ms0%AS42207AKOS - Agencija za komunikacijska omrezja in storitve republike Slovenije, SI

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:  no reply
 2:  2a12:d8c0:109f:121::a1                                0.760ms 
 3:  2a12:d8c0:101f:6::1                                  10.490ms 
 4:  no reply
 5:  e0-35.core1.zag2.he.net                              19.258ms 
 6:  no reply
 7:  e0-35.core1.lju1.he.net                              22.514ms 
 8:  six.akos.si                                          23.189ms 
 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)   openRFC 4890 ✓

filter likely at: (none) · min PMTU on path: 1500

4/4
Echo small (56B) 1.8ms
4/4
Echo 1500B (DF) 1.9ms
yes
Type 1 dest-unreach
443,80
TCP responds on

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
1fw1-lju.6connect.com
2607:fae0:a000::2
0.2ms0%*AS80386CONNECT - 6connect, Inc., US
2*-0%*-
32a03:a100:0:201:1::153.3ms20%AS56635XENYA - XENYA inzeniring, proizvodnja in trgovina, d.o.o. Ljubljana, SI
4six.akos.si @SIX
2001:7f8:46::4:2207
3.0ms0%AS42207AKOS
52a0b:15c0:abcd:1::abcd:ac051.0ms0%AS42207AKOS - Agencija za komunikacijska omrezja in storitve republike Slovenije, SI

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

tracepath -6

 1?: [LOCALHOST]                        0.033ms pmtu 1500
 1:  fw1-lju.6connect.com                                  0.700ms 
 1:  fw1-lju.6connect.com                                  0.898ms 
 2:  ccr-to-fw-ccr1-gw-lju.6connect.com                    0.763ms 
 3:  2a03:a100:0:201:1::1                                  0.670ms 
 4:  six.akos.si                                           3.483ms 
 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