€100 welcome bonus a code for your next order, after your first renewal How the bonus works

Why choose us

One data center, connected to all of Europe.

Every server you rent from us is in our own data center in Sofia, and we run it ourselves. Instead of opening more sites, we built the network out of this one: our own wavelengths to nine other points of presence from London to Istanbul, ten transit carriers and more than 25 exchanges.

24/7 on siteour own hardware engineers, in our own data center
25+ exchangesand ten transit carriers
Ten siteson our own wavelengths, from London to Istanbul
31 msto Frankfurt and 42 ms to London, round trip

One well-connected site beats many badly connected ones

Many hosting companies list a long row of cities. We list one, on purpose.

The network behind it

A long list of cities looks good on a hosting site. Before you count them, ask what stands behind each one: whose building it is, who is on the floor at night, how many carriers the site has, and whether the cities are joined by the provider's own backbone or each one buys its transit alone. Some providers have good answers for every city. Many have a few racks and one or two uplinks per site, and that is what we decided not to build.

All our servers are in Sofia, and the money went into the network out of Sofia: Juniper MX304 routers at the border, ten transit carriers, peering at more than 25 European exchanges, more than 100 PNI ports into content, cloud and hosting networks, and our own DWDM wavelengths to the nine other points of presence. Those nine are network sites: routers, exchange ports and, in five of them, a scrubbing cluster. No customer server runs there.

Distance sets a floor. Light in fibre needs about 1 ms of round trip for every 100 km, so Frankfurt can never be closer to Sofia than about 14 ms, or London than about 20. Above that floor the path decides: how far the fibre wanders, how many networks the packet crosses, whether it is handed over at an exchange or carried by a transit carrier, and whether the route is chosen for speed or for the fewest AS hops. A server in a thinly connected site can be closer on the map and still take the long way round. From our network it is about 31 ms to Frankfurt and 42 ms to London, as the table below shows.

With one site, what a server needs can be next to it. The warehouse of parts and whole servers and the engineers on the floor are in the building where your server runs. An attack that enters the backbone in another city is dropped at the cluster there, before it heads for Sofia.

Sometimes one site in Sofia is the wrong answer. If your service has to survive losing a whole city, it needs a copy in another one. If your users are mostly in Western Europe, a server in Frankfurt, Amsterdam or London is 30 to 40 ms closer to them than one in Sofia, and for games, voice or trading that decides it. Sofia makes sense when your users are spread over Central and Eastern Europe, the Balkans and Turkey, with the big Western exchanges still 31 to 42 ms away.

25+
European exchanges we peer at
10
transit carriers
100+
PNI ports into content, cloud and hosting networks
5
direct spans out of Sofia: Frankfurt, Budapest, Bucharest, Thessaloniki, Istanbul
Topic Many locations, rented space One site, our own network
Connectivity Often one or two upstreams per location, whatever the building offers. Ten carriers, 25+ exchanges and 100+ PNI ports, behind every server.
Latency Low to its own city, and whatever the upstream gives everywhere else. Our own wavelengths from Sofia to nine other points of presence. Round trip: about 31 ms to Frankfurt, 42 ms to London, 15 ms to Athens.
DDoS Often a null route, or traffic sent to a scrubbing centre far away. Dropped on our own network at the nearest of six scrubbing clusters, always on, and never a null route as our mitigation.

Round-trip latency from Sofia

Round trip from Sofia
Region City and round trip
Balkans Thessaloniki 6 msZagreb 12 msAthens 15 msBelgrade 27 ms
Central Europe Budapest 13 msPrague 14 msKyiv 24 msWarsaw 29 msVienna 34 msMunich 35 ms
Western Europe Milan 22 msFrankfurt 31 msAmsterdam 32 msZurich 33 msParis 37 msLondon 42 ms
Caucasus & Middle East Yerevan 68 msTbilisi 74 msBaku 85 msTel Aviv 89 msRiyadh 102 ms
Africa Cairo 81 ms

Our own data center, against rented colocation

Most hosting companies with many locations rent colocation: racks, power and cooling in a building another company runs. We run ours.

The data center in detail

Renting colocation works, and plenty of good services run on it. It does put a second company between you and your server, and when something breaks, your ticket waits in that company's queue as well as in your provider's.

In a rented rack a failed drive becomes two tickets: one to the hosting company, then one from the hosting company to the building. The spare is often ordered and shipped, because few providers keep a full shelf in every city they list, and a visit at night or at the weekend is often billed per job.

When a drive fails at 3 a.m. on a Saturday in our data center, the replacement comes off our own shelf and the engineer already in the building fits it. Nothing is ordered and nobody is called in. Every server is a Dell PowerEdge or an HPE ProLiant, so the shelf holds spares for a short list of models, and a custom build is put together from the same stock, in the building where it will run.

It works the same way when the hardware is yours. With colocation here your servers stand in our building, on our network and behind our filtering, and the remote hands are our own engineers.

24/7
our own hardware engineers in the building
0
contractors or data center staff between you and your server
2
server makers only, Dell and HPE, so the spares on the shelf fit
Topic Rented colocation Our own data center
Who is on the floor The landlord's staff or a remote-hands contractor, working one queue for every tenant. Our own hardware engineers, and nobody else's.
A failed part A ticket to the building, a part ordered and shipped, then another ticket to fit it. Taken from our own warehouse on site and fitted by the engineer on shift.
Nights and weekends Remote hands on call, often billed per visit and rarely quick. Engineers in the building 24 hours a day, every day.
Custom builds Parts bought for your order, then shipped to a site the provider rarely sees. Built from our own stock, in the building where the server will run.
Changes Power, cabling and access go through the landlord. Decided by us and done by us.

Who picks up

You will be talking to a person. This is a decision about what the business is, more than a policy we advertise. When a server or a network is down, the cost of being misunderstood is measured in minutes, and every layer between you and somebody who can change a rule is one of those minutes spent.

Contact details

Nothing answers before a human does

No chatbot on the site, no AI agent on the first line, no language model reading your ticket and deciding its priority. The first reply you get is written by an engineer who can already see the traffic you are describing.

One escalation, not four

The people on the support line are the people who run our network and who built the filter. There is no tier one whose job is to ask you to reboot, and no queue between you and somebody who can change a rule or pull a drive.

Reachable the way you actually work

E-mail or a shared channel with your team, 24 hours a day, every day. During an incident we stay with it until the traffic is clean, and you get the packet-level record of what was dropped afterwards. Customers get a named account manager and a network engineer who know the server, the routing and its history.

And why Sofia

Sofia was a choice as well: five reasons, each with its number and its source.

01 Geography

Between Western Europe and the Middle East

From Sofia the round trip is about 31 ms to Frankfurt, 32 ms to Amsterdam and 42 ms to London, and 15 ms to Athens, 74 ms to Tbilisi, 81 ms to Cairo and 89 ms to Tel Aviv. Bulgaria is a fibre corridor in its own right: the 1,182 km Caucasus Cable System lands at Balchik on the Black Sea and runs overland to Frankfurt, and our own backbone has direct spans from Sofia to Frankfurt, Budapest, Bucharest, Thessaloniki and Istanbul.

WonderNetwork RTTs, Sept 2026, the same from our network; DE-CIX Sofia; Caucasus Cable System

02 Power

Nuclear and solar: low-carbon electricity at a low price

In 2025 the two VVER-1000 reactors at Kozloduy supplied 39.6% of Bulgaria's electricity and renewables 32.2%, solar alone 17.4% after installed PV grew from 1.7 GW at the end of 2022 to about 6 GW at the end of 2025. Coal still covers about a fifth, down from 41% in 2022, so we say low-carbon, not green. Industrial electricity cost €0.141 per kWh in the second half of 2025 against an EU average of €0.184 and €0.226 in Germany: 23% below the EU average, ninth-lowest of the 27. Two further AP1000 units are in the engineering phase, targeted for the mid-to-late 2030s.

Eurostat nrg_cb_pem and nrg_pc_205 (2025); ENTSO-E via pv magazine, Feb 2026; World Nuclear Association

03 Jurisdiction

EU, euro area, Schengen, NATO

In the EU since 1 January 2007 and in NATO since 29 March 2004; Schengen at its air and sea borders from 31 March 2024 and at its land borders from 1 January 2025; the 21st member of the euro area on 1 January 2026, the lev replaced at the fixed 1.95583. For your server that means your data sits inside the EU under the same GDPR as everywhere else in the Union, your contract is under EU member-state law and a judgment from any EU court is enforceable here without a separate procedure, your invoices are in euro with no exchange-rate exposure, hardware shipped from anywhere in the EU crosses no customs border, and your engineers reach the rack on a Schengen-internal trip.

EU country profile; nato.int; Council Decision (EU) 2025/1407; ECB, 1 Jan 2026; Regulation (EU) 1215/2012

04 Ground

Less seismic hazard than Istanbul or Bucharest

Sofia is not earthquake-free and we will not tell you it is. The 2020 European Seismic Hazard Model puts the city's 475-year peak ground acceleration at about 0.26 g on rock. That is below Istanbul (0.41 g) and Bucharest (0.30 g), in the same band as Athens and Zagreb, and well above Frankfurt (0.05 g) or Milan (0.08 g). Bulgarian codes design for exactly that: reference acceleration 0.23 g under the Eurocode 8 national annex, seismic coefficient 0.27 on the 1000-year zoning map. The last earthquake to devastate Sofia was in 1858; the strongest since, nearby, were the M5.3 of 1917 and the Mw 5.6 Pernik earthquake of May 2012, 25 km away, which caused superficial damage. Bulgaria has had no magnitude-7 earthquake since 1928. Ask us for the building's own structural documentation: a national hazard map is not a site survey.

ESHM20 via the EFEHR hazard services API; BDS EN 1998-1/NA:2012; Ordinance RD-02-20-2/2012; USGS ComCat

05 People

One of the fastest-growing IT workforces in Europe

Bulgaria employs 141,500 ICT specialists (2025), a headcount up 27% since 2022. That is the fourth-fastest growth in the EU, against an EU average of 11.5%. The ICT sector produces 8.1% of the country's gross value added against an EU average of 5.2%, and Sofia is where it lives: the capital generates 88% of Bulgaria's information-and-communication output and employs 116,000 of the sector's 139,000 people. The software industry sells 87% of what it makes abroad and grew revenue 11.5% in 2024; Bulgaria ranks 18th of 123 in the EF English Proficiency Index. SAP Labs (in Sofia since 2000), Bosch (nearly 700 software engineers) and Uber (since 2014) hire from the same pool our engineers come from.

Eurostat isoc_sks_itspt (2025), nama_10r_3gva (2024); BASSCOM Barometer, Dec 2025; EF EPI 2025

Certified and audited

ISO 9001 and ISO 27001 certified, PCI-DSS compliant, GDPR and NIS2 by design.

Cloud Wall Ltd is certified for quality management and information security, compliant with PCI-DSS for card-handling environments, and operates within the European security and incident-reporting framework that applies to digital infrastructure providers under NIS2. GDPR applies to us both as a controller, for the account and billing records we keep ourselves, and as a processor for whatever runs on your server, and it is designed into what we retain.

  • ISO 9001 Quality management system, certified to the international standard
  • ISO 27001 Information security management system, certified and audited
  • PCI-DSS Compliant infrastructure for the handling of card data
  • GDPR Controller for our own records, processor for your server's data
  • NIS2 The EU security and incident-reporting rules we work by

Questions

One site

Is one site a single point of failure?

For the building, yes: if the site is lost, every server in it is lost with it. Above your server's port the network is doubled: two or more Juniper MX304 at the border, two or more QFX10008 in the fabric, ten transit carriers, and five direct spans out of Sofia, to Frankfurt, Budapest, Bucharest, Thessaloniki and Istanbul. The power is redundant too: two independent substations, A and B feeds on separate panels, a modular redundant UPS and N+1 diesel generators, and the cooling is N+1. If your service has to keep running when a whole site is lost, keep a second copy in another city.

What about a provider with many sites and its own backbone?

Then compare one of their sites with ours. If it is in your users' city it will be closer, and you should weigh that first. What we put against it is the rest of this page: our own engineers in the building around the clock, the parts on our own shelf, filtering on our own network, and the path from our network to your prefixes, measured before you pay.

Sofia

Why not Frankfurt or Amsterdam?

If most of your users are in Western Europe, put the server there. From Sofia, Frankfurt is about 31 ms and London about 42 ms, and no network takes that distance away. Sofia is the closer site for Greece, the Balkans and Central and Eastern Europe: about 6 ms to Thessaloniki, 13 ms to Budapest and 15 ms to Athens. Send us your prefixes and we will measure the path from our network before you buy.

Is the electricity really green?

It is low-carbon: 72% of net generation in 2025 was nuclear or renewable and coal was 22%, down from 41% three years earlier. We use the accurate word. The direction is clear: solar capacity more than tripled between 2022 and 2025, and renewables overtook coal for the first time in 2025. We will update the figures every year from Eurostat.

What about earthquakes?

Sofia is a seismic region and we will not pretend otherwise. It has its own named seismic zone, and Bulgaria produced five magnitude-7 earthquakes between 1901 and 1928, including one of the largest shallow quakes on land in 20th-century Europe.

What the numbers say is comparative. On the 2020 European Seismic Hazard Model Sofia's 475-year peak ground acceleration is about 0.26 g on rock, against 0.41 g for Istanbul and 0.30 g for Bucharest, in the same band as Athens and Zagreb, and well above Frankfurt at 0.05 g. Bulgarian codes design for it, with a 0.23 g reference acceleration under the Eurocode 8 national annex, and there has been no magnitude-7 earthquake in Bulgaria since 1928. The last one to devastate Sofia was in 1858; the Mw 5.6 Pernik earthquake of 2012, 25 km from the city, caused superficial damage.

If seismic design is a procurement requirement, ask us for the facility's structural documentation rather than taking a national hazard map as a site survey.

Is Bulgaria a stable jurisdiction for a long-term contract?

It is an EU member state of nineteen years, in NATO for twenty-two, in Schengen and now in the euro area. Your contract is under EU member-state law and enforceable from any EU court; your data is under GDPR; your invoice is in euro. Those are the same guarantees you get in Frankfurt.

Are there enough engineers to staff a network around the clock?

Bulgaria has 141,500 ICT specialists and Sofia holds nearly nine tenths of the sector; SAP, Bosch and Uber run engineering centres here for the same reason. Our own team is senior system and network engineers who have run this network since 2009. The people who answer your ticket are the people who built the filter.

See the path from Sofia to your users.

Send us the prefixes you deliver to. We send back the measured path and latency from our network, so you can judge it for your own users before you order.