Serve your status page, your service names, and every incident update in more than one language.
A status page has one default language, and can carry any number of additional ones. Once a second language is on, everything a visitor reads becomes translatable: the page description, your service names, and the text of each incident and maintenance update. Visitors pick their language from the page itself.
This matters when:
English, French, German, Dutch, Polish, Russian, and Swedish. Any of them can be the default, and any of them can be added alongside it.
Go to Status Pages, pick your page, then open the Languages category.
The Default language is what every visitor sees first, and the language your service names and updates fall back to.
Add each language you want under Additional languages. They appear as tags you can remove later.
Your service names and page description now show one input per language. Fill them in, then hit Publish.
With more than one language enabled, the incident and maintenance editors show a language tab above each text field. Write the title and each update once per language, and the visitor sees the version matching their choice.
A language tab you leave blank publishes blank, so during a fast-moving incident the pragmatic move is to write the same text in every tab first and refine the translations afterwards. Editing an update later works exactly like editing any other incident update.
A language picker appears on the status page once a second language is enabled. The page opens in your default language, not in the visitor's browser language, and their choice is remembered in their browser for the next visit.
| Output | Behavior |
|---|---|
| RSS and Atom feeds | Served in the default language, or another one with ?lang=fr |
| Public API | Returns a title object keyed by language code |
| status.json | Language independent, it carries no text |
Additional languages require the Business plan. The default language selector stays available on every plan.
That language tab was left blank when the update was published. Open the incident, fill the tab in, and save. An update written before you added a second language is not affected: text typed while the page had a single language is reused for every language you add later.
Removing a language drops the text written for it. Re-adding the language gives you empty fields again, so export or copy anything you want to keep before removing one.
Tell us which one through the chat or by email. Adding a language means translating the interface strings on our side, so it is a request we act on rather than a setting you can flip.