AS21034 - MICSO-SRL-AS Micso Information Technology SrlPARFC 4890 ✓RPKI ✓ 1/1ASPA ✓

← back to summary

All countriesHomeState of IPv6TopologyIXPsAboutipv6.si ↗ Sparky

AS overview

Test target: 2a00:1be0:85:69:40:: · micso.it · address space: PA · prefixes announced: 1

prefix(es): 2a00:1be0::/32

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 / hostnameSourceNL host (go6lab)ITA host (Karsolink)SLO host (6connect)
ping1500B:80:443reachedping1500B:80:443reachedping1500B:80:443reached
2a00:1be0:85:69:40::
micso.it
drvopenopen-openopen-openopen-

RPKI & ASPA

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

PrefixRPKI stateReasonCovering VRP(s)
2a00:1be0::/32✓ validmatched VRP (correct origin, length within maxLength)AS21034 /32 maxLen 32 (ripe)

ASPA: this AS has published an ASPA record listing 3 upstream provider(s) that are authorized to propagate routes from it: AS3269, AS8928, AS12874. 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

At least one router inside AS21034's announced prefix replied during the random-target probe. Hop(s): 2a00:1be0:0:97::257. 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:

Why they disagree - different probe methods: These vantages picked different probe methods, so their verdicts are not directly comparable. The active test tries methods in order (icmp6-echodns-tcptlshttp) and stops at the first that produces a definitive verdict; if the chosen method differs, the underlying evidence differs too. Most often this is because the path PMTU on one vantage is below 1500 B, so the natural Echo Reply is already fragmented and the icmp6-echo method falls through to a TCP-based one. This is largely a measurement artifact, not a destination-behaviour difference.

Failure detail — what to grep in your logs
vantageour sourceyour targetmethodresulttested (UTC)
go6lab2a00:8642:42::752a00:1be0:85:69:40::icmp6-echohonored2026-05-30T12:42:20Z
karsolink2a12:d8c0:105a:9001::a1542a00:1be0:85:69:40::tlspartial2026-05-30T12:44:40Z
odin2607:fae0:a000::422a00:1be0:85:69:40::icmp6-echohonored2026-05-30T12:42:12Z

Attempt log (go6lab):

  1. icmp6-echohonored (size_before=1460, size_after=None)
  2. dns-tcpno_tcp: connect failed: timed out
  3. tlsnot_honored (size_before=2856, size_after=2856)
  4. httpinconclusive (size_before=219, size_after=None): natural max segment 219B already <= 1220B; nothing to shrink

Attempt log (karsolink):

  1. icmp6-echono_echo: no Echo Reply to 1300-byte probe
  2. dns-tcpno_tcp: connect failed: timed out
  3. tlspartial (size_before=2856, size_after=1937)
  4. httpinconclusive (size_before=200, size_after=None): natural max segment 200B already <= 1220B; nothing to shrink

Attempt log (odin):

  1. icmp6-echohonored (size_before=1460, size_after=None)
  2. dns-tcpno_tcp: connect failed: timed out
  3. tlsnot_honored (size_before=2856, size_after=3365)
  4. httpinconclusive (size_before=200, size_after=None): natural max segment 200B 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.

Where the path divergence is

Mixed disagreement. At least one pair of vantages used the same probe method and disagreed (real Type 2 asymmetry); other pairs used different methods (probe-availability noise). The path-divergence summary below covers all pairs; the AI interpretation focuses on the real cases.

Per-vantage probe + verdict (headline):

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

vantageicmp6-echodns-tcptlshttp
go6labhonoredno_tcpnot_honoredinconclusive
karsolinkno_echono_tcppartialinconclusive
odinhonoredno_tcpnot_honoredinconclusive

✓ 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): AS12874, AS21034, AS50673.

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::3303AS51988ARNES-SIX - ARNES, SI✓ honored
52001:918:100:74::1AS3303SWISSCOM - Swisscom (Schweiz) AG, CH? no_response
62001:4d98:a000::15d-NA? no_response
72001:b00:1:1:1::1b5AS12874FASTWEB - Fastweb SpA, IT? no_response
82001:b00:1:1:2::abAS12874FASTWEB - Fastweb SpA, IT? no_response
92001:b00:1:1:2::dbAS12874FASTWEB - Fastweb SpA, IT? no_response
102a00:1be0:0:97::257AS21034MICSO-SRL-AS - Micso Information Technol? no_response
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

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

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
12a00:8642:42::30.8ms0%AS203993STEFFANN-DC-AS - S.J.M. Steffann, NL
2*-0%*-
32a00:1ca8:1::1942.4ms0%AS50673Serverius-as - Serverius Holding B.V., NL
42a03:3f40::10:335.6ms0%AS50673Serverius-as - Serverius Holding B.V., NL
52001:7f8:1::a501:2874:189.1ms0%-NA
62001:b00:1:1:3::13120.8ms0%AS12874FASTWEB - Fastweb SpA, IT
72001:b00:1:1:3::d731.8ms0%AS12874FASTWEB - Fastweb SpA, IT
82001:b00:1:1:2::d932.1ms50%AS12874FASTWEB - Fastweb SpA, IT
92a00:1be0:0:97::25737.3ms0%AS21034MICSO-SRL-AS - Micso Information Technology Srl, IT
10*-0%-
11*-0%-
12*---
13*---
14*---
15*---
16*---
17*---
18*---
19*---
20*---
21*---
22*---
23*---
24*---

Rate-limited ICMPv6: 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:  2a00:8642:42::3                                       1.807ms 
 1:  2a00:8642:42::3                                       1.694ms 
 2:  no reply
 3:  2a00:1ca8:1::194                                      4.055ms 
 4:  2a03:3f40::10:33                                      8.497ms 
 5:  2001:7f8:1::a501:2874:1                              64.174ms 
 6:  2001:b00:1:1:3::133                                  21.812ms 
 7:  2001:b00:1:1:3::d7                                   30.468ms 
 8:  2001:b00:1:1:2::db                                   29.849ms 
 9:  2a00:1be0:0:97::257                                  40.913ms 
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) 34.2ms
4/4
Echo 1500B (DF) 34.4ms
no
Type 1 dest-unreach
443,80
TCP responds on

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
1*-0%*-
2*---
3*-90%-
4fastweb.minap.it
2001:7f8:c5::a501:2874:1
10.8ms30%AS12874Fastweb S.p.A.
52001:b00:1:1:1::1af9.6ms0%AS12874FASTWEB - Fastweb SpA, IT
62001:b00:1:1:3::d717.8ms0%AS12874FASTWEB - Fastweb SpA, IT
72001:b00:1:1:2::d918.4ms20%AS12874FASTWEB - Fastweb SpA, IT
82a00:1be0:0:97::25722.3ms0%AS21034MICSO-SRL-AS - Micso Information Technology Srl, IT
9*-0%-
10*-0%-
11*---
12*---
13*---
14*---
15*---
16*---
17*---
18*---
19*---
20*---
21*---
22*---
23*---
24*---

Rate-limited ICMPv6: hop 3, hop 4, hop 7 (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.725ms 
 1:  karsolink-01.net.karsolink.com                        0.786ms 
 2:  2a12:d8c0:109f:121::a1                                1.278ms 
 3:  2a12:d8c0:101f:6::1                                  10.614ms 
 4:  no reply
 5:  2001:b00:1:1:1::1b1                                  10.000ms 
 6:  2001:b00:1:1:3::d7                                   18.257ms 
 7:  2001:b00:1:1:2::db                                   22.173ms 
 8:  2a00:1be0:0:97::257                                  23.882ms 
 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) 29.4ms
3/4
Echo 1500B (DF) 29.2ms
no
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*-80%-
42001:7f8:46:0:1::33037.9ms0%AS51988ARNES-SIX - ARNES, SI
52001:918:100:74::17.9ms0%AS3303SWISSCOM - Swisscom (Schweiz) AG, CH
62001:4d98:a000::15d8.8ms90%-NA
72001:b00:1:1:1::1b510.2ms0%AS12874FASTWEB - Fastweb SpA, IT
82001:b00:1:1:2::ab22.5ms0%AS12874FASTWEB - Fastweb SpA, IT
92001:b00:1:1:2::db27.5ms50%AS12874FASTWEB - Fastweb SpA, IT
102a00:1be0:0:97::25729.4ms0%AS21034MICSO-SRL-AS - Micso Information Technology Srl, IT
11*-0%-
12*-0%-
13*---
14*---
15*---
16*---
17*---
18*---
19*---
20*---
21*---
22*---
23*---
24*---

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

tracepath -6

 1?: [LOCALHOST]                        0.039ms pmtu 1500
 1:  fw1-lju.6connect.com                                  3.023ms 
 1:  fw1-lju.6connect.com                                  1.089ms 
 2:  no reply
 3:  no reply
 4:  2001:7f8:46:0:1::3303                                 8.337ms 
 5:  2001:918:100:74::1                                    8.271ms 
 6:  2001:4d98:a000::119                                  24.667ms asymm 11 
 7:  2001:b00:1:1:3::131                                  10.751ms asymm  9 
 8:  2001:b00:1:1:2::ab                                   19.147ms asymm 10 
 9:  2001:b00:1:1:2::db                                   26.215ms asymm 11 
10:  2a00:1be0:0:97::257                                  29.879ms 
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