AS overview
Test target: 2001:af8:36::36 · ns-too.tele.net · address space: PA · prefixes announced: 3
prefix(es): 2001:af8:36::/48, 2001:af8:35::/48, 2001:af8::/32
Targets & per-vantage-point probe results (2 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 / hostname | Source | SRB host (SOX, Belgrade) | DE host (Berlin) | DE host (Düsseldorf) | NL host (go6lab) | ITA host (Karsolink) | SLO host (6connect) | SLO host (T-2) | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ping | 1500B | :80 | :443 | reached | ping | 1500B | :80 | :443 | reached | ping | 1500B | :80 | :443 | reached | ping | 1500B | :80 | :443 | reached | ping | 1500B | :80 | :443 | reached | ping | 1500B | :80 | :443 | reached | ping | 1500B | :80 | :443 | reached | ||
2001:af8:35::35ns.tele.net | NS | ✗ | ✗ | ? | ? | ✓ | ✓ | ✓ | ? | ? | ✓ | ✓ | ✓ | ? | ? | ✓ | ✓ | ✗ | ? | ? | ✓ | ✓ | ✓ | ? | ? | ✓ | ✓ | ✓ | ? | ? | ✓ | ✓ | ✓ | ? | ? | ✓ |
2001:af8:36::36ns-too.tele.net | NS | ✓ | ✓ | ? | ? | ✓ | ✓ | ✓ | ? | ? | ✓ | ✓ | ✓ | ? | ? | ✓ | ✗ | ✗ | ? | ? | ✓ | ✓ | ✓ | ? | ? | ✓ | ✓ | ✓ | ? | ? | ✓ | ✓ | ✓ | ? | ? | ✓ |
VIX / AAIX / SAIX / TIROL-IX / ERA-IX peering
VIX / AAIX / SAIX / TIROL-IX / ERA-IX member - Selective peering, peering member, since 2026-05-28. IPv6 LAN: 2001:7f8:30:0:2:1:0:5358. Locations: -.
RPKI & ASPA
3 of 3 prefix(es) covered by a valid ROA.
| Prefix | RPKI state | Reason | Covering VRP(s) |
|---|---|---|---|
2001:af8:36::/48 | ✓ valid | matched VRP (correct origin, length within maxLength) | AS5385 /48 maxLen 48 (ripe); AS5385 /32 maxLen 32 (ripe) |
2001:af8:35::/48 | ✓ valid | matched VRP (correct origin, length within maxLength) | AS5385 /48 maxLen 48 (ripe); AS5385 /32 maxLen 32 (ripe) |
2001:af8::/32 | ✓ valid | matched VRP (correct origin, length within maxLength) | AS5385 /32 maxLen 32 (ripe) |
Random-IP probe (yarrp) into the AS' prefixes
At least one router inside AS5385's announced prefix replied during the random-target probe. Hop(s): 2001:af8:3:802::251, 2001:af8:3:802::252. 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:
- SRB host (SOX, Belgrade): inconclusive: no Echo Reply to 1300-byte probe. (ICMPv6 Echo + forged PTB)
- DE host (Berlin): Type 2 honored. Forged PTB accepted; next response shrunk. (ICMPv6 Echo + forged PTB)
- DE host (Düsseldorf): Type 2 honored. Forged PTB accepted; next response shrunk. (ICMPv6 Echo + forged PTB)
- NL host (go6lab): Type 2 NOT honored. Forged PTB had no effect (filtered en route or stack ignored it). (ICMPv6 Echo + forged PTB)
- ITA host (Karsolink): Type 2 honored. Forged PTB accepted; next response shrunk. (ICMPv6 Echo + forged PTB)
- SLO host (6connect): Type 2 honored. Forged PTB accepted; next response shrunk. (ICMPv6 Echo + forged PTB)
- SLO host (T-2): Type 2 honored. Forged PTB accepted; next response shrunk. (ICMPv6 Echo + forged PTB)
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
| vantage | our source | your target | method | result | tested (UTC) |
|---|---|---|---|---|---|
| belgrade | 2a09:ab81::91 | 2001:af8:36::36 | icmp6-echo | no_echo | 2026-09-22T13:51:00Z |
| berlin | 2a06:d1c1:10b::cccc | 2001:af8:36::36 | icmp6-echo | honored | 2026-09-22T13:50:55Z |
| duseldorf | 2a06:d1c1:10d::aaaa | 2001:af8:36::36 | icmp6-echo | honored | 2026-09-22T13:50:56Z |
| go6lab | 2a00:8642:42::75 | 2001:af8:36::36 | icmp6-echo | not_honored | 2026-09-22T13:51:16Z |
| karsolink | 2a12:d8c0:105a:9001::a154 | 2001:af8:36::36 | icmp6-echo | honored | 2026-09-22T13:50:54Z |
| odin | 2607:fae0:a000::42 | 2001:af8:36::36 | icmp6-echo | honored | 2026-09-22T13:50:57Z |
| t2 | 2a01:261:313:b814:2a0:98ff:fe5b:13e4 | 2001:af8:36::36 | icmp6-echo | honored | 2026-09-22T13:50:57Z |
Attempt log (belgrade):
icmp6-echo→ no_echo: no Echo Reply to 1300-byte probedns-tcp→ inconclusive (reply 156 B before PTB): max DNS-over-TCP segment 156B; not big enough to test PMTU shrinktls→ no_tcp: TLS connect failedhttp→ no_tcp: tcp/80 not open
Attempt log (berlin):
icmp6-echo→ honored (honored by fragmenting its reply into 2 via the IPv6 Fragment Header, rather than resizing)dns-tcp→ inconclusive (reply 133 B before PTB): max DNS-over-TCP segment 133B; not big enough to test PMTU shrinktls→ no_tcp: TLS connect failedhttp→ no_tcp: tcp/80 not open
Attempt log (duseldorf):
icmp6-echo→ honored (honored by fragmenting its reply into 2 via the IPv6 Fragment Header, rather than resizing): natural Echo Reply at 1500B was already split into IPv6 fragments without our PTB intervention -- the destination's stack has a cached path MTU below 1500B from a previously-honored ICMPv6 Type 2, which is itself evidence that this destination honors PTB on this path.dns-tcp→ inconclusive (reply 156 B before PTB): max DNS-over-TCP segment 156B; not big enough to test PMTU shrinktls→ no_tcp: TLS connect failedhttp→ no_tcp: tcp/80 not open
Attempt log (go6lab):
icmp6-echo→ not_honored (reply shrank 1460→1460 B)dns-tcp→ inconclusive (reply 175 B before PTB): max DNS-over-TCP segment 175B; not big enough to test PMTU shrinktls→ no_tcp: TLS connect failedhttp→ no_tcp: tcp/80 not open
Attempt log (karsolink):
icmp6-echo→ honored (honored by fragmenting its reply into 2 via the IPv6 Fragment Header, rather than resizing)dns-tcp→ inconclusive (reply 156 B before PTB): max DNS-over-TCP segment 156B; not big enough to test PMTU shrinktls→ no_tcp: TLS connect failedhttp→ no_tcp: tcp/80 not open
Attempt log (odin):
icmp6-echo→ honored (honored by fragmenting its reply into 2 via the IPv6 Fragment Header, rather than resizing): natural Echo Reply at 1500B was already split into IPv6 fragments without our PTB intervention -- the destination's stack has a cached path MTU below 1500B from a previously-honored ICMPv6 Type 2, which is itself evidence that this destination honors PTB on this path.dns-tcp→ inconclusive (reply 156 B before PTB): max DNS-over-TCP segment 156B; not big enough to test PMTU shrinktls→ no_tcp: TLS connect failedhttp→ no_tcp: tcp/80 not open
Attempt log (t2):
icmp6-echo→ honored (honored by fragmenting its reply into 2 via the IPv6 Fragment Header, rather than resizing)dns-tcp→ inconclusive (reply 156 B before PTB): max DNS-over-TCP segment 156B; not big enough to test PMTU shrinktls→ no_tcp: TLS connect failedhttp→ no_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 1460 B; after, it was 1460 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
- 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.
- 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.
- 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-22T13:51:16Z) 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):
- belgrade: probe
icmp6-echo→ verdictno_echo - berlin: probe
icmp6-echo→ verdicthonored - duseldorf: probe
icmp6-echo→ verdicthonored - go6lab: probe
icmp6-echo→ verdictnot_honored - karsolink: probe
icmp6-echo→ verdicthonored - odin: probe
icmp6-echo→ verdicthonored - t2: probe
icmp6-echo→ verdicthonored
Full per-method matrix (all four methods run at each vantage):
| vantage | icmp6-echo | dns-tcp | tls | http |
|---|---|---|---|---|
| belgrade | no_echo | inconclusive | no_tcp | no_tcp |
| berlin | honored | inconclusive | no_tcp | no_tcp |
| duseldorf | honored | inconclusive | no_tcp | no_tcp |
| go6lab | not_honored | inconclusive | no_tcp | no_tcp |
| karsolink | honored | inconclusive | no_tcp | no_tcp |
| odin | honored | inconclusive | no_tcp | no_tcp |
| t2 | honored | inconclusive | no_tcp | no_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): AS5385, AS201011, AS9002.
- From belgrade (open/Type-2=no_echo) the path enters an opaque hop at hop 12; from berlin (open/Type-2=honored) the same hop is in AS5385. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From belgrade (open/Type-2=no_echo) the path enters an opaque hop at hop 12; from duseldorf (open/Type-2=honored) the same hop is in AS5385. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From belgrade (open/Type-2=no_echo) the path enters AS5385 at hop 5; from go6lab (echo_only/Type-2=not_honored) the same hop is in AS9002. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From belgrade (open/Type-2=no_echo) the path enters an opaque hop at hop 10; from karsolink (open/Type-2=honored) the same hop is in AS5385. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From belgrade (open/Type-2=no_echo) the path enters AS5385 at hop 4; from odin (open/Type-2=honored) the same hop is in AS5603. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From belgrade (open/Type-2=no_echo) the path enters an opaque hop at hop 11; from t2 (open/Type-2=honored) the same hop is in AS5385. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From berlin (open/Type-2=honored) the path enters AS201011 at hop 8; from go6lab (echo_only/Type-2=not_honored) the same hop is in AS5385. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From berlin (open/Type-2=honored) the path enters AS201011 at hop 10; from karsolink (open/Type-2=honored) the same hop is in AS5385. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From berlin (open/Type-2=honored) the path enters AS201011 at hop 9; from odin (open/Type-2=honored) the same hop is in AS5385. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From berlin (open/Type-2=honored) the path enters AS201011 at hop 11; from t2 (open/Type-2=honored) the same hop is in AS5385. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From duseldorf (open/Type-2=honored) the path enters AS201011 at hop 8; from go6lab (echo_only/Type-2=not_honored) the same hop is in AS5385. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From duseldorf (open/Type-2=honored) the path enters AS201011 at hop 10; from karsolink (open/Type-2=honored) the same hop is in AS5385. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From duseldorf (open/Type-2=honored) the path enters AS201011 at hop 9; from odin (open/Type-2=honored) the same hop is in AS5385. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From duseldorf (open/Type-2=honored) the path enters AS201011 at hop 11; from t2 (open/Type-2=honored) the same hop is in AS5385. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From go6lab (echo_only/Type-2=not_honored) the path enters AS5385 at hop 7; from karsolink (open/Type-2=honored) the same hop is in AS201011. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From go6lab (echo_only/Type-2=not_honored) the path enters AS203993 at hop 3; from odin (open/Type-2=honored) the same hop is in AS5603. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From go6lab (echo_only/Type-2=not_honored) the path enters an opaque hop at hop 11; from t2 (open/Type-2=honored) the same hop is in AS5385. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From karsolink (open/Type-2=honored) the path enters AS201011 at hop 9; from odin (open/Type-2=honored) the same hop is in AS5385. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From karsolink (open/Type-2=honored) the path enters AS5385 at hop 10; from t2 (open/Type-2=honored) the same hop is in AS201011. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
- From odin (open/Type-2=honored) the path enters AS5385 at hop 9; from t2 (open/Type-2=honored) the same hop is in AS201011. Last common AS: AS5385. The disagreement is most likely rooted in one of those two transit ASes.
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
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 2001:af8:36::36
amsterdam - verdict ?
(no hops captured)
belgrade - verdict no_echo
verdict = no_echo; final pmtu = 1500
| # | hop IP | pmtu change |
|---|---|---|
| 1 | <span class='muted'>no reply</span> | |
| 2 | 2001:7f8:1e::4 | |
| 3 | 2001:7f8:30:0:2:1:0:5358 | |
| 4 | 2001:af8:3:802::251 | |
| 5 | 2001:af8:36::36 |
berlin - verdict honored
verdict = honored; final pmtu = 1500
| # | hop IP | pmtu change |
|---|---|---|
| 1 | <span class='muted'>no reply</span> | |
| 2 | 2a06:d1c0::dead:beef:1c02 | |
| 3 | 2a00:c380:b200:230::192 | |
| 4 | 2a00:c380:b200:230::45 | |
| 5 | 2a00:c380:f000::4b | |
| 6 | 2a01:4a0:0:2087::33 | |
| 7 | 2a01:4a0:0:2071::4 | |
| 8 | 2a01:4a0:0:2021::4 | |
| 9 | 2a01:4a0:0:2019::37 | |
| 10 | 2a01:4a0:0:2020::40 | |
| 11 | 2a01:4a0:1338:1f6::2 | |
| 12 | 2001:af8:36::36 |
duseldorf - verdict honored
verdict = honored; final pmtu = 1500
| # | hop IP | pmtu change |
|---|---|---|
| 1 | <span class='muted'>no reply</span> | |
| 2 | 2001:4ba0:92f4:3::1 | |
| 3 | <span class='muted'>no reply</span> | |
| 4 | 2001:4ba0:ffe9:115::3 | |
| 5 | 2001:4ba0:ffe9:4f::1 | |
| 6 | 2001:4ba0:ffe9:44::2 | |
| 7 | 2a01:4a0:0:2071::4 | |
| 8 | 2a01:4a0:0:2021::4 | |
| 9 | 2a01:4a0:0:2019::37 | |
| 10 | 2a01:4a0:0:2020::40 | |
| 11 | 2a01:4a0:1338:1f6::2 | |
| 12 | 2001:af8:36::36 |
go6lab - verdict not_honored
verdict = not_honored; final pmtu = 1500
| # | hop IP | pmtu change |
|---|---|---|
| 1 | <span class='muted'>no reply</span> | |
| 2 | 2a00:8642:1000:f000::1 | |
| 3 | 2a00:8642:dc1:2::b | |
| 4 | 2001:7f8:1::a500:9002:1 | |
| 5 | 2a02:2d8:0:8813:232a::1 | |
| 6 | 2a02:2d8:0:8813:232a::2 | |
| 7 | 2001:af8:3:802::252 | |
| 8 | 2001:af8:36::36 |
karsolink - verdict honored
verdict = honored; final pmtu = 1500
| # | hop IP | pmtu change |
|---|---|---|
| 1 | <span class='muted'>no reply</span> | |
| 2 | 2a12:d8c0:109f:121::a1 | |
| 3 | 2a12:d8c0:101f:6::1 | |
| 4 | 2a03:b020:1:51::a | |
| 5 | 2a03:b020::224 | |
| 6 | 2001:7f8::8463:0:1 | |
| 7 | 2a01:4a0:0:2019::37 | |
| 8 | 2a01:4a0:0:2020::40 | |
| 9 | 2a01:4a0:1338:1f6::2 | |
| 10 | 2001:af8:36::36 |
odin - verdict honored
verdict = honored; final pmtu = 1500
| # | hop IP | pmtu change |
|---|---|---|
| 1 | <span class='muted'>no reply</span> | |
| 2 | 2607:fae0:a000:2::2 | |
| 3 | 2a00:ee1:800:9::1 | |
| 4 | 2a00:ee0:1:10::2 | |
| 5 | 2a00:ee0:1:15::2 | |
| 6 | 2a01:4a0:0:2019::37 | |
| 7 | 2a01:4a0:0:2020::40 | |
| 8 | 2a01:4a0:1338:1f6::2 | |
| 9 | 2001:af8:36::36 |
t2 - verdict honored
verdict = honored; final pmtu = 1500
| # | hop IP | pmtu change |
|---|---|---|
| 1 | <span class='muted'>no reply</span> | |
| 2 | 2a01:260:1::225 | |
| 3 | 2a01:260:1:1::9c | |
| 4 | 2001:7f8:13::a523:3891:1 | |
| 5 | 2001:7f8:13::a523:3891:1 | |
| 6 | 2a01:4a0:0:2074::3 | |
| 7 | 2a01:4a0:0:2019::37 | |
| 8 | 2a01:4a0:0:2019::37 | |
| 9 | 2a01:4a0:0:2020::40 | |
| 10 | 2a01:4a0:1338:1f6::2 | |
| 11 | 2001:af8:36::36 |
Target 2001:af8:35::35
amsterdam - verdict ?
(no hops captured)
belgrade - verdict not_honored
verdict = not_honored; final pmtu = 1500
| # | hop IP | pmtu change |
|---|---|---|
| 1 | <span class='muted'>no reply</span> | |
| 2 | 2001:7f8:1e::4 | |
| 3 | 2001:7f8:30:0:2:1:0:5358 | |
| 4 | 2001:af8:3:802::251 | |
| 5 | 2001:af8:35::35 |
berlin - verdict honored
verdict = honored; final pmtu = 1500
| # | hop IP | pmtu change |
|---|---|---|
| 1 | <span class='muted'>no reply</span> | |
| 2 | 2a06:d1c0::dead:beef:1c02 | |
| 3 | 2a00:c380:b200:230::192 | |
| 4 | 2a00:c380:b200:230::45 | |
| 5 | 2a00:c380:f000::4b | |
| 6 | 2a01:4a0:0:2087::33 | |
| 7 | 2a01:4a0:0:2071::4 | |
| 8 | 2a01:4a0:0:2021::4 | |
| 9 | 2a01:4a0:0:2019::37 | |
| 10 | 2a01:4a0:0:2020::40 | |
| 11 | 2a01:4a0:1338:1f6::2 | |
| 12 | 2001:af8:35::35 |
duseldorf - verdict honored
verdict = honored; final pmtu = 1500
| # | hop IP | pmtu change |
|---|---|---|
| 1 | <span class='muted'>no reply</span> | |
| 2 | 2001:4ba0:92f4:3::1 | |
| 3 | <span class='muted'>no reply</span> | |
| 4 | 2001:4ba0:ffe9:115::3 | |
| 5 | 2001:4ba0:ffe9:8::2 | |
| 6 | 2001:4ba0:ffe9:44::2 | |
| 7 | 2a01:4a0:0:2071::4 | |
| 8 | 2a01:4a0:0:2021::4 | |
| 9 | 2a01:4a0:0:2019::37 | |
| 10 | 2a01:4a0:0:2020::40 | |
| 11 | 2a01:4a0:1338:1f6::2 | |
| 12 | 2001:af8:35::35 |
go6lab - verdict not_honored
verdict = not_honored; final pmtu = 1500
| # | hop IP | pmtu change |
|---|---|---|
| 1 | <span class='muted'>no reply</span> | |
| 2 | 2a00:8642:1000:f000::1 | |
| 3 | 2a00:8642:dc1:2::b | |
| 4 | 2001:7f8:1::a500:9002:1 | |
| 5 | 2a02:2d8:0:8813:232a::1 | |
| 6 | 2a02:2d8:0:8813:232a::2 | |
| 7 | 2001:af8:3:802::251 | |
| 8 | 2001:af8:35::35 |
karsolink - verdict honored
verdict = honored; final pmtu = 1500
| # | hop IP | pmtu change |
|---|---|---|
| 1 | <span class='muted'>no reply</span> | |
| 2 | 2a12:d8c0:109f:121::a1 | |
| 3 | 2a12:d8c0:101f:6::1 | |
| 4 | 2a03:b020:1:51::a | |
| 5 | 2a03:b020::224 | |
| 6 | 2001:7f8::8463:0:1 | |
| 7 | 2a01:4a0:0:2019::37 | |
| 8 | 2a01:4a0:0:2020::40 | |
| 9 | 2a01:4a0:1338:1f6::2 | |
| 10 | 2001:af8:35::35 |
odin - verdict honored
verdict = honored; final pmtu = 1500
| # | hop IP | pmtu change |
|---|---|---|
| 1 | <span class='muted'>no reply</span> | |
| 2 | 2607:fae0:a000:2::2 | |
| 3 | 2a00:ee1:800:9::1 | |
| 4 | 2a00:ee0:1:15::2 | |
| 5 | 2a00:ee0:1:15::2 | |
| 6 | 2a01:4a0:0:2019::37 | |
| 7 | 2a01:4a0:0:2020::40 | |
| 8 | 2a01:4a0:1338:1f6::2 | |
| 9 | 2001:af8:35::35 |
t2 - verdict honored
verdict = honored; final pmtu = 1500
| # | hop IP | pmtu change |
|---|---|---|
| 1 | <span class='muted'>no reply</span> | |
| 2 | 2a01:260:1::225 | |
| 3 | 2a01:260:1:1::9c | |
| 4 | 2001:7f8:13::a523:3891:1 | |
| 5 | 2a01:4a0:0:2074::3 | |
| 6 | 2a01:4a0:0:2021::4 | |
| 7 | 2a01:4a0:0:2021::4 | |
| 8 | 2a01:4a0:0:2020::40 | |
| 9 | 2a01:4a0:1338:1f6::2 | |
| 10 | 2001:af8:35::35 |
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 ↗
- ● SRB host (SOX, Belgrade)
- ● DE host (Berlin)
- ● DE host (Düsseldorf)
- ● NL host (go6lab)
- ● ITA host (Karsolink)
- ● SLO host (6connect)
- ● SLO host (T-2)
- ── solid line = echo reply, PTB honored (clean reach)
- — — dashed line = echo reply but PTB not honored (RFC 4890 violation)
- no line = no echo reply (never reached)
- ◉ target: green = clean, amber = reachable-but-violation / unreachable
- ⚠ suspected drop AS
- ⋯ silent (unanswered) hops
- ● IXP hop
From SRB host (SOX, Belgrade) open
filter likely at: (none) · min PMTU on path: 1500
Path (traceroute + mtr + PTR)
| # | IP / PTR | RTT | mtr loss | AS | AS holder |
|---|---|---|---|---|---|
| 1 | 2a09:ab81::1 | 0.2ms | 0%* | AS60733 | PERKE-NET - ZORAN PEROVIC trading as Agencija Perke.NET, RS |
| 2 | 2001:7f8:1e::4 | 0.4ms | 0% | AS13004 | SOX - Serbian Open Exchange DOO, RS |
| 3 | vix1.tele.net @VIX / AAIX / SAIX / TIROL-IX / ERA-IX 2001:7f8:30:0:2:1:0:5358 | 24.7ms | 0% | - | NA |
| 4 | 2001:af8:3:802::252 | 25.2ms | 0% | AS5385 | RUSSMEDIA-IT - Russmedia IT GmbH, AT |
| 5 | ns-too.tele.net 2001:af8:36::36 | 25.8ms | 0% | AS5385 | RUSSMEDIA-IT - Russmedia IT GmbH, AT |
tracepath -6
1?: [LOCALHOST] 0.019ms pmtu 1500
1: _gateway 0.918ms
1: _gateway 0.604ms
2: 2001:7f8:1e::4 1.993ms
3: vix1.tele.net 25.315ms asymm 11
4: 2001:af8:3:802::252 27.071ms asymm 12
5: ns-too.tele.net 24.782ms !A
Resume: pmtu 1500 From DE host (Berlin) openRFC 4890 ✓
filter likely at: (none) · min PMTU on path: 1500
Path (traceroute + mtr + PTR)
| # | IP / PTR | RTT | mtr loss | AS | AS holder |
|---|---|---|---|---|---|
| 1 | xe-0-0-13-178.gw01.ber01.as59645.net 2a06:d1c1:100:b::1 | 0.2ms | 0%* | AS59645 | WYBT-NET - Tobias Fiebig, DE |
| 2 | ae0-2453.cr10.ber01.lwlcom.net 2a06:d1c0::dead:beef:1c02 | 0.5ms | 0%* | AS59645 | WYBT-NET - Tobias Fiebig, DE |
| 3 | ae3-90.cr10.ham01.lwlcom.net 2a00:c380:b200:230::192 | 4.7ms | 0% | AS50629 | LWLCOM - LWLcom GmbH, DE |
| 4 | ae0-50.cr11.ham01.lwlcom.net 2a00:c380:b200:230::45 | 5.0ms | 0% | AS50629 | LWLCOM - LWLcom GmbH, DE |
| 5 | 2a00:c380:f000::4b | 5.2ms | 0% | AS50629 | LWLCOM - LWLcom GmbH, DE |
| 6 | ae4-2087.dus10.core-backbone.com 2a01:4a0:0:2087::33 | 11.2ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 7 | ae21-2071.fra10.core-backbone.com 2a01:4a0:0:2071::4 | 10.7ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 8 | ae2-2021.fra20.core-backbone.com 2a01:4a0:0:2021::4 | 10.5ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 9 | ae1-2019.bas10.core-backbone.com 2a01:4a0:0:2019::37 | 15.5ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 10 | ae8-2020.zur10.core-backbone.com 2a01:4a0:0:2020::40 | 16.6ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 11 | 2a01:4a0:1338:1f6::2 | 18.0ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 12 | ns-too.tele.net 2001:af8:36::36 | 16.9ms | 0% | AS5385 | RUSSMEDIA-IT - Russmedia IT GmbH, AT |
tracepath -6
1?: [LOCALHOST] 0.027ms pmtu 1500
1: xe-0-0-13-178.gw01.ber01.as59645.net 1.049ms
1: xe-0-0-13-178.gw01.ber01.as59645.net 0.781ms
2: ae0-2453.cr10.ber01.lwlcom.net 1.467ms
3: ae3-90.cr10.ham01.lwlcom.net 5.441ms
4: ae0-50.cr11.ham01.lwlcom.net 5.546ms
5: 2a00:c380:f000::4b 6.184ms asymm 4
6: ae4-2087.dus10.core-backbone.com 11.885ms asymm 5
7: ae21-2071.fra10.core-backbone.com 11.609ms asymm 5
8: ae2-2021.fra20.core-backbone.com 11.414ms asymm 4
9: ae1-2019.bas10.core-backbone.com 16.057ms asymm 5
10: ae8-2020.zur10.core-backbone.com 17.057ms asymm 6
11: 2a01:4a0:1338:1f6::2 18.000ms asymm 7
12: ns-too.tele.net 17.131ms !A
Resume: pmtu 1500 From DE host (Düsseldorf) openRFC 4890 ✓
filter likely at: (none) · min PMTU on path: 1500
Path (traceroute + mtr + PTR)
| # | IP / PTR | RTT | mtr loss | AS | AS holder |
|---|---|---|---|---|---|
| 1 | xe-0-0-12-142.gw01.dus01.as59645.net 2a06:d1c1:100:d::1 | 0.1ms | 0%* | AS59645 | WYBT-NET - Tobias Fiebig, DE |
| 2 | eth1-0-12-h5594.edge5-dus1.bb.wiit.network 2001:4ba0:92f4:3::1 | 1.5ms | 0% | AS24961 | MYLOC-AS - WIIT AG, DE |
| 3 | lag13.agr3-dus3.bb.wiit.network 2001:4ba0:ffe9:7d::1 | 6.9ms | 0% | AS24961 | MYLOC-AS - WIIT AG, DE |
| 4 | lag30.core3-dus1.bb.wiit.network 2001:4ba0:ffe9:109::2 | 0.2ms | 0% | AS24961 | MYLOC-AS - WIIT AG, DE |
| 5 | lag2.core1-dus-ix.bb.wiit.network 2001:4ba0:ffe9:4f::1 | 0.4ms | 0% | AS24961 | MYLOC-AS - WIIT AG, DE |
| 6 | core-backbone-dus-gw.bb.wiit.network 2001:4ba0:ffe9:44::2 | 10.1ms | 0% | AS24961 | MYLOC-AS - WIIT AG, DE |
| 7 | ae21-2071.fra10.core-backbone.com 2a01:4a0:0:2071::4 | 9.6ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 8 | ae2-2021.fra20.core-backbone.com 2a01:4a0:0:2021::4 | 9.5ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 9 | ae1-2019.bas10.core-backbone.com 2a01:4a0:0:2019::37 | 14.2ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 10 | ae8-2020.zur10.core-backbone.com 2a01:4a0:0:2020::40 | 15.4ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 11 | 2a01:4a0:1338:1f6::2 | 16.6ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 12 | ns-too.tele.net 2001:af8:36::36 | 15.5ms | 0% | AS5385 | RUSSMEDIA-IT - Russmedia IT GmbH, AT |
tracepath -6
1?: [LOCALHOST] 0.021ms pmtu 1500
1: xe-0-0-12-142.gw01.dus01.as59645.net 0.647ms
1: xe-0-0-12-142.gw01.dus01.as59645.net 1.159ms
2: eth1-0-12-h5594.edge5-dus1.bb.wiit.network 2.606ms
3: no reply
4: lag30.core3-dus1.bb.wiit.network 0.414ms
5: lag2.core1-dus-ix.bb.wiit.network 0.658ms
6: core-backbone-dus-gw.bb.wiit.network 10.453ms
7: ae21-2071.fra10.core-backbone.com 9.691ms asymm 6
8: ae2-2021.fra20.core-backbone.com 9.643ms asymm 5
9: ae1-2019.bas10.core-backbone.com 14.395ms asymm 6
10: ae8-2020.zur10.core-backbone.com 15.715ms asymm 7
11: 2a01:4a0:1338:1f6::2 16.629ms asymm 8
12: ns-too.tele.net 15.740ms !A
Resume: pmtu 1500 From NL host (go6lab) echo onlyRFC 4890 ✗
filter likely at: destination AS5385 (RUSSMEDIA-IT) · min PMTU on path: 1500
Path (traceroute + mtr + PTR)
| # | IP / PTR | RTT | mtr loss | AS | AS holder |
|---|---|---|---|---|---|
| 1 | 2a00:8642:42::2 | 0.7ms | 0% | AS203993 | GNA-DC1-AS - S.J.M. Steffann, NL |
| 2 | gw.friends.steffann.nl 2a00:8642:1000:f000::1 | 3.7ms | 0%* | AS203993 | GNA-DC1-AS - S.J.M. Steffann, NL |
| 3 | ccr2-ccr1.dc1.nogalliance.org 2a00:8642:dc1:2::b | 5.4ms | - | AS203993 | GNA-DC1-AS - S.J.M. Steffann, NL |
| 4 | ams-ix.retn.net 2001:7f8:1::a500:9002:1 | 5.8ms | 0% | - | NA |
| 5 | 2a02:2d8:0:8813:232a::1 | 15.3ms | 0% | AS9002 | RETN-AS - RETN Limited, GB |
| 6 | 2a02:2d8:0:8813:232a::2 | 18.4ms | 0% | AS9002 | RETN-AS - RETN Limited, GB |
| 7 | 2001:af8:3:802::252 | 19.5ms | 0% | AS5385 | RUSSMEDIA-IT - Russmedia IT GmbH, AT |
| 8 | ns-too.tele.net 2001:af8:36::36 | 17.3ms | - | AS5385 | RUSSMEDIA-IT - Russmedia IT GmbH, AT |
tracepath -6
1?: [LOCALHOST] 0.042ms pmtu 1500
1: 2a00:8642:42::2 2.231ms
1: 2a00:8642:42::2 2.663ms
2: no reply
3: no reply
4: ams-ix.retn.net 7.704ms asymm 7
5: 2a02:2d8:0:8813:232a::1 20.130ms asymm 6
6: 2a02:2d8:0:8813:232a::2 21.483ms asymm 7
7: 2001:af8:3:802::251 20.018ms asymm 8
8: ns-too.tele.net 26.326ms !A
Resume: pmtu 1500 From ITA host (Karsolink) openRFC 4890 ✓
filter likely at: (none) · min PMTU on path: 1500
Path (traceroute + mtr + PTR)
| # | IP / PTR | RTT | mtr loss | AS | AS holder |
|---|---|---|---|---|---|
| 1 | * | - | 0%* | - | |
| 2 | * | - | - | - | |
| 3 | 2a12:d8c0:101f:6::1 | 9.7ms | - | AS204471 | KARSOLINK - 2S Computers SRL, IT |
| 4 | 2a03:b020:1:51::a | 10.1ms | 0% | AS41327 | FIBERTELECOM-AS - Fiber Telecom S.p.A., IT |
| 5 | 2a03:b020::224 | 18.8ms | 0% | AS41327 | FIBERTELECOM-AS - Fiber Telecom S.p.A., IT |
| 6 | ae3-1.fra20.core-backbone.com 2001:7f8::8463:0:1 | 18.9ms | 0% | - | NA |
| 7 | ae1-2019.bas10.core-backbone.com 2a01:4a0:0:2019::37 | 23.8ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 8 | ae8-2020.zur10.core-backbone.com 2a01:4a0:0:2020::40 | 24.9ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 9 | 2a01:4a0:1338:1f6::2 | 26.1ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 10 | ns-too.tele.net 2001:af8:36::36 | 25.1ms | 0% | AS5385 | RUSSMEDIA-IT - Russmedia IT GmbH, AT |
tracepath -6
1?: [LOCALHOST] 0.028ms pmtu 1500
1: karsolink-01.net.karsolink.com 1.172ms
2: 2a12:d8c0:109f:121::a1 0.983ms
3: 2a12:d8c0:101f:6::1 10.492ms
4: 2a03:b020:1:51::a 11.080ms
5: 2a03:b020::224 19.564ms
6: ae3-1.fra20.core-backbone.com 19.589ms
7: ae1-2019.bas10.core-backbone.com 24.310ms
8: ae8-2020.zur10.core-backbone.com 25.400ms
9: 2a01:4a0:1338:1f6::2 26.193ms
10: ns-too.tele.net 25.560ms !A
Resume: pmtu 1500 From SLO host (6connect) openRFC 4890 ✓
filter likely at: (none) · min PMTU on path: 1500
Path (traceroute + mtr + PTR)
| # | IP / PTR | RTT | mtr loss | AS | AS holder |
|---|---|---|---|---|---|
| 1 | fw1-lju.6connect.com 2607:fae0:a000::2 | 0.2ms | 0%* | AS8038 | 6CONNECT - 6connect, Inc., US |
| 2 | * | - | - | - | |
| 3 | 2a00:ee1:800:9::1 | 2.9ms | - | AS5603 | SIOL-NET - Telekom Slovenije, d.d., SI |
| 4 | 2a00:ee0:1:15::2 | 1.1ms | 0% | AS5603 | SIOL-NET - Telekom Slovenije, d.d., SI |
| 5 | ae3-1.fra20.core-backbone.com 2001:7f8::8463:0:1 | 14.3ms | 0% | - | NA |
| 6 | ae1-2019.bas10.core-backbone.com 2a01:4a0:0:2019::37 | 18.6ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 7 | ae8-2020.zur10.core-backbone.com 2a01:4a0:0:2020::40 | 16.5ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 8 | 2a01:4a0:1338:1f6::2 | 17.6ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 9 | ns-too.tele.net 2001:af8:36::36 | 16.6ms | 0% | AS5385 | RUSSMEDIA-IT - Russmedia IT GmbH, AT |
tracepath -6
1?: [LOCALHOST] 0.036ms pmtu 9000
1: fw1-lju.6connect.com 0.545ms
1: fw1-lju.6connect.com 0.605ms
2: no reply
3: 2a00:ee1:800:9::1 2.019ms
4: 2a00:ee0:1:10::2 1.330ms asymm 3
5: 2a00:ee0:1:10::2 65.457ms pmtu 1500
5: ae3-1.fra20.core-backbone.com 14.372ms asymm 9
6: ae1-2019.bas10.core-backbone.com 19.049ms asymm 10
7: ae8-2020.zur10.core-backbone.com 16.879ms asymm 12
8: 2a01:4a0:1338:1f6::2 17.868ms asymm 13
9: ns-too.tele.net 17.024ms !A
Resume: pmtu 1500 From SLO host (T-2) openRFC 4890 ✓
filter likely at: (none) · min PMTU on path: 1500
Path (traceroute + mtr + PTR)
| # | IP / PTR | RTT | mtr loss | AS | AS holder |
|---|---|---|---|---|---|
| 1 | * | - | - | - | |
| 2 | * | - | 0%* | - | |
| 3 | * | - | 0%* | - | |
| 4 | * | - | 0% | - | |
| 5 | * | - | 0% | - | |
| 6 | * | - | 0% | - | |
| 7 | * | - | 0% | - | |
| 8 | * | - | 0% | - | |
| 9 | ae8-2020.zur10.core-backbone.com 2a01:4a0:0:2020::40 | 33.3ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 10 | 2a01:4a0:1338:1f6::2 | 35.0ms | 0% | AS201011 | CORE-BACKBONE - Core-Backbone GmbH, DE |
| 11 | ns-too.tele.net 2001:af8:36::36 | 28.9ms | - | AS5385 | RUSSMEDIA-IT - Russmedia IT GmbH, AT |
tracepath -6
1?: [LOCALHOST] 0.023ms pmtu 1500
1: 2a01:261:313:b814::1 0.754ms
1: no reply
2: 2a01:260:1::225 3.271ms
3: 2a01-260-1-1--9c.core6.t-2.net 3.264ms
4: 2a01-260-1-1--39.core6.t-2.net 1.995ms asymm 3
5: ae16-2074.fra10.core-backbone.com 31.821ms asymm 9
6: ae2-2021.fra20.core-backbone.com 32.462ms asymm 8
7: ae1-2019.bas10.core-backbone.com 34.520ms asymm 10
8: ae8-2020.zur10.core-backbone.com 33.206ms
9: 2a01:4a0:1338:1f6::2 31.172ms
10: 2a01:4a0:1338:1f6::2 31.680ms asymm 9
11: ns-too.tele.net 30.442ms !A
Resume: pmtu 1500