Help › If our servers are down
What happens if our servers are down
On this page
ResilientLang has two parts that share only static files.
- The control plane is our dashboard, API, translation engines and publisher. It can go down.
- The delivery plane is the set of translation files on your own site and on two content delivery networks. It is built to stay up.
Nothing a visitor's browser does to show a translated page calls the control plane.
What happens during an outage#
| What fails | What your visitor sees | What you cannot do meanwhile |
|---|---|---|
| Our dashboard and API | Translated pages, as normal | Edit, translate or publish |
| Your own site's copy of the files | The loader tries the next place: first one CDN, then the other | Nothing |
| All places that hold the files | The copy saved in the visitor's browser from an earlier visit | Nothing for returning visitors |
| Nothing can be loaded at all | Your page in the original language, never a broken page | Translations for first-time visitors |
| A file has been tampered with | The loader refuses it and keeps what it had | Nothing |
Every request by the loader has a time limit, 2.5 seconds per place by default. A failure at any step leaves the page in the original language.
What this does not cover#
Read The honest limits. In short, new translations need our servers, and a first-time visitor needs at least one place that holds the files.
Check it yourself#
Open your site in a private window. Block the host that serves the translation files in your browser tools. Reload. You should see the original language, not an error. See Install with the script tag.
Status#
We plan a status page hosted separately from the platform, so it stays up when the platform is down. Its address is OPEN.
Keep your own copy#
See Keep your own copy.
Nothing is deployed yet. This is how the product is designed and tested in the repository, including a test in a real browser with the origin taken down.