AS57913 - toscanatlc ToscanaTLC s.r.lPARFC 4890 ✓RPKI ✓ 1/1ASPA ✓

← back to summary

All countriesHomeState of IPv6TopologyIXPsAboutipv6.si ↗ Sparky

AS overview

Test target: 2a13:f600::1 · static prefix probe · address space: PA · prefixes announced: 1

prefix(es): 2a13:f600::/29

Targets & per-vantage-point probe results (1 target(s) across 7 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 / hostnameSourceSRB host (SOX, Belgrade)DE host (Berlin)DE host (Düsseldorf)NL host (go6lab)ITA host (Karsolink)SLO host (6connect)SLO host (T-2)
ping1500B:80:443reachedping1500B:80:443reachedping1500B:80:443reachedping1500B:80:443reachedping1500B:80:443reachedping1500B:80:443reachedping1500B:80:443reached
2a13:f600::1prbrefusedrefusedrefusedrefusedrefusedrefused??refusedrefusedrefusedrefusedrefusedrefused

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 - Open peering, peering member, since 2023-03-17. IPv6 LAN: 2001:7f8:b:100:1d1:a5d5:7913:182. Locations: -.

RPKI & ASPA

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

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

ASPA: this AS has published an ASPA record listing 2 upstream provider(s) that are authorized to propagate routes from it: AS5398, AS41327. 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 35 arbitrary IPv6 address(es) inside AS57913's announced prefix(es). No router inside the prefix responded. The deepest visible hop was 2001:7f8:c5::a505:7913:1 at hop 13 - that router does not answer ICMPv6 Echo. This is not in AS57913'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

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)
belgrade2a09:ab81::912a13:f600::1icmp6-echohonored2026-09-23T12:09:34Z
berlin2a06:d1c1:10b::cccc2a13:f600::1icmp6-echohonored2026-09-23T12:09:32Z
duseldorf2a06:d1c1:10d::aaaa2a13:f600::1icmp6-echohonored2026-09-23T12:09:30Z
go6lab2a00:8642:42::752a13:f600::1icmp6-echonot_honored2026-09-23T12:11:34Z
karsolink2a12:d8c0:105a:9001::a1542a13:f600::1icmp6-echohonored2026-09-23T12:09:31Z
odin2607:fae0:a000::422a13:f600::1icmp6-echohonored2026-09-23T12:09:31Z
t22a01:261:313:b814:2a0:98ff:fe5b:13e42a13:f600::1icmp6-echohonored2026-09-23T12:09:33Z

Attempt log (belgrade):

  1. icmp6-echohonored (honored by fragmenting its reply into 2 via the IPv6 Fragment Header, rather than resizing)
  2. dns-tcpno_tcp: connect failed: [Errno 111] Connection refused
  3. tlsno_tcp: TLS connect failed
  4. httpno_tcp: tcp/80 not open

Attempt log (berlin):

  1. icmp6-echohonored (honored by fragmenting its reply into 2 via the IPv6 Fragment Header, rather than resizing)
  2. dns-tcpno_tcp: connect failed: [Errno 111] Connection refused
  3. tlsno_tcp: TLS connect failed
  4. httpno_tcp: tcp/80 not open

Attempt log (duseldorf):

  1. icmp6-echohonored (honored by fragmenting its reply into 2 via the IPv6 Fragment Header, rather than resizing)
  2. dns-tcpno_tcp: connect failed: [Errno 111] Connection refused
  3. tlsno_tcp: TLS connect failed
  4. httpno_tcp: tcp/80 not open

Attempt log (go6lab):

  1. icmp6-echonot_honored (reply shrank 1260→1260 B)
  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-echohonored (honored by fragmenting its reply into 2 via the IPv6 Fragment Header, rather than resizing)
  2. dns-tcpno_tcp: connect failed: [Errno 111] Connection refused
  3. tlsno_tcp: TLS connect failed
  4. httpno_tcp: tcp/80 not open

Attempt log (odin):

  1. icmp6-echohonored (honored by fragmenting its reply into 2 via the IPv6 Fragment Header, rather than resizing)
  2. dns-tcpno_tcp: connect failed: [Errno 111] Connection refused
  3. tlsno_tcp: TLS connect failed
  4. httpno_tcp: tcp/80 not open

Attempt log (t2):

  1. icmp6-echohonored (honored by fragmenting its reply into 2 via the IPv6 Fragment Header, rather than resizing)
  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 2a01:261:313:b814:2a0:98ff:fe5b:13e4 or src host 2a06:d1c1:10b::cccc or src host 2a06:d1c1:10d::aaaa or src host 2a09:ab81::91 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 some of our source IPs but not others, the drop is path-asymmetric - at least one transit on the differing route is filtering.

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 1260 B; after, it was 1260 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, 2a12:d8c0:105a:9001::a154 on karsolink, 2a09:ab81::91 on belgrade, 2a01:261:313:b814:2a0:98ff:fe5b:13e4 on t2, 2a06:d1c1:10a::bbbb on amsterdam, 2a06:d1c1:10d::aaaa on duseldorf and 2a06:d1c1:10b::cccc on berlin), 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 or src host 2a09:ab81::91 or src host 2a01:261:313:b814:2a0:98ff:fe5b:13e4 or src host 2a06:d1c1:10a::bbbb or src host 2a06:d1c1:10d::aaaa or src host 2a06:d1c1:10b::cccc)'

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-09-23T12:11:34Z) 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
belgradehonoredno_tcpno_tcpno_tcp
berlinhonoredno_tcpno_tcpno_tcp
duseldorfhonoredno_tcpno_tcpno_tcp
go6labnot_honoredno_tcpno_tcpno_tcp
karsolinkhonoredno_tcpno_tcpno_tcp
odinhonoredno_tcpno_tcpno_tcp
t2honoredno_tcpno_tcpno_tcp

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): AS57913, AS6939, AS41327.

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.

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 2a13:f600::1

amsterdam - verdict ?

(no hops captured)

belgrade - verdict honored

verdict = honored; final pmtu = 1500

#hop IPpmtu change
1<span class='muted'>no reply</span>
22001:7f8:1e::108
32001:b28:3ff::a16f:0:1
42a03:b020::225
52a03:b020:1:66::b
62a13:f600::1
berlin - verdict honored

verdict = honored; final pmtu = 1500

#hop IPpmtu change
1<span class='muted'>no reply</span>
22a06:d1c0::dead:beef:1c02
32a00:c380:b200:230::220
42a00:c380:b200:230::5
52a00:c380:b200:230::92
62a00:c380:b200:230::24
72a00:c380:b200:230::187
82a00:c380:b200:230::213
92001:7f8:12a::18
102a03:b020::225
112a03:b020:1:66::b
122a13:f600::1
duseldorf - verdict honored

verdict = honored; final pmtu = 1500

#hop IPpmtu change
1<span class='muted'>no reply</span>
22001:4ba0:92f4:3::1
3<span class='muted'>no reply</span>
42001:4ba0:ffe9:109::2
52001:4ba0:ffe9:8a::2
62001:4ba0:ffe9:103e::1
72001:4ba0:ffe9:103b::1
82001:4ba0:ffe9:b8::
92001:4ba0:ffe9:a7::1
102001:4ba0:ffe9:da::2
112001:4ba0:ffe9:db::2
122001:4ba0:ffe9:9a::2
132001:7f8:c5::a505:7913:1
142a13:f600::1
go6lab - verdict not_honored

verdict = not_honored; final pmtu = 1500

#hop IPpmtu change
1<span class='muted'>no reply</span>
22a00:8642:1000:f000::1
32001:7f8:b7::a504:1327:1
42a03:b020::225
52a03:b020:1:66::b
62a13:f600::1
karsolink - verdict honored

verdict = honored; final pmtu = 1500

#hop IPpmtu change
1<span class='muted'>no reply</span>
22a12:d8c0:109f:121::a1
32a12:d8c0:101f:103::1
42a13:f600::1
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
42a03:a100:0:201:1::1
5<span class='muted'>no reply</span>
62001:470:0:2ea::2
7<span class='muted'>no reply</span>
82a13:f600::1
t2 - verdict honored

verdict = honored; final pmtu = 1500

#hop IPpmtu change
1<span class='muted'>no reply</span>
22a01:260:1::225
32a01:260:1:1::9c
42001:7f8:13::a500:6939:1
52001:7f8:13::a500:6939:1
62001:470:e:5a::2
72001:470:e:153::2
82001:470:e:153::2
92001:470:e:dd::1
102a13:f600::1

Multi-vantage path map

Every hop of all vantages’ traceroutes toward the target, drawn left→right, grouped into per-AS bubbles (a hop seen from several vantages is one shared bubble, so converging paths merge). It answers two questions per vantage — shown on each source bubble as echo ✓/⚠/✗ · trace ✓/✗: did the destination reply to ICMPv6 Echo (✓ honored, ⚠ replied but PTB not honored, ✗ no reply), and did the traceroute reach it. A line to the target is drawn only when that vantage got an echo reply — solid if the PTB was honored, dashed if not (reachable but a broken-PMTUD / RFC 4890 violation). The path depth still shows how far the traceroute itself got, and runs of unanswered (* *) hops collapse into one dashed “silent” bubble. Open full size ↗

multi-vantage path diagram for AS57913

From SRB host (SOX, Belgrade)   openRFC 4890 ✓

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

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

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
12a09:ab81::10.3ms0%*AS60733PERKE-NET - ZORAN PEROVIC trading as Agencija Perke.NET, RS
22001:7f8:1e::1080.3ms0%AS13004SOX - Serbian Open Exchange DOO, RS
32001:b28:3ff::a16f:0:144.3ms0%AS31500GNM-AS - Global Network Management Inc, AG
42a03:b020::22545.6ms0%AS41327FIBERTELECOM-AS - Fiber Telecom S.p.A., IT
52a03:b020:1:66::b45.1ms0%AS41327FIBERTELECOM-AS - Fiber Telecom S.p.A., IT
6lo0-f1a01-itmil01.as57913.net
2a13:f600::1
47.6ms0%AS57913toscanatlc - ToscanaTLC s.r.l., IT

tracepath -6

 1?: [LOCALHOST]                        0.087ms pmtu 1500
 1:  _gateway                                              0.505ms 
 1:  _gateway                                              0.629ms 
 2:  2001:7f8:1e::108                                      0.544ms 
 3:  2001:b28:3ff::a16f:0:1                               41.512ms 
 4:  2a03:b020::225                                       46.487ms asymm  6 
 5:  2a03:b020:1:66::b                                    41.963ms asymm  6 
 6:  lo0-f1a01-itmil01.as57913.net                        42.815ms reached
     Resume: pmtu 1500 hops 6 back 5 

From DE host (Berlin)   openRFC 4890 ✓

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

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

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
1xe-0-0-13-178.gw01.ber01.as59645.net
2a06:d1c1:100:b::1
0.3ms0%*AS59645WYBT-NET - Tobias Fiebig, DE
2ae0-2453.cr10.ber01.lwlcom.net
2a06:d1c0::dead:beef:1c02
0.5ms0%*AS59645WYBT-NET - Tobias Fiebig, DE
3ae0-10.cr10.ber03.lwlcom.net
2a00:c380:b200:230::220
0.7ms0%AS50629LWLCOM - LWLcom GmbH, DE
4ae0-15.cr11.dtm01.lwlcom.net
2a00:c380:b200:230::5
8.3ms0%AS50629LWLCOM - LWLcom GmbH, DE
5ae0-10.cr10.dtm02.lwlcom.net
2a00:c380:b200:230::255
8.6ms0%AS50629LWLCOM - LWLcom GmbH, DE
6ae0-20.cr10.dus04.lwlcom.net
2a00:c380:b200:230::139
8.5ms0%AS50629LWLCOM - LWLcom GmbH, DE
7ae0-10.cr10.dus01.lwlcom.net
2a00:c380:b200:230::187
28.2ms0%AS50629LWLCOM - LWLcom GmbH, DE
8ae6-60.cr10.ams01.lwlcom.net
2a00:c380:b200:230::213
11.4ms0%AS50629LWLCOM - LWLcom GmbH, DE
92001:7f8:12a::1814.7ms0%-NA
102a03:b020::22524.2ms0%AS41327FIBERTELECOM-AS - Fiber Telecom S.p.A., IT
112a03:b020:1:66::b24.5ms0%AS41327FIBERTELECOM-AS - Fiber Telecom S.p.A., IT
12lo0-f1a01-itmil01.as57913.net
2a13:f600::1
24.4ms0%AS57913toscanatlc - ToscanaTLC s.r.l., IT

tracepath -6

 1?: [LOCALHOST]                        0.024ms pmtu 1500
 1:  xe-0-0-13-178.gw01.ber01.as59645.net                  0.604ms 
 1:  xe-0-0-13-178.gw01.ber01.as59645.net                  0.447ms 
 2:  ae0-2453.cr10.ber01.lwlcom.net                        0.721ms 
 3:  ae0-10.cr10.ber03.lwlcom.net                          1.210ms 
 4:  ae0-15.cr11.dtm01.lwlcom.net                          8.813ms asymm  5 
 5:  ae0-20.cr10.dtm01.lwlcom.net                          8.614ms asymm  4 
 6:  ae0-20.cr10.dus04.lwlcom.net                          8.618ms asymm  5 
 7:  ae0-20.cr10.dus01.lwlcom.net                          8.824ms asymm  4 
 8:  ae6-60.cr10.ams01.lwlcom.net                         11.559ms asymm  5 
 9:  2001:7f8:12a::18                                     15.014ms asymm  4 
10:  2a03:b020::225                                       24.417ms asymm  4 
11:  2a03:b020:1:66::b                                    24.482ms asymm 12 
12:  lo0-f1a01-itmil01.as57913.net                        24.776ms reached
     Resume: pmtu 1500 hops 12 back 11 

From DE host (Düsseldorf)   openRFC 4890 ✓

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

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

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
1xe-0-0-12-142.gw01.dus01.as59645.net
2a06:d1c1:100:d::1
0.3ms0%*AS59645WYBT-NET - Tobias Fiebig, DE
2eth1-0-12-h5594.edge5-dus1.bb.wiit.network
2001:4ba0:92f4:3::1
1.3ms0%AS24961MYLOC-AS - WIIT AG, DE
3*-0%-
4lag30.core3-dus1.bb.wiit.network
2001:4ba0:ffe9:109::2
0.3ms0%AS24961MYLOC-AS - WIIT AG, DE
5lag0-vl1011.core1-fra-ix.bb.wiit.network
2001:4ba0:ffe9:8a::2
4.3ms0%AS24961MYLOC-AS - WIIT AG, DE
6lag0-vl1001.core1-nbg-ncd.bb.wiit.network
2001:4ba0:ffe9:103e::1
7.0ms0%AS24961MYLOC-AS - WIIT AG, DE
7lag0-vl6.core2-nbg-ncd.bb.wiit.network
2001:4ba0:ffe9:103b::1
6.9ms0%AS24961MYLOC-AS - WIIT AG, DE
82001:4ba0:ffe9:b814.4ms0%-
9lag0-vl1009.core1-muc-eq3.bb.wiit.network
2001:4ba0:ffe9:a7::1
9.9ms0%AS24961MYLOC-AS - WIIT AG, DE
10lag0-vl1001.core1-pda-vsix.bb.wiit.network
2001:4ba0:ffe9:da::2
20.4ms0%AS24961MYLOC-AS - WIIT AG, DE
11lag0-vl1001.core1-mil-mix.bb.wiit.network
2001:4ba0:ffe9:db::2
20.4ms0%AS24961MYLOC-AS - WIIT AG, DE
12lag0-vl5.core3-mil-irid.bb.wiit.network
2001:4ba0:ffe9:9a::2
20.2ms0%AS24961MYLOC-AS - WIIT AG, DE
13toscanatlc.minap.it
2001:7f8:c5::a505:7913:1
20.5ms0%AS57913ToscanaTLC s.r.l.
14lo0-f1a01-itmil01.as57913.net
2a13:f600::1
20.7ms0%AS57913toscanatlc - ToscanaTLC s.r.l., IT

tracepath -6

 1?: [LOCALHOST]                        0.019ms pmtu 1500
 1:  xe-0-0-12-142.gw01.dus01.as59645.net                  0.360ms 
 1:  xe-0-0-12-142.gw01.dus01.as59645.net                  0.385ms 
 2:  eth1-0-12-h5594.edge5-dus1.bb.wiit.network            1.198ms 
 3:  no reply
 4:  lag30.core3-dus1.bb.wiit.network                      0.353ms 
 5:  lag0-vl1011.core1-fra-ix.bb.wiit.network              4.547ms 
 6:  lag0-vl1001.core1-nbg-ncd.bb.wiit.network             7.139ms 
 7:  lag0-vl6.core2-nbg-ncd.bb.wiit.network                7.123ms 
 8:  lag0-vl1006.core2-muc2.bb.wiit.network                9.759ms 
 9:  lag0-vl1009.core1-muc-eq3.bb.wiit.network             9.680ms 
10:  lag0-vl1001.core1-pda-vsix.bb.wiit.network           20.546ms 
11:  lag0-vl1001.core1-mil-mix.bb.wiit.network            20.598ms asymm  9 
12:  lag0-vl5.core3-mil-irid.bb.wiit.network              20.408ms asymm  8 
13:  toscanatlc.minap.it                                  20.732ms asymm 11 
14:  lo0-f1a01-itmil01.as57913.net                        20.685ms reached
     Resume: pmtu 1500 hops 14 back 10 

From NL host (go6lab)   openRFC 4890 ✗

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

4/4
Echo small (56B) 22.1ms
4/4
Echo 1500B (DF) 19.8ms
yes
Type 1 dest-unreach
-
TCP responds on

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
12a00:8642:42::20.8ms0%AS203993GNA-DC1-AS - S.J.M. Steffann, NL
2*-0%*-
3speed-ix.fibertelecom.it
2001:7f8:b7::a504:1327:1
3.6ms0%-NA
42a03:b020::22519.3ms0%AS41327FIBERTELECOM-AS - Fiber Telecom S.p.A., IT
52a03:b020:1:66::b19.6ms0%AS41327FIBERTELECOM-AS - Fiber Telecom S.p.A., IT
6lo0-f1a01-itmil01.as57913.net
2a13:f600::1
19.3ms0%AS57913toscanatlc - ToscanaTLC s.r.l., IT

tracepath -6

 1?: [LOCALHOST]                        0.045ms pmtu 1500
 1:  2a00:8642:42::2                                       6.013ms 
 1:  2a00:8642:42::2                                       2.644ms 
 2:  gw.friends.steffann.nl                                2.479ms 
 3:  speed-ix.fibertelecom.it                              3.323ms 
 4:  2a03:b020::225                                       22.414ms 
 5:  2a03:b020:1:66::b                                    22.207ms 
 6:  lo0-f1a01-itmil01.as57913.net                        25.778ms reached
     Resume: pmtu 1500 hops 6 back 6 

From ITA host (Karsolink)   openRFC 4890 ✓

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

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

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
1karsolink-01.net.karsolink.com
2a12:d8c0:105a:9001::1
0.3ms0%*AS204471KARSOLINK - 2S Computers SRL, IT
2*-0%*-
3*-90%-
4lo0-f1a01-itmil01.as57913.net
2a13:f600::1
8.9ms0%AS57913toscanatlc - ToscanaTLC s.r.l., IT

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

tracepath -6

 1?: [LOCALHOST]                        0.036ms pmtu 1500
 1:  karsolink-01.net.karsolink.com                        0.517ms 
 1:  karsolink-01.net.karsolink.com                        0.623ms 
 2:  no reply
 3:  no reply
 4:  lo0-f1a01-itmil01.as57913.net                         9.367ms reached
     Resume: pmtu 1500 hops 4 back 4 

From SLO host (6connect)   openRFC 4890 ✓

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

4/4
Echo small (56B) 11.9ms
3/4
Echo 1500B (DF) 12.8ms
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.7ms0%*AS80386CONNECT - 6connect, Inc., US
2*---
32a03:a100:0:201:1::10.7ms0%AS56635XENYA - XENYA inzeniring, proizvodnja in trgovina, d.o.o. Ljubljana, SI
4e0-1.core1.lju1.he.net
2001:470:1:5be::1
1.9ms0%AS6939HURRICANE - Hurricane Electric LLC, US
5*---
6port-channel1.core1.zag2.he.net
2001:470:0:2ea::2
209.7ms0%AS6939HURRICANE - Hurricane Electric LLC, US
7*---
8lo0-f1a01-itmil01.as57913.net
2a13:f600::1
12.7ms0%AS57913toscanatlc - ToscanaTLC s.r.l., IT

tracepath -6

 1?: [LOCALHOST]                        0.020ms pmtu 9000
 1:  fw1-lju.6connect.com                                  0.579ms 
 1:  fw1-lju.6connect.com                                  0.734ms 
 2:  no reply
 3:  2a03:a100:0:201:1::1                                  1.226ms 
 4:  2a03:a100:0:201:1::1                                  0.837ms pmtu 1500
 4:  e0-1.core1.lju1.he.net                                2.464ms 
 5:  no reply
 6:  port-channel1.core1.zag2.he.net                      50.360ms 
 7:  no reply
 8:  lo0-f1a01-itmil01.as57913.net                        12.470ms reached
     Resume: pmtu 1500 hops 8 back 8 

From SLO host (T-2)   openRFC 4890 ✓

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

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

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
12a01:261:313:b814::10.6ms0%*AS34779T-2-AS - T-2, d.o.o., SI
22a01:260:1::2251.9ms0%*AS34779T-2-AS - T-2, d.o.o., SI
32a01-260-1-1--9c.core6.t-2.net
2a01:260:1:1::9c
2.2ms0%*AS34779T-2-AS - T-2, d.o.o., SI
4hurricane-electric.nikhef.nlsix.net
2001:7f8:13::a500:6939:1
38.9ms0%*-NA
5hurricane-electric.nikhef.nlsix.net
2001:7f8:13::a500:6939:1
38.1ms0%-NA
6be1.core2.fra2.he.net
2001:470:e:43::2
41.7ms0%AS6939HURRICANE - Hurricane Electric LLC, US
7be3.core4.fra1.he.net
2001:470:e:5a::2
41.4ms10%AS6939HURRICANE - Hurricane Electric LLC, US
8be1.core1.mil2.he.net
2001:470:e:dd::1
34.0ms0%AS6939HURRICANE - Hurricane Electric LLC, US
9*-0%-
10*---
11lo0-f1a01-itmil01.as57913.net
2a13:f600::1
31.9ms0%AS57913toscanatlc - ToscanaTLC s.r.l., IT

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

tracepath -6

 1?: [LOCALHOST]                        0.015ms pmtu 1500
 1:  no reply
 2:  2a01:260:1::225                                       6.500ms 
 3:  2a01-260-1-1--9c.core6.t-2.net                        3.217ms 
 4:  2a01-260-1-1--39.core6.t-2.net                        2.324ms asymm  3 
 5:  hurricane-electric.nikhef.nlsix.net                  35.904ms asymm  4 
 6:  be7.core2.fra2.he.net                                38.864ms asymm  5 
 7:  be3.core4.fra1.he.net                                41.977ms 
 8:  be1.core1.mil2.he.net                                32.967ms asymm  7 
 9:  no reply
10:  lo0-f1a01-itmil01.as57913.net                        33.741ms reached
     Resume: pmtu 1500 hops 10 back 7