Service status: 99.9% uptime, monitored 24/7

Every maintenance window is announced on this status page in advance, so a quick look here tells you what work is coming and which components it touches. If the work can affect your service, you also receive an email with the exact date, the time window and the expected impact, so you can judge whether anything on your side needs preparation. The announced window is the maximum reserved time, and the real interruption is often shorter. If planned work clashes with something important on your side, for example a release or a campaign, write to support@cloudhosting.lv before the window starts and we will see what can be adjusted.

Our stated availability target is 99.9% across the infrastructure. We measure availability per service and count announced maintenance windows separately from unplanned downtime. If you need the level of your specific plan confirmed in writing before you order, or a stricter commitment for a project where downtime is expensive, write to us and we will put it in the offer. If you are not sure how the target applies to your service carries, or you want to move to the stricter option, write to support@cloudhosting.lv and we will confirm the details before you change anything.

This page tracks the shared platform: the VPS layer, the network, DNS and the other components. A problem limited to one server or one website will not change these indicators, so an Operational status does not rule out an issue on your side. Typical causes include a crashed process on the server, a full disk, an expired domain or a local network problem between you and us. Before writing in, note what exactly fails: the website, SSH access, email or everything at once, and whether it fails from other networks too. Then contact support with your service name and those details; the NOC responds around the clock and can check your specific server immediately.

This page is the fastest way to check. It shows the live status of the VPS platform, dedicated servers, web and application hosting, the network and uplinks, Anycast DNS and the client area, broken down by region: Riga and Amsterdam. During an incident the affected component changes state and updates are posted here while the work progresses, so refreshing this page keeps you informed without waiting for a ticket reply. If every component reads Operational but your own service still misbehaves, the fault is probably local to your server or connection, so write to support@cloudhosting.lv or call +371 66 66 29 69 and the NOC will investigate.

All services run in two regions today. The primary site is our own Tier 3+ data center in Riga, Latvia, labeled RIX1 on this page, which we operate ourselves rather than renting space from a third party, so we control both the facility and the infrastructure. The second region is Amsterdam in the Netherlands, NL1, useful when you want capacity closer to Western European users. Traffic in both regions rides our own network, AS58269. A third region in Dubai, DXB1, is planned for 2026 and already appears on this page so you can follow its status. If you are unsure which region fits your workload, or you need Dubai earlier, ask support before ordering.

A percentage becomes meaningful when you translate it into time: 99.9% availability allows no more than about 43 minutes of downtime per month. That budget is meant for unplanned incidents, which is why every component on this page is watched by the NOC 24/7: the earlier a fault is caught, the less of that budget it consumes. That budget matters most for online shops, payment flows and APIs, where every minute of silence has a price. When you compare hosting offers, translate each promised percentage into minutes per month the same way; it quickly shows which numbers are commitments and which are decoration.

Two channels work at any hour: email support@cloudhosting.lv or call +371 66 66 29 69. Email suits anything that needs detail or attachments, while the phone is quicker when your service is completely unreachable and every minute counts. Whichever you choose, name the exact service, say when the problem started and attach error messages or screenshots if you have them; concrete details shorten the diagnosis noticeably. Reports go straight to the NOC, which is staffed around the clock, so an incident raised in the middle of the night is handled immediately, not queued until office hours. If the fault turns out to be platform-wide, you will also see its progress reflected on this page.