Is Cricbuzz down?
cricbuzz.com is reachable but answered 403 to our probes. It is probably up and blocking automated or regional traffic — not an outage.
- Website
- cricbuzz.com
- Response time
- 755 ms (median)
- Uptime (24 h)
- 100%
- Last down
- no outage in 90 days
Report a problemNo problem reports in 24 h
Response time — last 24 checks
Median across 4 regions, one point every 2 minutes. Red markers = round failed.
Last 24 hours
One bar per hour · colour = success rate · height = median response.
Latest check by region
| Region | Result | Response | DNS | TLS expires | Server |
|---|---|---|---|---|---|
| Dallas, US | HTTP 403 | 2330 ms | 54 ms | — | AkamaiGHost |
| Washington DC, US | HTTP 403 | 961 ms | 67 ms | — | AkamaiGHost |
| Frankfurt, DE | HTTP 403 | 548 ms | 2 ms | — | AkamaiGHost |
| Singapore, SG | HTTP 403 | 292 ms | 70 ms | — | AkamaiGHost |
Resolves to: 13.235.191.202, 23.222.202.21, 2600:141b:f000:d083::3332, 2600:141b:f000:d087::3332
Service status history
| Time (UTC) | Regions OK | Response |
|---|---|---|
| 26 Oct 2026 16:06 UTC | 4/4 | 754 ms |
| 26 Oct 2026 16:04 UTC | 4/4 | 717 ms |
| 26 Oct 2026 16:02 UTC | 4/4 | 734 ms |
| 26 Oct 2026 16:00 UTC | 4/4 | 745 ms |
| 26 Oct 2026 15:58 UTC | 4/4 | 726 ms |
| 26 Oct 2026 15:56 UTC | 4/4 | 762 ms |
| 26 Oct 2026 15:54 UTC | 4/4 | 788 ms |
| 26 Oct 2026 15:52 UTC | 4/4 | 712 ms |
| 26 Oct 2026 15:50 UTC | 4/4 | 769 ms |
| 26 Oct 2026 15:48 UTC | 4/4 | 748 ms |
| 26 Oct 2026 15:46 UTC | 4/4 | 780 ms |
| 26 Oct 2026 15:44 UTC | 4/4 | 754 ms |
| Time (UTC) | Regions OK | Response |
|---|---|---|
| 26 Oct 2026 15:42 UTC | 4/4 | 830 ms |
| 26 Oct 2026 15:40 UTC | 4/4 | 706 ms |
| 26 Oct 2026 15:39 UTC | 4/4 | 794 ms |
| 26 Oct 2026 15:37 UTC | 4/4 | 727 ms |
| 26 Oct 2026 15:35 UTC | 4/4 | 784 ms |
| 26 Oct 2026 15:33 UTC | 4/4 | 764 ms |
| 26 Oct 2026 15:31 UTC | 4/4 | 750 ms |
| 26 Oct 2026 15:29 UTC | 4/4 | 732 ms |
| 26 Oct 2026 15:27 UTC | 4/4 | 734 ms |
| 26 Oct 2026 15:25 UTC | 4/4 | 760 ms |
| 26 Oct 2026 15:23 UTC | 4/4 | 821 ms |
| 26 Oct 2026 15:21 UTC | 4/4 | 708 ms |
Problems with Cricbuzz? Report it
No user reports in the last 24 hours. Anonymous, no account needed.
Recent comments
No comments yet. If something is broken for you, say so above — it helps everyone else.
What this result means
The server answered HTTP 403 to automated requests from every region. That is a security policy (bot protection or geo-blocking), not an outage — the site is most likely fine in a normal browser.
1 · Browser
- Hard-refresh: Ctrl+F5 (Mac: ⌘+Shift+R).
- Try a private/incognito window — rules out extensions and stale cookies.
- Clear cache & cookies for cricbuzz.com.
2 · DNS
- Flush DNS: Windows
ipconfig /flushdns, macOSsudo dscacheutil -flushcache. - Switch to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) DNS.
- Works on mobile data but not Wi-Fi? Your ISP's DNS or filtering is the culprit.
3 · Network
- Disable VPN/proxy, or turn one on if your region blocks the site.
- Check firewall, antivirus web-shield and parental controls.
- Restart your router; ask a friend elsewhere to open this page.
More in News
Outages happening right now
Verdict rule: DOWN when most regions fail, DEGRADED when some fail or the median exceeds 3 s, RESTRICTED when the site answers 401/403/429 to our probes. Checks come from Dallas, Washington DC, Frankfurt and Singapore. Share: https://isitdownorme.com/cricbuzz