Status Page Writing — Incident Update Vocabulary
Learn to write clear, professional status page updates during incidents.
0 / 31 completed
1 / 31
Which status page status correctly describes a partial service degradation where some features are affected?
'Degraded performance' or 'Partial outage' is the correct status for when some features are affected but the service is not completely down.
2 / 31
What is the most important information to include in the FIRST status page update during an incident?
The first update should acknowledge the incident immediately, even before the cause is known. Users need to know the team is aware and investigating.
3 / 31
Which phrase is most appropriate for a status page 'All Clear' update?
An 'All Clear' update should confirm full resolution, state all systems are operational, and optionally commit to a post-incident report — using professional, reassuring language.
4 / 31
What does 'impact' mean in status page terminology?
Impact in status page context refers to how the incident affects users — which features are unavailable, how many users are affected, and what they cannot do.
5 / 31
Which writing style is correct for a status page update?
Status pages should use active voice, plain English, timestamps, and clear next steps. Users need clarity, not technical jargon or legal language.
6 / 31
Sarah posted this comment on a PR describing a recent outage:
"The API is intermittently returning 502 errors. We've rolled back the deployment, but it's still happening. Users are reporting timeouts."This scenario demonstrates a common situation where developers need to communicate the severity of an incident clearly. Option A is too strong - 'completely unavailable' isn't necessarily accurate if some users *can* still access parts of the system. Option B describes poor performance, not an outage. Option C suggests a critical bug requiring immediate escalation – while potentially true, the description doesn't fully convey the intermittent nature of the problem. The correct answer accurately reflects the situation: 'intermittent instability' aligns with the reported 502 errors and timeouts, acknowledging ongoing investigation.
7 / 31
John posted this update to the team Slack channel during a status page incident:
"We're seeing high latency on the payment gateway. Users are reporting failed transactions. The monitoring system is showing increased CPU utilization on the database servers. We've initiated scaling of the gateway, but it's not yet resolved."This update accurately describes a partial service degradation. Using phrases like 'high latency' and 'intermittent errors' conveys that some features (payment processing) are affected while others might still function. The key is to communicate *how* the issue impacts users – in this case, 'failed transactions' – rather than simply stating the system is down; a crucial element of effective status page communication.
8 / 31
David posted this PR description before initiating a rollback:
"Minor performance degradation observed on the user authentication service. Investigating potential correlation with recent code changes. Monitoring shows increased request latency."David's description is appropriate because it focuses on observed symptoms—increased latency—and avoids hyperbole. While further investigation is needed, framing the issue as a 'performance degradation' allows for a measured response. Options A and C are too alarmist or demand immediate escalation that isn't warranted at this stage; option D asks for unnecessary detail before understanding the problem.9 / 31
Mark, a SRE, is drafting a status page update for a recent outage affecting the user profile service. He's considering these options:
A: 'Service degraded due to an unknown issue.' B: 'User profiles are currently unavailable. We are investigating and expect a resolution within 15-30 minutes.' C: 'Experiencing intermittent connectivity issues with user profile data.' D: 'The system is experiencing high error rates, impacting user profile access.'
Option B is the most appropriate. A status page update should immediately inform users of the problem and provide an estimated resolution timeframe – this is crucial for managing expectations. Options A and C are too vague; they lack specifics about the impact and action being taken. Option D focuses solely on error rates without conveying the user-facing consequences, which is less effective communication.
10 / 31
Sarah posted this comment on a PR describing a recent outage:
"The API is intermittently returning 502 errors. We've rolled back the deployment, but it's still happening. Users are reporting timeouts."This scenario demonstrates a common situation where developers need to communicate the severity of an incident clearly. Option A is too strong - 'completely unavailable' isn't necessarily accurate if some users *can* still access parts of the system. Option B describes poor performance, not an outage. Option C suggests a critical bug requiring immediate escalation – while potentially true, the description doesn't fully convey the intermittent nature of the problem. The correct answer accurately reflects the situation: 'intermittent instability' aligns with the reported 502 errors and timeouts, acknowledging ongoing investigation.
11 / 31
John posted this update to the team Slack channel during a status page incident:
"We're seeing high latency on the payment gateway. Users are reporting failed transactions. The monitoring system is showing increased CPU utilization on the database servers. We've initiated scaling of the gateway, but it's not yet resolved."This update accurately describes a partial service degradation. Using phrases like 'high latency' and 'intermittent errors' conveys that some features (payment processing) are affected while others might still function. The key is to communicate *how* the issue impacts users – in this case, 'failed transactions' – rather than simply stating the system is down; a crucial element of effective status page communication.
12 / 31
David posted this PR description before initiating a rollback:
"Minor performance degradation observed on the user authentication service. Investigating potential correlation with recent code changes. Monitoring shows increased request latency."David's description is appropriate because it focuses on observed symptoms—increased latency—and avoids hyperbole. While further investigation is needed, framing the issue as a 'performance degradation' allows for a measured response. Options A and C are too alarmist or demand immediate escalation that isn't warranted at this stage; option D asks for unnecessary detail before understanding the problem.13 / 31
Mark, a SRE, is drafting a status page update for a recent outage affecting the user profile service. He's considering these options:
A: 'Service degraded due to an unknown issue.' B: 'User profiles are currently unavailable. We are investigating and expect a resolution within 15-30 minutes.' C: 'Experiencing intermittent connectivity issues with user profile data.' D: 'The system is experiencing high error rates, impacting user profile access.'
Option B is the most appropriate. A status page update should immediately inform users of the problem and provide an estimated resolution timeframe – this is crucial for managing expectations. Options A and C are too vague; they lack specifics about the impact and action being taken. Option D focuses solely on error rates without conveying the user-facing consequences, which is less effective communication.
14 / 31
Sarah posted this comment on a PR describing a recent outage:
"The API is intermittently returning 502 errors. We've rolled back the deployment, but it's still happening. Users are reporting timeouts."This scenario demonstrates a common situation where developers need to communicate the severity of an incident clearly. Option A is too strong - 'completely unavailable' isn't necessarily accurate if some users *can* still access parts of the system. Option B describes poor performance, not an outage. Option C suggests a critical bug requiring immediate escalation – while potentially true, the description doesn't fully convey the intermittent nature of the problem. The correct answer accurately reflects the situation: 'intermittent instability' aligns with the reported 502 errors and timeouts, acknowledging ongoing investigation.
15 / 31
John posted this update to the team Slack channel during a status page incident:
"We're seeing high latency on the payment gateway. Users are reporting failed transactions. The monitoring system is showing increased CPU utilization on the database servers. We've initiated scaling of the gateway, but it's not yet resolved."This update accurately describes a partial service degradation. Using phrases like 'high latency' and 'intermittent errors' conveys that some features (payment processing) are affected while others might still function. The key is to communicate *how* the issue impacts users – in this case, 'failed transactions' – rather than simply stating the system is down; a crucial element of effective status page communication.
16 / 31
David posted this PR description before initiating a rollback:
"Minor performance degradation observed on the user authentication service. Investigating potential correlation with recent code changes. Monitoring shows increased request latency."David's description is appropriate because it focuses on observed symptoms—increased latency—and avoids hyperbole. While further investigation is needed, framing the issue as a 'performance degradation' allows for a measured response. Options A and C are too alarmist or demand immediate escalation that isn't warranted at this stage; option D asks for unnecessary detail before understanding the problem.17 / 31
Mark, a SRE, is drafting a status page update for a recent outage affecting the user profile service. He's considering these options:
A: 'Service degraded due to an unknown issue.' B: 'User profiles are currently unavailable. We are investigating and expect a resolution within 15-30 minutes.' C: 'Experiencing intermittent connectivity issues with user profile data.' D: 'The system is experiencing high error rates, impacting user profile access.'
Option B is the most appropriate. A status page update should immediately inform users of the problem and provide an estimated resolution timeframe – this is crucial for managing expectations. Options A and C are too vague; they lack specifics about the impact and action being taken. Option D focuses solely on error rates without conveying the user-facing consequences, which is less effective communication.
18 / 31
Sarah posted this comment on a PR describing a recent outage:
"The API is intermittently returning 502 errors. We've rolled back the deployment, but it's still happening. Users are reporting timeouts."This scenario demonstrates a common situation where developers need to communicate the severity of an incident clearly. Option A is too strong - 'completely unavailable' isn't necessarily accurate if some users *can* still access parts of the system. Option B describes poor performance, not an outage. Option C suggests a critical bug requiring immediate escalation – while potentially true, the description doesn't fully convey the intermittent nature of the problem. The correct answer accurately reflects the situation: 'intermittent instability' aligns with the reported 502 errors and timeouts, acknowledging ongoing investigation.
19 / 31
John posted this update to the team Slack channel during a status page incident:
"We're seeing high latency on the payment gateway. Users are reporting failed transactions. The monitoring system is showing increased CPU utilization on the database servers. We've initiated scaling of the gateway, but it's not yet resolved."This update accurately describes a partial service degradation. Using phrases like 'high latency' and 'intermittent errors' conveys that some features (payment processing) are affected while others might still function. The key is to communicate *how* the issue impacts users – in this case, 'failed transactions' – rather than simply stating the system is down; a crucial element of effective status page communication.
20 / 31
David posted this PR description before initiating a rollback:
"Minor performance degradation observed on the user authentication service. Investigating potential correlation with recent code changes. Monitoring shows increased request latency."David's description is appropriate because it focuses on observed symptoms—increased latency—and avoids hyperbole. While further investigation is needed, framing the issue as a 'performance degradation' allows for a measured response. Options A and C are too alarmist or demand immediate escalation that isn't warranted at this stage; option D asks for unnecessary detail before understanding the problem.21 / 31
Mark, a SRE, is drafting a status page update for a recent outage affecting the user profile service. He's considering these options:
A: 'Service degraded due to an unknown issue.' B: 'User profiles are currently unavailable. We are investigating and expect a resolution within 15-30 minutes.' C: 'Experiencing intermittent connectivity issues with user profile data.' D: 'The system is experiencing high error rates, impacting user profile access.'
Option B is the most appropriate. A status page update should immediately inform users of the problem and provide an estimated resolution timeframe – this is crucial for managing expectations. Options A and C are too vague; they lack specifics about the impact and action being taken. Option D focuses solely on error rates without conveying the user-facing consequences, which is less effective communication.
22 / 31
Emily, a SRE, is writing an update for the status page regarding a degraded API endpoint. The monitoring system indicates increased error rates and slow response times. Which of the following best describes how to phrase this initial notification to users?
'API experiencing intermittent issues.'
Option B is best because it clearly states the problem (latency & errors) and indicates ongoing investigation. Options A is too vague, C downplays the severity, and D isn't specific enough for a status page update – users need to understand *what* is happening.
23 / 31
Reviewer Alex comments on a PR describing a recent outage:
"The service returned 503 errors. We've deployed a hotfix; however, the errors persist. The monitoring dashboard shows high CPU utilization."
Which of the following responses best aligns with providing clear and actionable information in this scenario?
'The system is unstable.'
Option A correctly identifies the core problem (high CPU) and acknowledges the deployment of a fix. It's more specific than other options which are too general or simply state that there was a problem without detailing the ongoing impact. Options B and D don't provide enough technical detail.
24 / 31
During a Slack conversation about an outage affecting the user authentication service, David writes:
"We're seeing a high volume of failed login attempts. The monitoring system is reporting increased latency on the auth server. Users are reporting being unable to log in."
What's the most appropriate follow-up message to add, focusing on clarity and next steps?
'The service is down.'
Option B provides specific details about *why* users can't log in (surge in requests) and clearly links it to the monitoring data. It avoids vague statements like 'the service is down' which doesn't convey urgency or the cause of the issue. Options A and D are too generic.
25 / 31
Mark, an SRE, needs to update the status page for a service experiencing intermittent timeouts. He drafts:
'Service degraded due to an unknown issue.'
Which of the following improvements would be MOST effective in this initial draft?
Adding details about affected users or specific API endpoints
Option B immediately adds crucial context – the fact that it's causing timeouts. This shows users *how* they are impacted and indicates active investigation. Options A and C are too vague, while D is an overly negative statement.
26 / 31
The status page for the 'Phoenix' service is reporting high latency. Sarah, an SRE, needs to update the team. Which of the following statements would be MOST appropriate for her initial Slack message?
Context: The monitoring system shows increased network traffic and CPU usage.
Option B is the most appropriate initial response. It acknowledges the user reports (crucial for status pages) and indicates an investigation is underway. Options A, C, and D are too specific or suggest a definitive cause without sufficient data.
27 / 31
David, a DevOps engineer, is writing a PR description to explain an outage affecting the 'Aurora' service. The monitoring system shows increased error rates and slow response times. Which of the following best describes how to phrase this update for the status page?
Context: A recent code deployment triggered the issue.
Option B accurately reflects the situation – a faulty deployment caused the degradation and a rollback was initiated. This provides crucial context for users and indicates corrective action has been taken. Options A is too vague, C doesn't provide information, and D includes an estimated recovery time which isn't yet known.
28 / 31
John, a SRE, needs to update the status page for the 'Nova' service. The monitoring system indicates increased error rates and slow response times. Which of the following is the MOST effective way to describe the issue in the initial status page update?
Context: The root cause is a memory leak in a recently updated component.
Option B provides the most specific and actionable information. It clearly states the root cause (memory leak) and confirms a hotfix was deployed. This allows users to understand what's happening and why it's being addressed.
29 / 31
Reviewer Alex comments on a PR describing a recent outage:
"The service returned 503 errors. We've deployed a hotfix; however, the errors persist. The monitoring dashboard shows high CPU utilization."
Which of the following phrases would be MOST appropriate for Mark, an SRE, to add to this comment before requesting further investigation?
A: 'This is a minor issue and should resolve itself.'
B: 'We've deployed a hotfix - let's monitor closely!'
C: 'The persistent 503 errors and high CPU utilization indicate a potential bottleneck or new problem requiring immediate attention.'
D: 'It's just a temporary spike in traffic.'
Option C is crucial because it accurately interprets the provided data – persistent errors and high CPU – as signaling a significant issue needing investigation. The other options downplay the severity or offer inappropriate responses (e.g., assuming it's minor).
30 / 31
Mark, an SRE, needs to update the status page for a service experiencing intermittent timeouts. He drafts:
'Service degraded due to an unknown issue.'
Which of the following improvements would be MOST effective in providing immediate clarity and reducing user anxiety?
A: 'The service is currently unavailable.'
B: 'We're investigating intermittent timeouts on the service, which may result in temporary delays. We expect a resolution within 15 minutes.'
C: 'Everything is fine – just a hiccup!'
D: 'The system is experiencing unusual behavior.'
Option B offers the most informative and reassuring update. It clearly states the problem (intermittent timeouts), explains the potential impact (temporary delays), and provides an estimated resolution time. This transparency helps users understand the situation and manage their expectations.
31 / 31
Sarah, an SRE, is drafting a status page update for a service experiencing high latency. The monitoring system shows increased error rates and slow response times. Which of the following statements would be MOST appropriate to include regarding the potential root cause?
A: 'The issue is likely caused by a recent code deployment.'
B: 'We are investigating potential issues with database performance, which may contribute to the latency.'
C: 'It's probably just a temporary problem.'
D: 'The system is experiencing some network connectivity problems.'
Option B is best because it acknowledges that database performance could be a factor. It demonstrates an understanding of potential causes and shows proactive investigation. Options A and C are too speculative, while option D is vague.
Frequently Asked Questions
What does the "Status Page Writing — Incident Update Vocabulary" exercise cover?
Learn to write clear, professional status page updates during incidents.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Status Page Writing — Incident Update Vocabulary"?
This exercise has 31 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more External Crisis Communication exercises?
Browse the full External Crisis Communication hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.