No reported issuesAn email when it goes down, and when it’s back.
As of 03:30 UTC on 12 November 2026, Code.org's status page reports no issues. Its last reported problem was on 19 October 2026: “Studio.Code.org is degraded”, issue, for 1 h 19 min from 15:41 UTC.
- Last problem
- 19 Oct · 1 h 19 min
- Problems, last 30 days
- 1
- Typical incident
- 20 h 22 min
- Longest in 90 days
- 20 h 22 min · 8 Oct
Uptime
Code.org, last 30 days
99.81 %
Biggest dip: Code.org, 1.3 h of issue on Oct 19.
Incidents
Started in the last 7 days
0
This week Week before
No incidents this week. The last one: Code.org, issue on Oct 19.
Recovery
Median time back online
1 h 19 min
0 of 1 were over within an hour. Each dot is one incident; the dashed line is the median.
Components 3
All online
- Code.org
- CSForAll.org
- Studio.Code.org
Last 90 days
2 incidents in 47 days tracked · no reported issues 98.1% of the time · typical incident 20 h 22 min
Recent incidents
Times in UTC
- Issues with WebLab and 1 more 1 h 19 min
Issue - Intermittent issues with Google Oauth Login 20 h 22 min Issue
Having issues right now
Paribu Humanity (H) Yatırma ve Çekme İşlemleri
CriticalAWS · Bahrain (me-south-1) Region Availability
CriticalAWS · UAE (me-central-1) Region Availability
CriticalGW Sistemas O componente “SAAS Webtrans” e alguns outros componentes estão Inativos
Critical
More in Education
All 215 in EducationWhere this comes from
Stackpulse reads Code.org’s official status page at status.code.org every minute and keeps 90 days of what changed. We don’t test Code.org ourselves, so a problem shows here once Code.org reports it.
Stackpulse isn’t affiliated with Code.org. Names and logos belong to their owners.
For agents and scripts
The same data as Markdown for AI agents, updated every 30 seconds. With Pro, the API and the MCP server give scripts and AI assistants every service and your own dashboards.