Keeping Systems Running: Lessons from a Service Problem

Article Summary

On August 17, GitHub had a big service problem that lasted almost eight hours. This problem stopped many important services like logging in, GitHub Actions, and Copilot. It caused difficulties for developers and companies around the world who were trying to finish their work. This was the second problem GitHub faced in August, showing that they need to work faster to make their systems better and more dependable.

GitHub found that the problem started when too many people tried to use the service at once. A main computer system could not handle the new high number of users. This caused problems in other systems, leading to login failures and stopping many GitHub services. To fix this, teams changed how internet traffic was directed, separated the affected systems, and slowly brought services back online. Some parts took longer to fix because of extra traffic during the recovery.

GitHub says that these problems were not caused by bad code. Instead, the systems could not handle the large number of users. Since April, the number of tasks on GitHub has doubled. This shows why their systems are under pressure. To improve things, GitHub is adding more computer power and storage. They are also moving more services to a cloud platform called Azure to help manage the growing demand. They are also improving how they test new updates and watch their systems to prevent future issues.

Key Vocabulary

Comprehension Questions

1. What was the main problem GitHub faced on August 17?

• A planned system upgrade
• A power outage at their main office
• A service problem that stopped many systems
• A new feature release that failed

2. What did GitHub identify as the main reason for the service problems?

• Mistakes in their computer code
• Too many users trying to use the service at the same time
• A cyber attack from a competitor
• Old equipment that broke down suddenly

3. Why did GitHub start moving more of its services to Azure?

• To get a special discount from Azure
• To reduce its workforce
• To better handle growing user numbers and improve system capacity
• Because Azure offered faster internet speeds

4. Based on the article, what is GitHub still working on to improve its reliability?

• Developing completely new software from scratch
• Only focusing on fixing old equipment
• Improving how they test updates and watch their systems for problems
• Reducing the number of services they offer to users

5. Do you think GitHub's current plans will completely prevent all future service problems, and why?

• Yes, because they are adding a lot of new hardware.
• No, because technology always has unexpected issues.
• Yes, because they are moving to Azure completely.
• No, the article says 'this work is not complete' and there are always new challenges as systems grow.

Discussion Prompts

1. Has your company ever experienced a major service problem or outage? How did it affect your work and customers?

2. What steps does your company take to ensure its services or products are reliable for users?

3. How important is it for a business to communicate openly with customers when there is a service disruption?

Live Session Prep & Cheat Sheet

🎯 Speaking Targets (Vocabulary)

Try to use these target terms in your speaking turns:

• Outage
• Reliability
• Capacity
• Mitigate
• Availability

⚙️ Grammar Target Formula

Showing Cause and Effect: Cause + (due to / because of / as a result of) + Effect

💬 Discussion Openers

Use these phrases to open or structure your arguments:

• In my experience...
• What do you think about...?
• I agree/disagree because...
• Could you explain more about...?

Teacher Notes

This lesson focuses on understanding a business problem (service outage) and the steps taken to fix it. Emphasize B1 vocabulary related to IT and operations. Guide students to use cause-and-effect phrases naturally in discussions. The article summary is simplified, so encourage students to identify specific actions GitHub took.

Speaking Class Facilitation Guide (Tutors/Moderators Only)

🎭 Role-Play Scenario

Situation: Your company's main website or service has just experienced a major outage, affecting many customers. You need to inform customers and start the recovery process.

Goal: Work together to create a clear, reassuring message for customers and a plan for fixing the outage and future prevention.

⚖️ Debate Prompt

{"side_a":["Sharing details builds trust and shows transparency.","Customers feel more respected and understand the situation better.","It can help customers take their own steps if they understand the technical reasons."],"side_b":["Too many technical details can confuse customers.","It might make the company look less professional or capable.","Competitors could use the technical information against the company."],"question":"Should companies always share full technical details of service problems with customers?"}

💡 Discussion Facilitation Tips

Encourage students to use the vocabulary words like 'outage', 'reliability', and 'capacity' in their role-play and debate. Listen for correct use of 'due to' and 'because of' when students explain causes. Correct gently if needed. Ask follow-up questions to prompt deeper thinking, e.g., 'What are the possible long-term effects of this problem?'

Session Blueprint

Has your company ever experienced a major service problem or outage? How did it affect your work and customers?