AS197209 - STN STORITVEPI/PARFC 4890 ✓RPKI ✗ 1/2ASPA -

← back to summary

All countriesHomeState of IPv6TopologySIXAboutipv6.si ↗ Sparky

AS overview

Test target: 2001:67c:be0::2 · via IPv6 Hitlist (responsive) · address space: mixed · prefixes announced: 2

prefix(es): 2001:67c:be0::/48, 2a00:ee7::/48

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
2001:67c:be0::1prb??-??-refusedrefused-
2001:67c:be0::2hit??-??-refusedrefused-

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

0 of 2 prefix(es) covered by a valid ROA, 1 invalid, 1 not-found.

PrefixRPKI stateReasonCovering VRP(s)
2a00:ee7::/48✗ invalidprefix is covered by VRP(s) for different origin AS(es): AS5603AS5603 /32 maxLen 32 (ripe); AS5603 /29 maxLen 29 (ripe)
2001:67c:be0::/48- not-foundno covering VRP

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

We probed 14 arbitrary IPv6 address(es) inside AS197209's announced prefix(es). No router inside the prefix responded. The deepest visible hop was 2a02:800:1:2001::7 at hop 8 - that router answers ICMPv6 Echo. This is not in AS197209'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 - 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
vantageour sourceyour targetmethodresulttested (UTC)
go6lab2a00:8642:42::752001:67c:be0::2icmp6-echohonored2026-05-30T10:32:31Z
karsolink2a12:d8c0:105a:9001::a1542001:67c:be0::2icmp6-echono_echo2026-05-30T10:36:55Z
odin2607:fae0:a000::422001:67c:be0::2icmp6-echohonored2026-05-30T10:32:24Z

Attempt log (go6lab):

  1. icmp6-echohonored (size_before=1460, size_after=None)
  2. dns-tcpno_tcp: connect failed: timed out
  3. tlsno_tcp: TLS connect failed
  4. httpno_tcp: tcp/80 not open

Attempt log (karsolink):

  1. icmp6-echono_echo: no Echo Reply to 1300-byte probe
  2. dns-tcpno_tcp: connect failed: timed out
  3. tlsno_tcp: TLS connect failed
  4. httpno_tcp: tcp/80 not open

Attempt log (odin):

  1. icmp6-echohonored (size_before=1460, size_after=None)
  2. dns-tcpno_tcp: connect failed: [Errno 111] Connection refused
  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
go6labhonoredno_tcpno_tcpno_tcp
karsolinkno_echono_tcpno_tcpno_tcp
odinhonoredno_tcpno_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 AS (ranked by how often they appear at the divergence point on the path of the worse-classifying vantage): AS9119.

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:0:1::9119AS51988ARNES-SIX - ARNES, SI? no_response
52a02:800:1:2001::7AS9119SOFTNET-AS - SOFTNET d.o.o., SI? 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.

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.6ms
yes
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
2*-0%*-
32a00:1ca8:1::1942.5ms10%AS50673Serverius-as - Serverius Holding B.V., NL
42a03:3f40::10:335.6ms0%AS50673Serverius-as - Serverius Holding B.V., NL
5*-20%-
6*-50%-
72a02:800:1:2001::724.3ms0%AS9119SOFTNET-AS - SOFTNET d.o.o., SI

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

tracepath -6

 1?: [LOCALHOST]                        0.033ms pmtu 1500
 1:  2a00:8642:42::3                                       2.709ms 
 1:  2a00:8642:42::3                                       1.680ms 
 2:  gw.friends.steffann.nl                                2.584ms 
 3:  2a00:1ca8:1::194                                      2.970ms 
 4:  2a03:3f40::10:33                                      5.655ms 
 5:  2001:7f8:13::a500:9119:1                             11.552ms asymm  7 
 6:  sn-lju-hu-0-1-0-0-81-slo.ntwk.softnet.si             24.515ms asymm  9 
 7:  2a02:800:1:2001::7                                   23.368ms reached
     Resume: pmtu 1500 hops 7 back 10 

From ITA host (Karsolink)   all blocked

filter likely at: before path completes · 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%*-
3*-60%-
4*---
5*---
6*---
7*---
8*-70%-
9*---
10*---
11*---
12*---
13*---
14*---
15*---
16*---
17*---
18*---
19*---
20*---
21*---
22*---
23*---
24*---

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.030ms pmtu 1500
 1:  karsolink-01.net.karsolink.com                        0.557ms 
 1:  karsolink-01.net.karsolink.com                        0.686ms 
 2:  2a12:d8c0:109f:121::a1                                0.767ms 
 3:  2a12:d8c0:101f:6::1                                  10.272ms 
 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)   openRFC 4890 ✓

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

4/4
Echo small (56B) 2.4ms
4/4
Echo 1500B (DF) 1.5ms
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.3ms0%*AS80386CONNECT - 6connect, Inc., US
2*---
3*---
42001:7f8:46:0:1::9119 @SIX1.9ms70%AS51988ARNES-SIX - ARNES, SI
52a02:800:1:2001::70.9ms0%AS9119SOFTNET-AS - SOFTNET d.o.o., SI

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

tracepath -6

 1?: [LOCALHOST]                        0.059ms pmtu 1500
 1:  fw1-lju.6connect.com                                  0.445ms 
 1:  fw1-lju.6connect.com                                  0.371ms 
 2:  no reply
 3:  2a03:a100:0:201:1::1                                  0.723ms 
 4:  2001:7f8:46:0:1::9119                                 1.896ms 
 5:  2a02:800:1:2001::7                                    1.780ms reached
     Resume: pmtu 1500 hops 5 back 5