Offer Free .in, .co.in or .com domain for year one with web or WordPress hosting on a 12-month+ term, plus free migration. See the offer
Status · 6 regions · 23 components

System status

The state of our website, client area, hosting, VPS, dedicated servers and business email in every region, with active incidents, planned maintenance and the last 14 days. Our operations team updates this page by hand.

Checking status…

Loading the latest state of every component.

Updated by our team:

Active incidents
—
Maintenance
—
Components
—
History starts
—

Every service, by region

Each component's state as of the last update, grouped by product. History starts 20 Oct 2026, when this page went live; a bar for each day appears here once 7 days are recorded.

  • Operational
  • Degraded performance
  • Partial outage
  • Major outage
  • Maintenance
  • Not tracked yet

Loading components…

Active incidents

Times are India Standard Time (UTC+05:30). Updates are newest first.

Loading incidents…

Scheduled maintenance

Windows in IST and UTC

Loading maintenance…

Planned work that could interrupt a service is posted here at least 48 hours before it starts, and emailed to subscribers. Scheduled maintenance with that notice is excluded from the uptime SLA.

Past 14 days

Incidents and maintenance, day by day

  1. Loading history…

Resolved incidents stay listed here for 14 days with their full update timeline.

How we report

Four rules for posting incidents

This page is updated by hand, so the timestamp at the top tells you exactly when someone on our team last changed it. When something breaks, these are the rules we hold ourselves to, alongside how we handle security incidents.

Read the uptime SLA

  1. 01

    Posted within 15 minutes

    Once we confirm customers are affected, an incident goes up here with the services and regions involved — before we know the cause.

  2. 02

    Updated every 30 minutes

    Every open incident gets a timestamped update at least every 30 minutes until it is resolved, even when the update is that we are still working on it.

  3. 03

    A post-mortem for major incidents

    What happened, why, how long it lasted, who was affected and what we are changing so it does not happen again, linked from the incident.

  4. 04

    Maintenance 48 hours ahead

    Planned work is announced at least 48 hours before it starts, with the window in IST and UTC and the services it touches.

Uptime SLA 99.99%

network and infrastructure uptime on every product, measured monthly.

Below 99.99%
10%service credit
Below 99.0%
25%service credit
Below 95.0%
50%service credit
Dedicated hardware
4 hreplacement after diagnosis

Credits are a share of the affected service's monthly fee, capped at 50% a month and paid as account credit. Full terms, exclusions and how to claim are in the SLA.

Get status emails

Status notices only — never marketing. Each email names the services and regions involved, with times in IST.

  • Incident postedWhat is affected and what we know so far
  • Incident resolvedHow long it lasted and what caused it
  • Maintenance bookedThe window in IST and UTC, at least 48 hours ahead

status.json Public · no key · JSON

Prefer to poll?

This page reads one public file, which changes only when our team posts an update. Point your own monitoring, Slack bot or dashboard at it, and please poll no more than every five minutes.

curl -s https://virtualcloud.in/assets/data/status.json \
  | jq '{overall, updated, incidents: (.incidents | length)}'
Response
{
  "overall": "operational",
  "updated": "2026-10-20T10:00:00+05:30",
  "incidents": 0
}
  • overalloperational · degraded · partial · major · maintenance
  • components[]id, group, name, status, history by day
  • incidents[]impact, status, components and timestamped updates
  • maintenance[]start, end, components and description
Open status.json