bgpreport

Network · data from 2026-11-12

AS42232 PARISAT PARISAT Tavkozlesi es Szolgaltato Korlatolt Felelossegu Tarsasag

Registry name: PARISAT PARISAT Tavkozlesi es Szolgaltato Korlatolt Felelossegu Tarsasag, HU · not in PeeringDB

22IPv4 routes 54.5% RPKI valid · 95.5% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
9No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS42232, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS42232, 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.
213.181.221.0/24 Invalid: origin Other origin only 10 1%low visibility 12
31.24.17.0/24 No ROA RIR databaseRIPE 672 100% 67
31.24.18.0/24 No ROA RIR databaseRIPE 672 100% 67
31.24.19.0/24 No ROA RIR databaseRIPE 672 100% 67
31.24.20.0/24 No ROA RIR databaseRIPE 672 100% 67
31.24.21.0/24 No ROA RIR databaseRIPE 672 100% 67
31.24.22.0/24 No ROA RIR databaseRIPE 672 100% 67
31.24.23.0/24 No ROA RIR databaseRIPE 672 100% 67
93.190.2.0/24 No ROA RIR databaseRIPE 672 100% 67
139.28.196.0/22 No ROA RIR databaseRIPE 672 100% 66
46.251.0.0/21 Valid RIR databaseRIPE 672 100% 67
79.121.82.0/23 Valid RIR databaseRIPE 672 100% 67
88.87.248.0/22 Valid RIR databaseRIPE 672 100% 67
88.87.252.0/22 Valid RIR databaseRIPE 672 100% 67
91.83.112.0/21 Valid RIR databaseRIPE 672 100% 67
91.147.200.0/22 Valid RIR databaseRIPE 672 100% 66
91.147.204.0/22 Valid RIR databaseRIPE 672 100% 66
91.147.224.0/21 Valid RIR databaseRIPE 672 100% 67
91.147.248.0/22 Valid RIR databaseRIPE 672 100% 66
91.147.252.0/22 Valid RIR databaseRIPE 672 100% 66
94.248.160.0/21 Valid RIR databaseRIPE 672 100% 66
213.163.9.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS42232 isn't in PeeringDB, where networks name their 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 14 are in fix.csv.

  • ROA: origin1
  • ROA: none9
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin213.181.221.0/24ROAs covering it name AS29278, not AS42232. If AS42232 should announce it, add a ROA for AS42232.10 of 673
Route object: none213.181.221.0/24Route objects for it name AS29278. Add a route object with origin AS42232 in the RIR database for the space.10 of 673
ROA: none31.24.17.0/24No ROA covers it. Add a ROA for AS42232, maxLength 24.672 of 673
ROA: none31.24.18.0/24No ROA covers it. Add a ROA for AS42232, maxLength 24.672 of 673
ROA: none31.24.19.0/24No ROA covers it. Add a ROA for AS42232, maxLength 24.672 of 673
ROA: none31.24.20.0/24No ROA covers it. Add a ROA for AS42232, maxLength 24.672 of 673
ROA: none31.24.21.0/24No ROA covers it. Add a ROA for AS42232, maxLength 24.672 of 673
ROA: none31.24.22.0/24No ROA covers it. Add a ROA for AS42232, maxLength 24.672 of 673
ROA: none31.24.23.0/24No ROA covers it. Add a ROA for AS42232, maxLength 24.672 of 673
ROA: none93.190.2.0/24No ROA covers it. Add a ROA for AS42232, maxLength 24.672 of 673
ROA: none139.28.196.0/22No ROA covers it. Add a ROA for AS42232, maxLength 22.672 of 673

Route objects not announced

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

31.24.16.0/21RIPENo ROA
91.147.224.0/22RIPEInvalid: maxLength
2a03:bf00:100::/40RIPENo 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.