bgpreport

Network · data from 2026-11-12

AS210392 AriaOxin-AS Azarakhsh Ava-e Ahvaz Co

Registry name: AriaOxin-AS Azarakhsh Ava-e Ahvaz Co, IR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS210392, 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.
88.135.33.0/24 No ROA None 668 99% 67
93.126.14.0/24 Valid RIR databaseRIPE 671 100% 66
93.126.23.0/24 Valid RIR databaseRIPE 671 100% 66
93.126.30.0/24 Valid RIR databaseRIPE 671 100% 66
93.126.31.0/24 Valid RIR databaseRIPE 671 100% 66
95.38.72.0/24 Valid RIR databaseRIPE 671 100% 66
178.239.152.0/24 Valid RIR databaseRIPE 671 100% 66
185.112.148.0/24 Valid RIR databaseRIPE 671 100% 66
185.180.128.0/24 Valid RIR databaseRIPE 671 100% 66
185.180.129.0/24 Valid RIR databaseRIPE 671 100% 66
185.180.130.0/24 Valid RIR databaseRIPE 671 100% 66
185.180.131.0/24 Valid RIR databaseRIPE 671 100% 66
93.126.45.0/24 Valid RIR databaseRIPE 669 99% 66
185.33.25.0/24 Valid RIR databaseRIPE 669 99% 66
185.212.48.0/24 Valid RIR databaseRIPE 669 99% 66

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none88.135.33.0/24No ROA covers it. Add a ROA for AS210392, maxLength 24.668 of 673
Route object: none88.135.33.0/24No route object for it. Add a route object with origin AS210392 in the RIR database for the space.668 of 673

Route objects not announced

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

87.248.140.0/24RIPEValid
93.126.48.0/24RIPEValid
93.126.50.0/24RIPEValid
2a0a:a480::/29RIPENo 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.