bgpreport

Network · data from 2026-11-12

AS198605 AVAST Software s.r.o.

Registry name: AVAST-AS-DC AVAST Software s.r.o., CZ · PeeringDB

22IPv4 routes 81.8% RPKI valid · 90.9% with a route object
8IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
3No ROA 2 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
85Route objects not announced registered with origin AS198605, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS198605, 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.

31.14.73.0/24 Invalid: origin Other origin only 0 0%low visibility 1
166.98.10.0/24 No ROA None 672 100% 67
166.98.8.0/24 No ROA RIR databaseARIN 673 100% 67
166.98.11.0/24 No ROA RIR databaseARIN 671 100% 67
5.45.58.0/24 Valid RIR databaseRIPE 673 100% 66
5.45.59.0/24 Valid RIR databaseRIPE 673 100% 66
5.62.36.0/23 Valid RIR databaseRIPE 673 100% 66
5.62.54.0/24 Valid RIR databaseRIPE 673 100% 66
5.62.60.0/23 Valid RIR databaseRIPE 673 100% 66
37.156.187.0/24 Valid RIR databaseRIPE 673 100% 66
69.94.64.0/24 Valid RIR databaseRIPE 673 100% 66
69.94.70.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
69.94.71.0/24 Valid RIR databaseRIPE 673 100% 66
69.94.74.0/23 Valid RIR databaseRIPE 673 100% 67
69.94.74.0/24 Valid RIR databaseRIPE 673 100% 66
69.94.75.0/24 Valid RIR databaseRIPE 673 100% 66
91.213.143.0/24 Valid RIR databaseRIPE 673 100% 66
185.189.92.0/24 Valid RIR databaseRIPE 673 100% 66
185.189.94.0/24 Valid RIR databaseRIPE 673 100% 66
185.189.95.0/24 Valid RIR databaseRIPE 673 100% 66
195.74.76.0/24 Valid RIR databaseRIPE 673 100% 66
77.234.40.0/24 Valid RIR databaseRIPE 672 100% 66
2001:67c:284::/48 Valid RIR databaseRIPE 636 100% 67
2a0b:e181::/40 Valid RIR databaseRIPE 636 100% 67
2a0b:e181:108::/45 Valid RIR databaseRIPE 636 100% 67
2a0b:e181:400::/40 Valid RIR databaseRIPE 636 100% 67
2a0b:e181:500::/40 Valid RIR databaseRIPE 636 100% 67
2a0b:e181:600::/40 Valid RIR databaseRIPE 636 100% 67
2a0b:e181:604::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:e181:605::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS198605's PeeringDB record names no AS-SET.

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 91 are in fix.csv.

  • ROA: origin1
  • ROA: none3
  • Route object: none2
  • Route object: not announced85
ChangePrefix or setDetailFull-table peers
ROA: origin31.14.73.0/24ROAs covering it name AS137409, not AS198605. If AS198605 should announce it, add a ROA for AS198605.0 of 673
Route object: none31.14.73.0/24Route objects for it name AS137409. Add a route object with origin AS198605 in the RIR database for the space.0 of 673
ROA: none166.98.10.0/24No ROA covers it. Add a ROA for AS198605, maxLength 24.672 of 673
Route object: none166.98.10.0/24No route object for it. Add a route object with origin AS198605 in the RIR database for the space.672 of 673
ROA: none166.98.8.0/24No ROA covers it. Add a ROA for AS198605, maxLength 24.673 of 673
ROA: none166.98.11.0/24No ROA covers it. Add a ROA for AS198605, maxLength 24.671 of 673

Route objects not announced

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

5.45.56.0/24RIPEValid
5.45.57.0/24RIPEValid
5.45.60.0/24RIPEValid
5.45.61.0/24RIPEValid
5.45.62.0/24RIPEValid
5.45.63.0/24RIPEValid
5.62.17.0/24RIPEValid
5.62.25.0/24RADB, RIPEValid
5.62.30.0/24RADB, RIPEValid
5.62.31.0/24RADBNo ROA
5.62.32.0/24RIPEValid
5.62.42.0/23RIPEValid
5.62.44.0/23RADB, RIPEValid
5.62.46.0/23RIPEValid
5.62.50.0/24RADB, RIPEValid
5.62.51.0/24RIPEInvalid: origin
5.62.52.0/24RIPEValid
5.62.53.0/24RIPEValid
5.62.55.0/24RADBValid
5.62.56.0/23RIPEValid
5.62.56.0/24RADB, RIPEValid
5.62.57.0/24RIPEValid
5.62.58.0/23RADBValid
5.62.62.0/23RADBValid
37.156.184.0/24RADB, RIPEValid
37.156.185.0/24RADB, RIPEValid
37.156.186.0/24RIPEValid
69.94.65.0/24RIPEValid
69.94.66.0/24RIPEValid
69.94.67.0/24RIPEValid
69.94.68.0/24RIPEValid
69.94.69.0/24RIPEValid
69.94.72.0/23RIPEValid
69.94.72.0/24RIPEValid
69.94.73.0/24RIPEValid
69.94.76.0/24RADB, RIPEValid
69.94.77.0/24RADB, RIPEValid
69.94.78.0/24RIPEValid
69.94.79.0/24RIPEValid
77.234.40.0/21RADBValid
77.234.41.0/24RIPEValid
77.234.42.0/24RIPEValid
77.234.43.0/24RIPEValid
77.234.44.0/24RIPEValid
77.234.45.0/24RIPEValid
77.234.46.0/24RIPEValid
77.234.47.0/24RIPEValid
159.242.224.0/23RIPENo ROA
159.242.226.0/23RIPENo ROA
159.242.227.0/24RADB, RIPEValid
159.242.232.0/23RIPEInvalid: origin
159.242.234.0/24RADB, RIPEValid
159.242.239.0/24RADBValid
185.51.228.0/22RADBValid
185.51.231.0/24RIPEValid
185.54.230.0/24RIPEValid
185.167.64.0/24RIPEValid
185.189.93.0/24RIPEValid
194.99.28.0/22RADB, RIPEValid
2001:67c:284:ff00::/56RIPEInvalid: maxLength
2a0b:e180::/29RIPEValid
2a0b:e181:100::/40RIPEValid
2a0b:e181:100::/42RIPEValid
2a0b:e181:140::/42RIPEValid
2a0b:e181:180::/42RIPEValid
2a0b:e181:1c0::/42RIPEValid
2a0b:e181:200::/40RIPEValid
2a0b:e181:300::/40RIPEValid
2a0b:e181:300::/42RADBValid
2a0b:e181:340::/42RADBValid
2a0b:e181:380::/42RADBValid
2a0b:e181:3c0::/42RADBValid
2a0b:e182:100::/40RIPEValid
2a0b:e182:100::/42RADB, RIPEValid
2a0b:e182:140::/42RADB, RIPEValid
2a0b:e182:180::/42RADB, RIPEValid
2a0b:e182:1c0::/42RADB, RIPEValid
2a0b:e182:200::/40RIPEValid
2a0b:e182:200::/45RIPEValid
2a0b:e182:300::/40RIPEValid
2a0b:e182:300::/42RADBValid
2a0b:e182:340::/42RADBValid
2a0b:e182:380::/42RADBValid
2a0b:e182:3c0::/42RADBValid
2a0b:e182:400::/40RIPEValid

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.