Website · iitm.ac.in

Is IIT Madras down?

iitm.ac.in education IN
DOWN
IIT Madras · iitm.ac.in
Unreachable via all 4 probe methods
HTTPS · 109 ms
94.74% uptimelast 30 days
See full history →
2026-06-27: no data2026-06-28: no data2026-06-29: no data2026-06-30: no data2026-07-01: no data2026-07-02: no data2026-07-03: no data2026-07-04: no data2026-07-05: no data2026-07-06: no data2026-07-07: no data2026-07-08: no data2026-07-09: no data2026-07-10: no data2026-07-11: no data2026-07-12: no data2026-07-13: no data2026-07-14: no data2026-07-15: no data2026-07-16: no data2026-07-17: no data2026-07-18: no data2026-07-19: no data2026-07-20: no data2026-07-21: no data2026-07-22: no data2026-07-23: no data2026-07-24: no data2026-07-25: no data2026-07-26: partial outage, 94.7% uptime, 95 checks
30 days agocollecting data · 1/30 daystoday
Checked 1s ago 4/4 probe methods returned data every 5 min · HTTP probe direct probe, not crowd-reported

Per-method results

HTTP/1.1 DOWN
-
blocked: getaddrinfo EBUSY iitm.ac.in
HTTP/2 DOWN
-
blocked: getaddrinfo EBUSY iitm.ac.in
Browser UA DOWN
-
blocked: getaddrinfo EBUSY iitm.ac.in
curl HEAD DOWN
-
blocked: getaddrinfo EBUSY iitm.ac.in

HTTP details

HTTP status
-
Response time
109 ms
Region consensus
0/4 reachable
24h success rate
0% (0/1 probes)

90-day uptime

93.81% 91/97 probes succeeded · 6 failed · 1/90 days with data · UTC
≥99.9% ≥99% ≥95% <95% no data

Network

Host
iitm.ac.in
Port
443
Transport
HTTPS
What this means

IIT Madras failed all 4 probe methods.

This is a confirmed outage. Most users worldwide are affected. Check the provider's status page or socials for an ETA, no client-side fix will help.

What to try next

Wait it out

Confirmed outages need fixing on the provider's side. Nothing you do locally will change the result.

Check related

Scroll to related services below to see if the outage is provider-wide.

Re-run

Reload this page to re-probe, we check on-demand as well as on the 5-minute cadence.

FAQ

Why is IIT Madras down right now?
Outages typically come from CDN/DNS issues, failed deploys, regional routing problems, or DDoS. We can't see IIT Madras's internal cause, we only confirm reachability from each probe method. If all 4 probe methods failed, it's a confirmed outage on IIT Madras's side. If only some failed, IIT Madras is up but blocking or mishandling a specific request type.
Is IIT Madras down for everyone or just me?
Look at the probe-method grid above. If every probe method succeeded, the issue is local to your network, flush DNS, switch networks, or disable your VPN. If two or more probe methods failed, the outage is on IIT Madras's side.
How often does isitdown.io re-check IIT Madras?
Every 5 minutes via background HTTP probes using 4 independent probe methods. You can also re-run on demand by reloading, the verdict above reflects the latest probe.

Get alerted when it goes down

Free account: 5 monitors with email alerts, checked every 5 minutes. Pro checks every minute and adds Discord + webhook alerts and a public status page.

Monitor IIT Madras — free One click — the form comes prefilled. No credit card.

Status badge

Embed a live status badge on your site, README, or status page. Updates automatically, same status-aware SVG the rest of isitdown.io uses.

IIT Madras status
<a href="https://isitdown.io/website/iitm.ac.in"><img src="https://isitdown.io/badge/iitm.ac.in.svg" alt="IIT Madras status"></a>

Related · education

Methodology

Probe
We send a GET request to the target URL with each probe method and time the full response.
Counts as DOWN
Every probe method fails the request (connect refused, DNS error, timeout, or HTTP 5xx).
Counts as DEGRADED
At least one probe method succeeds but at least one fails, the site is up but blocking or mishandling a specific request type.
Detail
Per-method results include HTTP status code, response time, and best-effort DNS / connect / TLS / first-byte phase timings when the Node HTTP client exposes them.
Cadence
Every 5 minutes, in parallel across 4 independent probe methods (HTTP/1.1 with strict TLS, HTTP/2, a browser User-Agent GET, and a curl-style HEAD) from our edge network. We check probe diversity, not geography — if a site blocks a non-browser User-Agent or only speaks HTTP/1.1, the four cards show it.
Rate-limited targets
If a host returns 429 or consistently drops connections from our IPs, we cap retries at 3 and report the last observed status, we do not flood the target to confirm the outage.
Data source
Our verdict is based on direct multi-method probes, every result above is a live network request, never a Twitter mention or DownDetector aggregate. User reports, when shown, appear separately below as a supplementary signal and are never used to determine the up/down verdict.
JSON: /check?target=iitm.ac.in&format=json Share: https://isitdown.io/check/iitm.ac.in