bgpreport

Network · data from 2026-11-12

AS213953 MizbanDadehPardis

Registry name: MizbanDadehPardis Mizban Dadeh Pardis .Ltd, IR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS213953, 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.42.214.0/24 Valid Other origin only 670 100% 66
88.218.19.0/24 Valid RIR databaseRIPE 672 100% 66
193.228.168.0/24 Valid RIR databaseRIPE 672 100% 66
193.228.169.0/24 Valid RIR databaseRIPE 672 100% 66
87.107.86.0/24 Valid RIR databaseRIPE 671 100% 67
88.218.16.0/24 Valid RIR databaseRIPE 670 100% 66
88.218.18.0/24 Valid RIR databaseRIPE 670 100% 66
185.42.213.0/24 Valid RIR databaseRIPE 670 100% 66
77.104.108.0/24 Valid RIR databaseRIPE 669 99% 66
217.114.46.0/24 Valid RIR databaseRIPE 641 95% 66
193.228.91.0/24 Valid RIR databaseRIPE 639 95% 66
2a14:ec00:3::/48 Valid RIR databaseRIPE 630 99% 67
2a14:ec00:4::/48 Valid RIR databaseRIPE 629 99% 67
2a14:ec00:5::/48 Valid RIR databaseRIPE 629 99% 67

AS-SET

AS213953'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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none185.42.214.0/24Route objects for it name AS198154. Add a route object with origin AS213953 in the RIR database for the space.670 of 673

Route objects not announced

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