Vercel, Railway and other PaaS availability from Russia - checked from our own server

Every few minutes we check whether Vercel, Railway, Render, Netlify, Heroku and Fly.io respond from a server located in Russia, and publish the raw results below. This is not the official status of any of these services - only our own measurements from one network vantage point in Russia.

Vantage point: РФ (dada-cloud, beget-prod)
Data is updating...
ServiceAvailabilityHTTP statusLatency, msTLS
VercelNo data---
RailwayNo data---
RenderNo data---
NetlifyNo data---
HerokuNo data---
Fly.ioNo data---

This is not an official status page

Every number on this page is captured by our own monitor running on a server in Russia (dada-cloud, beget-prod), and reflects reachability only from that specific network vantage point. We are not claiming that the listed services are down - a temporary block at the provider, DNS, or routing level specifically for Russian IP ranges is a common cause, not a failure on the service's side. For the official status, check the provider's own status page.

A Russian card and billing is a separate story

Even when a service is technically reachable, RU developers commonly report that paying for Vercel, Railway and similar PaaS with a Russian card gets declined by the acquiring bank or the provider itself - independent of whether the site is up at that moment. If the card doesn't go through, moving the project to a platform billed in rubles removes the question entirely.

Questions about foreign PaaS availability from Russia

There is no single cause: it can be a temporary network block for RU ranges, a DNS issue, or provider-side routing rather than an outage of the service itself. Our monitor records reachability from one point in Russia, not Vercel's official status.

Don't wait for it to get fixed - deploy where availability from Russia isn't a question

Dada Cloud runs on servers in Russia: ruble payments, the same GitHub-to-production flow, no "will it load today" guessing.