AS31042 - SERBIA-BROADBAND-AS Serbia BroadBand-Srpske Kablovske mrezePI/PARFC 4890 ✓RPKI ✓ 2/2ASPA -

← back to summary

All countriesHomeState of IPv6TopologySOXAboutipv6.si ↗ Sparky

AS overview

Test target: 2a03:87c0::1 · static prefix probe · address space: mixed · prefixes announced: 2

prefix(es): 2a00:1dd8::/29, 2a03:87c0::/29

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
2a03:87c0::1prb??-refusedrefused-refusedrefused-

SOX peering

SOX member - Open peering, peering member, since 2012-01-11. IPv6 LAN: -. Locations: -.

RPKI & ASPA

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

PrefixRPKI stateReasonCovering VRP(s)
2a03:87c0::/29✓ validmatched VRP (correct origin, length within maxLength)AS31042 /29 maxLen 29 (ripe)
2a00:1dd8::/29✓ validmatched VRP (correct origin, length within maxLength)AS31042 /29 maxLen 29 (ripe)

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

At least one router inside AS31042's announced prefix replied during the random-target probe. Hop(s): 2a00:1dd8:2:1::, 2a00:1dd8:2:24::1, 2a00:1dd8:2:25::1, 2a00:1dd8:2:26::1, 2a00:1dd8:2:27::1. 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 - 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::752a03:87c0::1icmp6-echohonored2026-05-30T11:30:01Z
karsolink2a12:d8c0:105a:9001::a1542a03:87c0::1icmp6-echono_echo2026-05-30T11:31:29Z
odin2607:fae0:a000::422a03:87c0::1icmp6-echohonored2026-05-30T11:29:53Z

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: [Errno 111] Connection refused
  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): 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.
  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 ASes (ranked by how often they appear at the divergence point on the path of the worse-classifying vantage): AS9002, AS6939.

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)
4*-- (no IP)
52001:470:0:578::1AS6939HURRICANE - Hurricane Electric LLC, US? no_response
62001:470:0:7ef::1AS6939HURRICANE - Hurricane Electric LLC, US? no_response
72001:470:e:5a::2AS6939HURRICANE - Hurricane Electric LLC, US? no_response
8*-- (no IP)
92001:7f8::7942:0:2-NA? no_response
102a00:1dd8:2:4-- (invalid IP)
112a00:1dd8:2:25::1AS31042SERBIA-BROADBAND-AS - Yettel d.o.o., RS? no_response
122a00:1dd8:2:c000::1AS31042SERBIA-BROADBAND-AS - Yettel d.o.o., RS? 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) 31.1ms
4/4
Echo 1500B (DF) 36.4ms
yes
Type 1 dest-unreach
-
TCP responds on

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
12a00:8642:42::30.7ms0%AS203993STEFFANN-DC-AS - S.J.M. Steffann, NL
2*-0%*-
32a00:1ca8:1::1942.8ms0%AS50673Serverius-as - Serverius Holding B.V., NL
42a03:3f40::10:335.1ms0%AS50673Serverius-as - Serverius Holding B.V., NL
52a02:2d8:1:a001:232a4.5ms0%-
6RT.EQX.FKT.DE.retn.net
2a02:2d8::57f5:e0a2
10.1ms20%AS9002RETN-AS - RETN Limited, GB
72001:7f8::7942:0:232.2ms0%-NA
82a00:1dd8:2:130.2ms0%-
9bg-ne-m-10-be2.sbb.rs
2a00:1dd8:2:27::1
30.2ms0%AS31042SERBIA-BROADBAND-AS - Yettel d.o.o., RS
10bg-tp-c-1-po2.sbb.rs
2a00:1dd8:2:c001::1
31.1ms0%AS31042SERBIA-BROADBAND-AS - Yettel d.o.o., RS

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

tracepath -6

 1?: [LOCALHOST]                        0.041ms pmtu 1500
 1:  2a00:8642:42::3                                       1.123ms 
 1:  2a00:8642:42::3                                       1.357ms 
 2:  gw.friends.steffann.nl                                2.507ms 
 3:  2a00:1ca8:1::194                                      2.997ms 
 4:  2a03:3f40::10:33                                      4.769ms 
 5:  ae1-499.RT.SRV.DRO.NL.retn.net                        5.204ms 
 6:  RT.EQX.FKT.DE.retn.net                               10.523ms asymm  8 
 7:  2001:7f8::7942:0:2                                   31.956ms 
 8:  bg-ne-m-0-be16.sbb.rs                                32.572ms asymm  9 
 9:  bg-ne-m-10-be2.sbb.rs                                32.239ms 
10:  bg-tp-c-1-po2.sbb.rs                                 39.124ms reached
     Resume: pmtu 1500 hops 10 back 11 

From ITA host (Karsolink)   open

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

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

Path (traceroute + mtr + PTR)

#IP / PTRRTTmtr lossASAS holder
1*---
2*---
32a12:d8c0:101f:103::18.4ms0%AS204471KARSOLINK - 2S Computers SRL, IT
42a02:2d8:1:b80d:232a7.7ms0%-
5RT.EQX.FKT.DE.retn.net
2a02:2d8::57f5:e0a2
19.4ms10%AS9002RETN-AS - RETN Limited, GB
6*---
72a00:1dd8:2:441.6ms0%-
8bg-tp-m-10-be2.sbb.rs
2a00:1dd8:2:25::1
40.3ms0%AS31042SERBIA-BROADBAND-AS - Yettel d.o.o., RS
9bg-tp-c-1-po1.sbb.rs
2a00:1dd8:2:c000::1
40.8ms10%AS31042SERBIA-BROADBAND-AS - Yettel d.o.o., RS

Rate-limited ICMPv6: hop 5, hop 9 (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.746ms 
 2:  2a12:d8c0:109f:121::a1                                0.940ms 
 3:  2a12:d8c0:101f:103::1                                 8.707ms 
 4:  ae8-202.rt.clr.mil.it.retn.net                        8.172ms asymm  5 
 5:  rt.eqx.fkt.de.retn.net                               20.228ms 
 6:  no reply
 7:  bg-ne-m-0-be16.sbb.rs                                42.140ms asymm  9 
 8:  bg-tp-m-10-be2.sbb.rs                                40.843ms asymm 10 
 9:  bg-tp-c-1-po2.sbb.rs                                 43.383ms reached
     Resume: pmtu 1500 hops 9 back 11 

From SLO host (6connect)   openRFC 4890 ✓

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

4/4
Echo small (56B) 19.9ms
3/4
Echo 1500B (DF) 21.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.3ms0%*AS80386CONNECT - 6connect, Inc., US
2*-0%*-
3*-90%-
4*-0%-
5100ge0-0-0-5.core1.vie1.he.net
2001:470:0:578::1
7.4ms0%AS6939HURRICANE - Hurricane Electric LLC, US
6100ge0-0-0-19.core2.fra2.he.net
2001:470:0:7ef::1
19.3ms0%AS6939HURRICANE - Hurricane Electric LLC, US
7be3.core4.fra1.he.net
2001:470:e:5a::2
19.6ms0%AS6939HURRICANE - Hurricane Electric LLC, US
8*-0%-
92001:7f8::7942:0:238.9ms--NA
102a00:1dd8:2:424.8ms--
11bg-tp-m-10-be2.sbb.rs
2a00:1dd8:2:25::1
25.9ms-AS31042SERBIA-BROADBAND-AS - Yettel d.o.o., RS
12bg-tp-c-1-po1.sbb.rs
2a00:1dd8:2:c000::1
37.5ms-AS31042SERBIA-BROADBAND-AS - Yettel d.o.o., RS

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

tracepath -6

 1?: [LOCALHOST]                        0.031ms pmtu 1500
 1:  fw1-lju.6connect.com                                  0.533ms 
 1:  fw1-lju.6connect.com                                  0.561ms 
 2:  ccr-to-fw-ccr1-gw-lju.6connect.com                    0.711ms 
 3:  2a03:a100:0:201:1::1                                  0.680ms 
 4:  2001:7f8:46::2:1215                                   9.583ms 
 5:  2a03:dd80:2::1                                       24.228ms asymm 10 
 6:  bg-tp-m-0-be3.sbb.rs                                 23.212ms asymm 11 
 7:  bg-ne-m-10-be1.sbb.rs                                23.763ms asymm 12 
 8:  bg-tp-c-1-po2.sbb.rs                                 12.345ms reached
     Resume: pmtu 1500 hops 8 back 8