an hour ago
Hello! We're enabling Railway CDN caching on our service web (project girafoufou, region EU West). We're on the Hobby plan. Two questions for our GDPR records:
-
Who operates the CDN edge that stores cached copies — Railway's own Hikari edge, or Fastly/Cloudflare as a sub-processor? In which countries are cached objects stored, and is there any way to keep cached copies within the EU? We only cache public static files (images, audio, video); pages and API responses are
private. -
Your docs mention that network egress "may be limited" above 100 GB/month. Does this apply to our plan, what does "limited" mean in practice, and do CDN cache hits count toward it?
Thanks!
Pinned Solution
39 minutes ago
We don't use Fastly anywhere anymore; we use our own in-house CDN.
5 Replies
an hour ago
We operate our own edge/CDN across a global network of points of presence (POPs) in dozens of cities, and cached copies are stored at whichever POP is nearest each visitor, so they are distributed worldwide with no option to restrict caching to EU-only locations. The published subprocessor list at trust.railway.com is the authoritative reference for your processing records. On egress, there is no hard 100 GB cap: we may throttle outbound bandwidth and reach out if it exceeds 100 GB/month to verify legitimacy, but CDN cache hits do not count toward egress at all since they are served directly from the edge without reaching your service (confirmed by the x-cache: HIT header).
Status changed to Awaiting User Response Railway • about 1 hour ago
Railway
We operate our own edge/CDN across a global network of points of presence (POPs) in dozens of cities, and cached copies are stored at whichever POP is nearest each visitor, so they are distributed worldwide with no option to restrict caching to EU-only locations. The published subprocessor list at [trust.railway.com](https://trust.railway.com) is the authoritative reference for your processing records. On egress, there is no hard 100 GB cap: we may throttle outbound bandwidth and reach out if it exceeds 100 GB/month to verify legitimacy, but CDN cache hits do not count toward egress at all since they are served directly from the edge without reaching your service (confirmed by the `x-cache: HIT` header).
an hour ago
Thanks! One follow-up for a human, for our GDPR records: in March a Railway employee wrote that "Fastly operates the CDN edge layer" (https://station.railway.com/questions/which-header-should-i-rely-on-for-real-c-d78a6f96). Is Fastly — or Cloudflare, listed on trust.railway.com — involved in serving or storing cached objects for Railway CDN today, or is it fully Railway's own Hikari edge? Thanks!
Status changed to Awaiting Railway Response Railway • about 1 hour ago
44 minutes ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 44 minutes ago
kotyv
Thanks! One follow-up for a human, for our GDPR records: in March a Railway employee wrote that "Fastly operates the CDN edge layer" (https://station.railway.com/questions/which-header-should-i-rely-on-for-real-c-d78a6f96). Is Fastly — or Cloudflare, listed on trust.railway.com — involved in serving or storing cached objects for Railway CDN today, or is it fully Railway's own Hikari edge? Thanks!
43 minutes ago
IIRC Railway does not use Fastly anymore.
0x5b62656e5d
IIRC Railway does not use Fastly anymore.
42 minutes ago
Thanks! Could a Railway employee confirm this officially? We need it in writing for our GDPR records: are cached objects for Railway CDN served and stored only on Railway's own infrastructure today (no Fastly or Cloudflare involved)?
39 minutes ago
We don't use Fastly anywhere anymore; we use our own in-house CDN.
Status changed to Awaiting User Response Railway • 39 minutes ago
Status changed to Solved 0x5b62656e5d • 36 minutes ago