bgpreport

Network · data from 2026-11-12

AS64434 Mizban Amvaj Sahel Sepehr Bushehr

Registry name: Iranicaserver Mizban Amvaj Sahel Sepehr Bushehr PJSC, IR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS64434, 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.
185.165.28.0/24 Valid Other origin only 672 100% 66
185.165.30.0/24 Valid Other origin only 672 100% 66

AS-SET

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

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none185.165.28.0/24Route objects for it name AS48147. Add a route object with origin AS64434 in the RIR database for the space.672 of 673
Route object: none185.165.30.0/24Route objects for it name AS48147. Add a route object with origin AS64434 in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS64434 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.