AS197579 - BASSPI/PARFC 4890 ✓RPKI ✓ 1/1ASPA ✓

← back to summary

All countriesHomeState of IPv6TopologySIXAboutipv6.si ↗ Sparky

AS overview

Test target: 2a13:6b40:0:185::10 · ns3.bass.si · address space: mixed · prefixes announced: 1

prefix(es): 2a13:6b40::/29

Targets & per-vantage-point probe results (2 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
2a13:6b40:0:185::10
ns3.bass.si
drv??-??-??-
2a13:6b40:0:92::56hit??-??-??-

SIX peering

Not an SIX member, but our traceroute path crosses the SIX LAN from SLO host (6connect) - reached via an SIX-resident transit operator.

RPKI & ASPA

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

PrefixRPKI stateReasonCovering VRP(s)
2a13:6b40::/29✓ validmatched VRP (correct origin, length within maxLength)AS197579 /29 maxLen 29 (ripe)

ASPA: this AS has published an ASPA record listing 4 upstream provider(s) that are authorized to propagate routes from it: AS3212, AS12778, AS34779, AS214499. Routes from this AS that arrive via any other upstream are considered ASPA-invalid by validators that enforce ASPA.

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

We probed 15 arbitrary IPv6 address(es) inside AS197579's announced prefix(es). No router inside the prefix responded. The deepest visible hop was 2a00:fc0:4320:3::a at hop 7 - that router answers ICMPv6 Echo. This is not in AS197579'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 - measurement artifact: One vantage's probe didn't generate enough data to detect segment shrinkage (natural reply too small, or no second response). The other vantage's verdict is the meaningful one.

Failure detail — what to grep in your logs
vantageour sourceyour targetmethodresulttested (UTC)
go6lab2a00:8642:42::752a13:6b40:0:185::10icmp6-echohonored2026-05-30T10:36:15Z
karsolink2a12:d8c0:105a:9001::a1542a13:6b40:0:185::10icmp6-echoinconclusive2026-05-30T10:45:57Z
odin2607:fae0:a000::422a13:6b40:0:185::10icmp6-echohonored2026-05-30T10:35:41Z

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. tlsno_tcp: TLS connect failed
  4. httpno_tcp: tcp/80 not open

Attempt log (karsolink):

  1. icmp6-echoinconclusive (size_before=1360, size_after=None): no Echo Reply after PTB (probe 1400B)
  2. dns-tcpinconclusive (size_before=156, size_after=None): max DNS-over-TCP segment 156B; not big enough to test PMTU shrink
  3. tlsno_tcp: TLS connect failed
  4. httpno_tcp: tcp/80 not open

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=156, size_after=None): max DNS-over-TCP segment 156B; not big enough to test PMTU shrink
  3. tlsno_tcp: TLS connect failed
  4. httpno_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):

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

vantageicmp6-echodns-tcptlshttp
go6labhonoredinconclusiveno_tcpno_tcp
karsolinkinconclusiveinconclusiveno_tcpno_tcp
odinhonoredinconclusiveno_tcpno_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, AS34779, AS3212.

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)
3*-- (no IP)
42001:7f8:46::3:4779AS34779T-2✓ honored
52a01:260:1:1::35AS34779T-2-AS - T-2, d.o.o., SI? no_response
62a01:260:c021::2AS34779T-2-AS - T-2, d.o.o., SI? no_response
7*-- (no IP)
8*-- (no IP)
9*-- (no IP)
10*-- (no IP)
11*-- (no IP)
12*-- (no IP)
13*-- (no IP)
14*-- (no IP)
15*-- (no IP)
16*-- (no IP)
17*-- (no IP)
18*-- (no IP)
19*-- (no IP)
20*-- (no IP)
21*-- (no IP)
22*-- (no IP)
23*-- (no IP)
24*-- (no IP)

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

3/4
Echo small (56B) 30.1ms
4/4
Echo 1500B (DF) 30.7ms
no
Type 1 dest-unreach
-
TCP responds on

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
12a00:8642:42::31.1ms0%AS203993STEFFANN-DC-AS - S.J.M. Steffann, NL
2gw.friends.steffann.nl
2a00:8642:1000:f000::1
2.2ms-AS203993STEFFANN-DC-AS - S.J.M. Steffann, NL
32a00:1ca8:1::1942.1ms10%AS50673Serverius-as - Serverius Holding B.V., NL
42a03:3f40::10:335.6ms0%AS50673Serverius-as - Serverius Holding B.V., NL
52001:7f8:13::a500:3212:130.6ms0%-NA
62a00:fc0:4320:3::a30.8ms0%AS3212TELEMACH - Telemach Slovenija d.o.o., SI
72a00:fc0:4320:3::b29.8ms0%AS3212TELEMACH - Telemach Slovenija d.o.o., SI
8*-0%-
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.046ms pmtu 1500
 1:  2a00:8642:42::3                                       2.275ms 
 1:  2a00:8642:42::3                                       2.160ms 
 2:  gw.friends.steffann.nl                                3.295ms 
 3:  2a00:1ca8:1::194                                      3.211ms 
 4:  2a03:3f40::10:33                                      6.671ms 
 5:  2001:7f8:13::a500:3212:1                             32.311ms asymm 10 
 6:  2a00:fc0:4320:3::a                                   32.276ms asymm 10 
 7:  2a00:fc0:4320:3::b                                   30.525ms asymm 11 
 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)   open

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

4/4
Echo small (56B) 25.8ms
3/4
Echo 1500B (DF) 25.9ms
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.5ms-AS204471KARSOLINK - 2S Computers SRL, IT
2*---
32a12:d8c0:101f:6::160.6ms80%AS204471KARSOLINK - 2S Computers SRL, IT
4*---
5100ge0-0-0-20.core1.vie1.he.net
2001:470:0:414::1
72.4ms0%AS6939HURRICANE - Hurricane Electric LLC, US
6telemach-d-o-o.e0-66.core2.vie1.he.net
2001:470:1:ab3::2
24.9ms10%AS6939HURRICANE - Hurricane Electric LLC, US
72a00:fc0:4320:3::a75.5ms0%AS3212TELEMACH - Telemach Slovenija d.o.o., SI
82a00:fc0:4320:3::b25.3ms0%AS3212TELEMACH - Telemach Slovenija d.o.o., SI
9*-0%-
10*---
11*---
12*---
13*---
14*---
15*---
16*---
17*---
18*---
19*---
20*---
21*---
22*---
23*---
24*---

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

tracepath -6

 1?: [LOCALHOST]                        0.029ms pmtu 1500
 1:  karsolink-01.net.karsolink.com                        0.625ms 
 2:  no reply
 3:  2a12:d8c0:101f:6::1                                  10.551ms 
 4:  no reply
 5:  100ge0-0-0-20.core1.vie1.he.net                      22.279ms 
 6:  2001:7f8:30:0:2:1:0:3212                             26.448ms asymm  9 
 7:  2a00:fc0:4320:3::a                                   25.711ms asymm  9 
 8:  2a00:fc0:4320:3::b                                   24.320ms asymm 10 
 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) 3.0ms
4/4
Echo 1500B (DF) 3.1ms
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.3ms0%*AS80386CONNECT - 6connect, Inc., US
2*---
3*---
4six.t-2.si @SIX
2001:7f8:46::3:4779
1.8ms0%AS34779T-2
52a01-260-1-1--35.core6.t-2.net
2a01:260:1:1::35
1.5ms0%AS34779T-2-AS - T-2, d.o.o., SI
62a01-260-c021--2.link6.t-2.net
2a01:260:c021::2
2.6ms0%AS34779T-2-AS - T-2, d.o.o., SI
7*-10%-
8*---
9*---
10*---
11*---
12*---
13*---
14*---
15*---
16*---
17*---
18*---
19*---
20*---
21*---
22*---
23*---
24*---

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

tracepath -6

 1?: [LOCALHOST]                        0.016ms pmtu 1500
 1:  fw1-lju.6connect.com                                  0.626ms 
 1:  fw1-lju.6connect.com                                  0.481ms 
 2:  no reply
 3:  2a03:a100:0:201:1::1                                  0.972ms 
 4:  six.t-2.si                                            1.414ms 
 5:  2a01-260-1-1--35.core6.t-2.net                        2.514ms 
 6:  2a01-260-c021--2.link6.t-2.net                        2.410ms 
 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