Live Status
The Live Status page shows whether Playground is working right now, what happened recently, and what we are working on. Open it from Live Status in the website footer, or go to playg.app/status. You do not need to sign in.
It updates by itself every minute. If it ever says its data may be delayed, the pings behind it have paused and the last known state is shown; check again in a few minutes.
What it does for you
- Tells you what is wrong, before you have to ask. If plays will not sync or a page is slow, look here first: you can see whether it is a known problem and whether we are already on it.
- Shows what is planned. Maintenance is announced ahead of time, with the time window and the parts affected, so you can plan around it.
- Keeps the history. The last 90 days of every component and a calendar of the last two months show how reliable each part has been.
- Sends you updates. Subscribe once and we email you when we post an incident or announce maintenance (see Get updates).
What to keep an eye on
The page lists the parts of Playground that matter to you. These are the ones to follow:
| Component | What it is | Follow it if… |
|---|---|---|
| Playground instance (for example Europe 0 or Europe 1) | The platform your organisation uses: plays, activity, approvals, your Control Panel | Always. Your organisation runs on one instance (see the note below) |
| Source Control (Bitbucket) | Where your plays are stored. Shows Bitbucket's own status and whether Playground can reach it | You push, sync or create plays: a Bitbucket problem can affect you even when Playground is healthy |
| MCP | Lets AI assistants connect with Playground | You use Playground from an AI assistant |
| Website | playg.app and its documentation | You rely on the docs or sign-up pages |
| Community | The community forum | You use the forum |
Check your own instance
Playground runs on more than one instance, and an incident or maintenance can affect one instance only while the others are fine. Open your main Playground app and note the instance your organisation runs on (if you are not sure, ask your administrator or contact us). Then follow the card with the same name on this page, and choose that component when you subscribe, so you hear about the issues that affect you.
What you see on the page
Headline: one line for the whole platform: all systems operational, slower than usual, a problem, or maintenance in progress.
Components: each part with its current state, its bars and its uptime over the last 24 hours, 7, 30 and 90 days. While a part is fine nothing else is said; when it is not, the card says since when.
State Meaning Operational Working normally Degraded Working, but slower than usual or with some failures Outage Not working Maintenance Planned work in progress Bars: each component has a row of bars. Use the switch above them to look at the last 24 hours (one bar every 30 minutes, times in your own timezone) or the last 90 days (one bar a day). We remember your choice on this device. Hover a bar to see what happened in that period and when, for example "service down 12:30 for 20 min", and how many pings were missed or slow, even on a green bar.
Color Meaning Green Up: everything is running Amber Some slowness detected (nothing alarming). Hover to see when and for how long Red Service down. Hover to see when and for how long Grey No data In the 24-hour view, one missed ping makes its half hour amber. A day in the 90-day view is coloured amber only from a few minutes of slow or missed pings, so one or two isolated slow pings do not colour a whole day. A real outage is always red: if a part was actually down (several pings in a row went unanswered), that half hour and that day are red, however short. Parts that we ping less often (for example once an hour) keep the colour of their last ping until the next one, so their bars have no gaps. If the 90-day view starts with grey days, we simply were not monitoring yet; the card says "Monitoring since" the first day with data.
Pings and uptime: we ping every part automatically. Uptime is the share of pings that got an answer (a slow answer still counts as up). The line above the figures says how many pings that was in the last 24 hours and how many were missed or slow, so a figure below 100% can always be explained.
Calendar: the last two months at a glance, in your own timezone. A day is red for an outage, yellow for a degradation, blue for maintenance and purple for a release. Hover or click a day to see what happened and when. Use the ← and → keys (or the arrows) to look at earlier months.
Incidents: problems we are working on, with updates from the team as they come in.
Update Meaning Investigating We know something is wrong and are looking into it Identified We found the cause and are working on a fix Monitoring A fix is in place and we are watching to be sure Resolved It is over Scheduled maintenance: planned work, announced ahead of time, with the window and the parts affected.
Past 30 days: resolved incidents and recent outages, degradations and maintenance.
What we leave out
Short moves or restarts that our hosting platform does on its own (a few seconds, and nothing else wrong) and planned maintenance are not counted as problems: they do not colour the bars, appear in the list or calendar, or lower the uptime. Anything longer, or with an app error behind it, is always shown.
Get updates
At the bottom of the page you can follow the status in two ways.
Enter your address and choose to follow everything or only the components you pick (we suggest your own instance and Source control). We send one mail with a confirmation link that works for 48 hours. Nothing is saved until you open that link, so only confirmed addresses receive updates. To change what you follow, subscribe again with a different choice.
After subscribing you receive:
| You get an email when… | What it tells you |
|---|---|
| An incident is opened | What is affected, the impact (degradation or outage) and what we know |
| An incident is updated | Progress: Investigating, Identified or Monitoring, with the latest message |
| An incident is resolved | That it is over, and what was done |
| Maintenance is announced | The time window and the parts affected, ahead of time |
| Maintenance is completed | That the work is finished |
Every mail starts with [Playg Status] and has an unsubscribe link. If you follow chosen components, you only get updates that affect them (plus updates about the platform in general).
You will not get an email for every short blip. We ping every minute and can show a component as degraded or down on this page before we have written an incident about it. Emails are sent when we post an incident or announce maintenance, so when something feels wrong, check the page rather than waiting for a mail.
Atom feed
Add https://www.playg.app/status/feed.atom to your feed reader to see the same incidents, maintenance and releases there.
If the page shows everything operational but something is wrong
The page is read-only and a few minutes behind real life at most. If something is not working for you and the page shows everything operational, please tell us from the Help page. Say which instance you use, what you were doing and the time (with your timezone), so we can find it.
note
If the Live Status page itself cannot be reached or says its data may be delayed, we may be having a problem of our own. The page then shows the last known state, so please check again shortly.