Iran Cloud Status

Price one server size (vCPU, RAM, disk) per month at Hamravesh and Liara, cheapest first. Hamravesh charges per unit (exact size, Iran or Germany datacenter). Liara sells fixed plans, so the answer is the cheapest PaaS and IaaS plan that is at least as big (IaaS also pays a monthly IPv4 fee). Traffic is not included. ArvanCloud and Chabokan are not compared: no readable plan table.

List one provider's status components (services, regions, clusters, servers) with their current status. Use it for "is ArvanCloud object storage in Simin OK?" or to see what a provider monitors. Status is one of operational, degraded, partial_outage, major_outage, maintenance. Names are as published: ArvanCloud English, Hamravesh and Chabokan Persian, Mihan WebHost server names. Use cs_regions for one line per region.

Show one incident with its full update timeline, affected components and the status each was set to. Use it after cs_incidents or cs_status when you need the whole story of a specific outage ("what did ArvanCloud say about incident 88?"). ArvanCloud and Chabokan have a detail endpoint; Hamravesh and ParsPack incidents are looked up in their published history (Hamravesh: the latest ~800 entries).

List recent incidents (outages, degradations, announcements) of the Iranian cloud providers, newest first, with their latest update. Use it for "what happened to ArvanCloud this week?" or "is the Hamravesh problem fixed?". Set updates=True for the full investigating -> resolved timeline, or call cs_incident with an id from here. ParsPack entries are announcements: status 'notice' while open, 'resolved' after, `components` are the affected product types. Hamravesh history reaches back years but is paged, so large `days` values cost extra requests. For counts and downtime see cs_reliability.

List announced maintenance windows that are upcoming or running, per provider, optionally with recent finished ones. Use it to check whether a planned change explains a disruption (include_past=True) or to warn about an upcoming window. Empty means nothing is announced. Times are ISO with the zone (Iran time, +03:30).

Show a provider's public price list in Toman, read from its own pricing page. Liara: fixed plans per product (PaaS, DBaaS, IaaS and WordPress with RAM, vCPU, disk; Email, AI, ObjectStorage with their own columns), monthly and hourly. Hamravesh: per-unit prices (vCore, GB RAM, GB SSD) in its Iran and Germany datacenters plus traffic, IP and monitoring fees. Chabokan: the starting price of each product. Use cs_compare_prices to price one specific server size across providers.

List the providers this server covers, what each one publishes, and which are not covered. Use it to answer "which Iranian clouds can you check?" or to pick the right provider id for the other tools. Makes no network calls.

Summarise status per region or group: component count, worst status and what is not operational. Use it for "is anything wrong in the Simin region?" or "which ArvanCloud region has problems?". Groups are the provider's own: ArvanCloud regions (Bamdad, Simin, Forough, Shahriar, Goethe, Qeysar, Global), Hamravesh Kubernetes cluster vs ungrouped, Chabokan service categories, Mihan WebHost server types. Next: cs_components for the members, cs_incidents for what happened.

Count incidents and add up incident time per provider over the last days, with the most affected components. Use it to compare how reliable the providers have been ("which Iranian cloud had the fewest incidents this month?", or with query='object storage' for one service). Counts incidents that overlap the window. Minutes run from an incident's start (or the window start) to its resolution (to now if still open) with overlapping incidents counted once; incident_time_percent is the share of the window with at least one incident open. That is not an uptime percentage: none of these providers publishes uptime, and a partial incident counts fully.

Show the live status of every Iranian cloud provider this server reads (ArvanCloud, Hamravesh, Chabokan, ParsPack, Mihan WebHost) in one call. Use it first for "is X down?" or "what is broken right now?". Each provider gives its overall status, which components are not operational, open incidents and upcoming maintenance counts. ParsPack has no component status (only announcements; status 'notice' is an announcement, not an outage). Next: cs_regions for a per-region view, cs_components for the full component list, cs_incident or cs_incidents for the timeline, cs_maintenance for maintenance windows.