Your site lives on one server, and your visitors are spread across the planet. Every image, every CSS file and every script has to make that whole trip, and along the way your server’s IP address is introduced to everyone. Our Iran CDN fixes both: content is served from the nearest edge node, inside Iran or abroad, and your origin stays hidden behind it.
Everything on this list is running on our nodes today. None of it is a roadmap item.
Static content is stored on the edge node, so the next request is answered without ever reaching your server. You get three cache modes (standard, aggressive and no cache), and large files and video are cached in 1 MB slices, so seeking through a video doesn’t pull the whole file again. Purging the cache takes one click, for a single URL or the whole domain.
A network of nodes in Europe and Iran. Each visitor is routed to the best node for them, and the European nodes read from each other’s caches: a file that is already warm in Helsinki isn’t fetched from your origin again in Falkenstein.
Enabled on every service port: many requests in parallel over one connection, header compression, and no queuing behind earlier files. For a page made of dozens of small files, this alone makes a noticeable difference.
The newest version of HTTP, running over UDP, live on port 443 and advertised to browsers with the Alt-Svc header. Its real advantage shows on poor networks and on mobile: one lost packet no longer stalls every other request, and switching between Wi-Fi and mobile data doesn’t drop the connection.
A Let’s Encrypt certificate is issued automatically, installed on every node and renewed before it expires, with nothing for you to do. TLS 1.3 with cluster-wide session resumption (a node you have already talked to doesn’t need a full handshake), plus 0-RTT and OCSP stapling.
Brotli for text, CSS, JavaScript, JSON, SVG and fonts, typically 15 to 25 percent smaller than gzip, with gzip as the fallback for clients that don’t support Brotli. Nothing to configure on your server.
JPEG and PNG images are converted to AVIF or WebP on the node itself and cached, depending on which format the visitor’s browser supports. Measured on a real image from this site: a 158 KB PNG became a 31 KB WebP and a 16 KB AVIF. Older browsers get the original file, untouched.
Per-IP caps on request rate and concurrent connections, at one of three levels you choose, plus protection against slow and half-open connections. Because this traffic never reaches your server, the load of an attack stays on the edge nodes and your origin stays out of reach.
For every hostname on the CDN: requests, traffic volume, cache hit ratio, traffic saved at the origin, the HTTP/2 and HTTP/3 share, and average response time, broken down by node. No visitor IPs, page URLs or browser details are stored.
These aren’t marketing numbers. They are the same matrix the CDN router uses to decide which node each visitor goes to. If the measurements go stale, the router stops trusting them, and this table disappears from the page.
3 nodes in this city. Load is spread across them, and if one fails, the others take over. This European node serves visitors outside Iran and reads from its peers’ caches, so your origin is hit less often.
This European node serves visitors outside Iran and reads from its peers’ caches, so your origin is hit less often.
A node inside Iran: the shortest possible path to visitors in Iran. If your origin is in Iran as well, the traffic never leaves the country at all.
This US node serves visitors outside Iran and reads from its peers’ caches, so your origin is hit less often.
2 nodes in this city. Load is spread across them, and if one fails, the others take over. This European node serves visitors outside Iran and reads from its peers’ caches, so your origin is hit less often.
| Visitors in… | Our closest node | Measured latency |
|---|---|---|
| Iran | Tehran | 10 ms |
| Europe | Falkenstein | 19 ms |
| North America | Hillsboro | 38 ms |
| Asia | Nuremberg | 155 ms |
| Africa | Nuremberg | 170 ms |
| Oceania | Hillsboro | 180 ms |
| South America | Hillsboro | 181 ms |
Each figure is the average round trip from that node to several reference servers on the same continent, re-measured several times a day (last measured 2026-10-16 21:47). This is network latency, not your page load time; that also depends on your own site.
No plugin to install, nothing to change on your server, and none of your file URLs change.
Set Mehran Host’s nameservers at your domain registrar. DNS management on PowerDNS is free, and records are published instantly.
Every A record has a CDN switch next to it. Turn it on: the origin IP is saved right there, and the public record now points to the edge nodes.
An SSL certificate is issued for that hostname and installed on every node. It takes about one to two minutes, and you can follow its status on the same page.
Set cache intensity, image optimization, the traffic shield and the other options for that hostname, and see its traffic stats in the same place.
Turning it off is just as easy: the record is published with a short TTL, so switching back to your origin takes effect in under a minute.
These are exactly the options you see in the customer panel, not a separate list that could drift from reality.
| Option | Modes |
|---|---|
| Cache level | Standard — the query string is part of the cache key Aggressive — query string ignored, HTML cached for six hours (for static sites) No cache — proxy only (useful while migrating) |
| Hotlink protection | Off On — images and media load only from your own domain |
| HSTS | Off On — browsers use HTTPS only, for one year |
| Image optimization | Off — images are served unchanged On — automatic JPEG/PNG to AVIF or WebP conversion at the edge |
| Abusive-traffic shield | Standard — 40 requests per second, 100 concurrent connections Strict — 8 requests per second, 20 connections (site under attack) Unlimited — for APIs and file hosting |
| Node selection | Best node for each visitor (best for websites) All nodes in one answer (more resilient, suited to long-lived connections) |
If your problem is on this list, turning the CDN on or off makes no difference, and it is better to know that before you buy. A big one for Iranian sites: files the browser fetches directly from domains outside Iran never pass through our nodes. We explain how to find them and host them locally in our guide to site speed on the National Information Network.
| If… | What actually happens |
|---|---|
| Your pages differ for each user (cart, dashboard, my account) | They aren’t cached, and they shouldn’t be. They are built by your server every time, so their speed depends on your server’s own resources. |
| Time to first byte (TTFB) is high because the site itself is slow | A CDN won’t fix that. Start with page caching and fewer plugins, then add resources; we explain how on our WordPress hosting page. |
| Your origin server is down | Cached content keeps being served for a while, but a CDN is not a replacement for your server. Fresh pages need the origin to be up. |
| You expect a large, targeted volumetric attack | Rate limiting and a hidden origin help a lot, but if your service is a serious target, talk to us first so we can review capacity for you. |
Every account gets 1 TB of CDN traffic free, and it never expires. After that, each GB costs 1,000 Toman (1,000,000 Toman per TB; 1 Toman = 10 Iranian rials), deducted from your wallet based on actual usage, with no monthly fee and no limit on the number of domains. If your balance runs out, the CDN pauses and traffic goes straight to your origin IP. One honest note: if your traffic runs to several terabytes a month, let us know before you launch so we can set capacity aside for you. Not to sell you anything, just so the network is ready in advance.
