bgpreport

Network · data from 2026-11-12

AS198926 Fazed Fazel Rezaei Kalantari

Registry name: Fazed Fazel Rezaei Kalantari, IR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198926, 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.
94.184.32.0/24 Invalid: origin Other origin only 1 0%low visibility 1
92.42.202.0/24 Valid RIR databaseRIPE 671 100% 66
94.184.39.0/24 Valid RIR databaseRIPE 671 100% 67
212.108.98.0/24 Valid RIR databaseRIPE 671 100% 67
62.60.138.0/24 Valid RIR databaseRIPE 668 99% 66

AS-SET

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

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin94.184.32.0/24ROAs covering it name AS6736, AS34837, AS60631, not AS198926. If AS198926 should announce it, add a ROA for AS198926.1 of 673
Route object: none94.184.32.0/24Route objects for it name AS6736, AS60631. Add a route object with origin AS198926 in the RIR database for the space.1 of 673

Route objects not announced

Every route object with origin AS198926 is announced.

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.