Check your DNS
Flush your DNS cache: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS.
Blockchain · evm
Is BNB Smart Chain down?
No, the BNB Smart Chain chain is producing fresh blocks and the public RPC answered every probe method.
UP
Collecting datano measured days yet of 30
30 days ago0/30 days measuredtoday
Checked 1s ago
single-source feed
every 5 min · HTTP probe
direct probe, not crowd-reported
Chain stats
- Latest block
- #115,032,775
- Block age
- 0s ago
- Expected block time
- 3s
- RPC latency
- 121ms
- RPC family
- evm
- Explorer
- https://bscscan.com
What this means
BNB Smart Chain is reachable.
If you still can't connect, the outage is on your side: DNS cache, VPN routing, ISP filtering, or a browser-level block. Try a different network or device to confirm.
What to try next
Try another network
Switch between Wi-Fi and mobile data, or disable your VPN. If it works there, the issue is on your primary network.
Browser reset
Try an incognito window or a different browser, a bad extension or cached error page can masquerade as downtime.
FAQ
Why is BNB Smart Chain down right now?
Outages typically come from CDN/DNS issues, failed deploys, regional routing problems, or DDoS. We can't see BNB Smart Chain's internal cause, we only confirm reachability from each probe method. If all 4 probe methods failed, it's a confirmed outage on BNB Smart Chain's side. If only some failed, BNB Smart Chain is up but blocking or mishandling a specific request type.
Is BNB Smart Chain 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 BNB Smart Chain's side.
How often does isitdown.io re-check BNB Smart Chain?
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.
Other chains
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.