bgpreport

Network · data from 2026-11-12

AS200554 KimiaCloud-AS Dade Pardaz Kimia Pouyesh PJS.

Registry name: KimiaCloud-AS Dade Pardaz Kimia Pouyesh PJS., IR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200554, 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.
85.133.169.0/24 Valid RIR databaseRIPE 670 100% 66
85.133.170.0/24 Valid RIR databaseRIPE 670 100% 66
185.41.0.0/24 Valid RIR databaseRIPE 670 100% 66
185.41.1.0/24 Valid RIR databaseRIPE 670 100% 66
185.41.2.0/24 Valid RIR databaseRIPE 670 100% 66
185.41.3.0/24 Valid RIR databaseRIPE 670 100% 66
5.160.10.0/24 Valid RIR databaseRADB, RIPE 669 99% 66
5.160.196.0/24 Valid RIR databaseRIPE 669 99% 66
81.12.39.0/24 Valid RIR databaseRIPE 669 99% 66

AS-SET

AS200554 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.

  • Route object: not announced2

Route objects not announced

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

81.12.81.0/24RIPEValid
185.41.0.0/22RIPEValid

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.