bgpreport

Network · data from 2026-11-12

AS49801 Sotoon-Cloud-Infrastructure Hezardastan Unit Cloud Computing PJSC

Registry name: Sotoon-Cloud-Infrastructure Hezardastan Unit Cloud Computing PJSC, IR · not in PeeringDB

4IPv4 routes 100.0% RPKI valid · 50.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
7Route objects not announced registered with origin AS49801, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS49801, 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.

46.245.48.0/21 Valid Nonecovered by 46.245.48.0/20 670 100% 66
46.245.56.0/21 Valid Nonecovered by 46.245.48.0/20 670 100% 66
185.166.107.0/24 Valid RIR databaseRIPE 671 100% 67
46.245.48.0/20 Valid RIR databaseRIPE 670 100% 66
2a10:a440::/29 Valid RIR databaseRIPE 632 99% 68
2a10:f980::/29 Valid RIR databaseRIPE 632 99% 68

AS-SET

AS49801 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 9 are in fix.csv.

  • Route object: none2
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: none46.245.48.0/21No route object for it. A route object for 46.245.48.0/20 with origin AS49801 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49801 in the RIR database for the space.670 of 673
Route object: none46.245.56.0/21No route object for it. A route object for 46.245.48.0/20 with origin AS49801 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49801 in the RIR database for the space.670 of 673

Route objects not announced

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

78.111.5.0/24RIPEValid
78.111.6.0/24RIPEValid
87.247.168.0/21RIPEValid
87.247.173.0/24RIPEValid
185.166.105.0/24RIPEValid
193.29.26.0/24RIPEValid
194.34.161.0/24RIPEValid

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.