bgpreport

Network · data from 2026-11-12

AS31042 Serbia BroadBand

Registry name: YETTEL-AS Yettel d.o.o., RS · PeeringDB

27IPv4 routes 81.5% RPKI valid · 96.3% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
3RPKI invalid 0 origin · 3 maxLength
2No ROA 1 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
32Route objects not announced registered with origin AS31042, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS31042, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

5.22.182.0/24 Invalid: maxLength RIR databaseRIPE 1 0%low visibility 1
5.22.186.0/24 Invalid: maxLength RIR databaseRIPE 1 0%low visibility 1
5.22.187.0/24 Invalid: maxLength RIR databaseRIPE 1 0%low visibility 1
176.106.120.0/21 No ROA RIR databaseRIPE 672 100% 66
176.108.32.0/20 No ROA RIR databaseRIPE 672 100% 66
82.117.195.0/24 Valid Nonecovered by 82.117.192.0/19 672 100% 66
5.22.188.0/24 Valid RIR databaseRIPE 673 100% 66
5.22.160.0/19 Valid RIR databaseRIPE 672 100% 66
46.17.144.0/21 Valid RIR databaseRIPE 672 100% 66
46.240.128.0/17 Valid RIR databaseRIPE 672 100% 66
80.93.224.0/19 Valid RIR databaseRIPE 672 100% 66
82.117.192.0/19 Valid RIR databaseRIPE 672 100% 66
87.116.128.0/18 Valid RIR databaseRIPE 672 100% 66
89.216.0.0/16 Valid RIR databaseRIPE 672 100% 66
89.216.128.0/17 Valid RIR databaseRIPE 672 100% 66
91.143.208.0/20 Valid RIR databaseRIPE 672 100% 66
94.127.0.0/21 Valid RIR databaseRIPE 672 100% 66
94.189.128.0/17 Valid RIR databaseRIPE 672 100% 66
94.230.176.0/20 Valid RIR databaseRIPE 672 100% 66
95.180.0.0/17 Valid RIR databaseRIPE 672 100% 66
178.148.0.0/15 Valid RIR databaseRIPE 672 100% 66
188.2.0.0/16 Valid RIR databaseRIPE 672 100% 66
188.246.32.0/19 Valid RIR databaseRIPE 672 100% 66
213.244.224.0/22 Valid RIR databaseRIPE 672 100% 66
217.26.208.0/21 Valid RIR databaseRIPE 672 100% 66
24.135.0.0/16 Valid RIR databaseRIPE 669 99% 66
89.216.0.0/17 Valid RIR databaseRIPE 669 99% 66
2a00:1dd8::/29 Valid RIR databaseRIPE 634 100% 67
2a03:87c0::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS31042: AS-SBB. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS31042 isn't in the set, or no route object for AS31042 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS31042 in itNot covered
AS-SBB RADB 2224 No 29
RIPE (also) 102103,332 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 39 are in fix.csv.

  • ROA: maxLength3
  • ROA: none2
  • Route object: none1
  • AS-SET: own ASN1
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: maxLength5.22.182.0/24ROA 5.22.160.0/19 AS31042 has maxLength 19; the route is a /24. Raise the maxLength, or add a ROA for 5.22.182.0/24.1 of 673
ROA: maxLength5.22.186.0/24ROA 5.22.160.0/19 AS31042 has maxLength 19; the route is a /24. Raise the maxLength, or add a ROA for 5.22.186.0/24.1 of 673
ROA: maxLength5.22.187.0/24ROA 5.22.160.0/19 AS31042 has maxLength 19; the route is a /24. Raise the maxLength, or add a ROA for 5.22.187.0/24.1 of 673
ROA: none176.106.120.0/21No ROA covers it. Add a ROA for AS31042, maxLength 21.672 of 673
ROA: none176.108.32.0/20No ROA covers it. Add a ROA for AS31042, maxLength 20.672 of 673
Route object: none82.117.195.0/24No route object for it. A route object for 82.117.192.0/19 with origin AS31042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31042 in the RIR database for the space.672 of 673
AS-SET: own ASNAS-SBBAS31042 isn't in AS-SBB (RADB) once expanded. Add AS31042 to it.

Route objects not announced

Route objects with origin AS31042 whose prefix no peer sees AS31042 announce. Many are kept on purpose (backup routes, space announced only in some places).

5.22.161.0/24RIPEValid
5.22.184.0/24RIPEValid
5.22.185.0/24RIPEValid
5.22.189.0/24RIPEValid
5.22.190.0/24RIPEValid
5.22.191.0/24RIPEValid
24.135.0.0/17RIPEValid
24.135.128.0/17RIPEValid
46.240.224.0/19RIPEInvalid: maxLength
80.93.224.0/20RIPEInvalid: maxLength
87.116.128.0/19RIPEValid
87.116.128.0/22RIPEValid
87.116.132.0/22RIPEValid
87.116.136.0/22RIPEValid
87.116.140.0/24RIPEValid
87.116.141.0/24RIPEValid
87.116.160.0/19RIPEValid
87.116.176.0/21RIPEValid
91.143.208.0/21RIPEInvalid: maxLength
91.238.61.0/24RIPENo ROA
94.189.128.0/18RIPEValid
94.189.192.0/18RIPEValid
95.180.0.0/22RIPEValid
178.148.0.0/16RIPEValid
178.149.0.0/16RIPEValid
185.12.43.0/24RIPEValid
185.20.36.0/24RIPEValid
185.20.37.0/24RIPEValid
188.2.0.0/17RIPEValid
188.2.128.0/17RIPEValid
2a00:1dd8::/32RIPEValid
2a04:1480::/29RIPENo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.