Network · data from 2026-11-12
AS31042 Serbia BroadBand
Registry name: YETTEL-AS Yettel d.o.o., RS · PeeringDB
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 |
| 5.22.186.0/24 | Invalid: maxLength | RIR databaseRIPE | 1 0%low visibility |
| 5.22.187.0/24 | Invalid: maxLength | RIR databaseRIPE | 1 0%low visibility |
| 176.106.120.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 176.108.32.0/20 | No ROA | RIR databaseRIPE | 672 100% |
| 82.117.195.0/24 | Valid | Nonecovered by 82.117.192.0/19 | 672 100% |
| 5.22.188.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.22.160.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 46.17.144.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 46.240.128.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 80.93.224.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 82.117.192.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 87.116.128.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 89.216.0.0/16 | Valid | RIR databaseRIPE | 672 100% |
| 89.216.128.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 91.143.208.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 94.127.0.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 94.189.128.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 94.230.176.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 95.180.0.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 178.148.0.0/15 | Valid | RIR databaseRIPE | 672 100% |
| 188.2.0.0/16 | Valid | RIR databaseRIPE | 672 100% |
| 188.246.32.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 213.244.224.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 217.26.208.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 24.135.0.0/16 | Valid | RIR databaseRIPE | 669 99% |
| 89.216.0.0/17 | Valid | RIR databaseRIPE | 669 99% |
| 2a00:1dd8::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a03:87c0::/29 | Valid | RIR databaseRIPE | 634 100% |
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.
| Name | Database | ASNs | Sets | AS31042 in it | Not covered |
|---|---|---|---|---|---|
| AS-SBB | RADB | 2 | 2 | No | 29 |
| RIPE (also) | 102 | 10 | 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
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 5.22.182.0/24 | ROA 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. |
| ROA: maxLength | 5.22.186.0/24 | ROA 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. |
| ROA: maxLength | 5.22.187.0/24 | ROA 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. |
| ROA: none | 176.106.120.0/21 | No ROA covers it. Add a ROA for AS31042, maxLength 21. |
| ROA: none | 176.108.32.0/20 | No ROA covers it. Add a ROA for AS31042, maxLength 20. |
| Route object: none | 82.117.195.0/24 | No 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. |
| AS-SET: own ASN | AS-SBB | AS31042 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/24 | RIPE | Valid |
| 5.22.184.0/24 | RIPE | Valid |
| 5.22.185.0/24 | RIPE | Valid |
| 5.22.189.0/24 | RIPE | Valid |
| 5.22.190.0/24 | RIPE | Valid |
| 5.22.191.0/24 | RIPE | Valid |
| 24.135.0.0/17 | RIPE | Valid |
| 24.135.128.0/17 | RIPE | Valid |
| 46.240.224.0/19 | RIPE | Invalid: maxLength |
| 80.93.224.0/20 | RIPE | Invalid: maxLength |
| 87.116.128.0/19 | RIPE | Valid |
| 87.116.128.0/22 | RIPE | Valid |
| 87.116.132.0/22 | RIPE | Valid |
| 87.116.136.0/22 | RIPE | Valid |
| 87.116.140.0/24 | RIPE | Valid |
| 87.116.141.0/24 | RIPE | Valid |
| 87.116.160.0/19 | RIPE | Valid |
| 87.116.176.0/21 | RIPE | Valid |
| 91.143.208.0/21 | RIPE | Invalid: maxLength |
| 91.238.61.0/24 | RIPE | No ROA |
| 94.189.128.0/18 | RIPE | Valid |
| 94.189.192.0/18 | RIPE | Valid |
| 95.180.0.0/22 | RIPE | Valid |
| 178.148.0.0/16 | RIPE | Valid |
| 178.149.0.0/16 | RIPE | Valid |
| 185.12.43.0/24 | RIPE | Valid |
| 185.20.36.0/24 | RIPE | Valid |
| 185.20.37.0/24 | RIPE | Valid |
| 188.2.0.0/17 | RIPE | Valid |
| 188.2.128.0/17 | RIPE | Valid |
| 2a00:1dd8::/32 | RIPE | Valid |
| 2a04:1480::/29 | RIPE | No 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.