Is GeM Portal Down?
Yes, we are detecting problems with GeM Portal that began 1 minute ago.
Service returned HTTP 0. Error: Connection timeout or resolution failure: cURL error 28: Connection timed out after 8001 milliseconds (see https://curl.se/libcurl/c/libcurl-errors.html) for https://gem.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 GeM Portal Issues
If you're experiencing issues with GeM Portal, try these troubleshooting steps:
Basic Steps
- 1. Verify your internet connection & proxy settings. GeM Portal uses secure government-grade connections, so if your organization enforces a proxy or VPN, ensure it is active and not blocking gem.gov.in. Try opening a known government site (e.g., india.gov.in) to confirm general connectivity.
- 2. Clear browser cache, cookies, and site data. The GeM portal frequently updates its UI and security tokens. Stale cache can cause login loops, missing buttons, or frozen certificate upload forms. After clearing, hard-refresh with Ctrl + F5 (Windows) or Cmd + Shift + R (Mac).
- 3. Test on an alternate browser or incognito window. GeM works best on current versions of Chrome, Edge, or Firefox. Disable all browser extensions (especially ad-blockers or password managers) that may interfere with the portal's JavaScript and digital signature pop-ups.
- 4. Restart your device and router. A simple reboot clears DNS caching and resets intermittent TCP/IP failures, which are common when uploading large bid documents or viewing tender files on GeM.
- 5. Verify your digital signature certificate (DSC) is plugged in and recognized. If you are a buyer or seller performing e-sign actions, check that your USB token/dongle is properly inserted and that the vendor's middleware (e.g., eMudhra, Sify, Capricorn) is running in the system tray.
Intermediate Steps
- 1. Check GeM's known peak-hour issues. The portal experiences heavy load between 10:00 AM and 1:00 PM IST, especially during financial year-end (March) or when new tenders are published. If pages load slowly or time out, wait 15–20 minutes and retry instead of refreshing repeatedly.
- 2. Flush DNS and reset network stack. Open Command Prompt as administrator and run ipconfig /flushdns, ipconfig /release, ipconfig /renew, and netsh winsock reset. Then restart your system. This resolves occasional "cannot reach server" errors caused by stale ISP routing to GeM's government CDN.
- 3. Test with a different network (mobile hotspot). Some office or institutional networks block non-standard ports or specific government endpoints. Switching to a personal mobile hotspot confirms whether your ISP or firewall is the culprit. If the portal works on mobile data, ask your network admin to allowlist gem.gov.in and its subdomains.
- 4. Temporarily disable your antivirus or firewall's HTTPS scanning. Security software sometimes intercepts GeM's SSL handshake, causing "Your connection is not private" warnings or a blank white screen. Add gem.gov.in to your antivirus's trusted sites list, then retry. Re-enable protection immediately afterward.
Still facing problems?
If none of the above steps resolve the issue, the problem may be on the GeM Portal's server side, not your local system. Use the 'Report Outage' button on this Is It Down Bro? status page to let our monitoring system know — this helps us track global or regional incidents and provides you with real-time status updates.
Troubleshooting & FAQs
Recent GeM Portal 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.