Is SWAYAM Down?
Yes, we are detecting problems with SWAYAM that began 1 minute ago.
Service returned HTTP 0. Error: cURL error 60: SSL: no alternative certificate subject name matches target host name 'www.swayam.gov.in' (see https://curl.se/libcurl/c/libcurl-errors.html) for https://www.swayam.gov.in
Real-time Incident Detection Chart
Spikes in user reports (line) mapped against status page traffic baseline (bars) detect outages via Z-score analysis.
Community Status Activity
Recent user-submitted feedback and problems reported.
Loading recent activity...
Troubleshooting SWAYAM Issues
If you're experiencing issues with SWAYAM, try these troubleshooting steps:
Basic Steps
- 1. Check SWAYAM's server status first. Since SWAYAM is a centralized national e-learning platform, widespread outages are common during exam registration or result announcement periods. Look for any banners on the homepage before troubleshooting locally.
- 2. Refresh and clear your browser cache. SWAYAM uses heavy JavaScript and video streaming components. Press Ctrl + F5 (Windows) or Cmd + Shift + R (Mac) to bypass cached files. Also, clear cookies for swayam.gov.in specifically, as stale session cookies often cause login loops.
- 3. Test your internet connection and firewall. SWAYAM requires a stable broadband connection (minimum 2 Mbps for video lectures). If you're on a college or office network, ensure that ports for streaming.swayam.gov.in and swayam.gov.in are not blocked, as many institutional firewalls restrict these domains.
- 4. Try a different browser or device. SWAYAM is optimized for Google Chrome and Mozilla Firefox (latest versions). If you're using Safari or an older browser, switch. Also, test on your mobile data (4G/5G) to rule out your Wi-Fi router issues.
- 5. Disable VPN and ad-blockers. SWAYAM flags certain VPN IP ranges as bot traffic, leading to "Access Denied" errors. Temporarily disable any ad-blocking or script-blocking extensions (like uBlock or NoScript) on the SWAYAM domain.
Intermediate Steps
- 1. Check your SWAYAM account session and exam window. A common issue is getting stuck on "Test Your Bandwidth" or "Login" pages. Ensure you're not using multiple tabs with the same account, as SWAYAM uses single-session tokens. Additionally, if you're trying to access a Proctored Exam or Final Certificate, confirm that the exam window is actually open—SWAYAM often closes access outside specified hours (IST).
- 2. Flush your DNS and renew IP lease. Open Command Prompt (as administrator) and run: ipconfig /flushdns then ipconfig /renew. Also, switch your DNS to Google (8.8.8.8) or Cloudflare (1.1.1.1) because SWAYAM's CDN (from Arnes or other educational networks) sometimes misroutes on ISP default DNS.
- 3. Synchronize your system time and timezone. SWAYAM uses time-stamped tokens for course access and quiz submissions. If your device clock is more than 2 minutes off (even due to timezone miscalibration), you'll get a "Request Timeout" or "Session Expired" error. Go to Settings > Date & Time and enable "Set Automatically."
- 4. Clear browser application data for video players. SWAYAM's lecture player is built on HLS (HTTP Live Streaming). If videos buffer infinitely, navigate to your browser settings and clear site data for d2lvlj452s8h6w.cloudfront.net (their video delivery domain) or disable hardware acceleration if using Chrome, as outdated GPU drivers frequently cause black screens.
Still facing issues? If none of the above solutions resolve your problem, the outage might be on SWAYAM's end. Please click the 'Report Outage' button on this page to let us and other users know that SWAYAM is not working for you today.
Troubleshooting & FAQs
Recent SWAYAM Outages
Helpline Info
Support details
Embeddable Status Badge
Add this dynamic SVG status shield to your customer docs, readme, or dashboard.
Status Methodology
Outage Detection: We check website availability using network scanners every minute. If a response fails, we perform automated retries.
Community Reporting: Spikes in user reports are analyzed via standard deviations (Z-score). Z-scores above 2.0 indicate a high likelihood of a localized or major outage.
Geolocating: Crowdsourced feedback tracks country origins using public IP-API geo databases to map the scope of outages.