Check your DNS
Flush your DNS cache: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS.
网站 · flappyfruit.fun
Flappy Fruit 是否宕机?
flappyfruit.fun
crypto-gaming
正常
100.00% uptimelast 30 days
See full history →
30 days agocollecting data · 2/30 daystoday
Checked 1s ago
4/4 regions returned data
every 5 min · HTTP probe
direct probe, not crowd-reported
各区域结果
HTTP/1.1 · strict TLS
正常
47 ms
HTTP 308
HTTP/2 · relaxed TLS
正常
33 ms
HTTP 308
GET · browser UA
正常
28 ms
HTTP 308
HEAD · curl UA
正常
25 ms
HTTP 308
HTTP 详情
- HTTP status
- 308
- Response time
- 25 ms
- Region consensus
- 4/4 reachable
- 24h success rate
- 100% (5/5 probes)
- 24h latency
- 17-36 ms · 28 ms avg
- Last successful probe
- 1s ago
90-day uptime
100.00%
≥99.9%
≥99%
≥95%
<95%
no data
耗时分解
- DNS lookup
- 6 ms
- TCP connect
- 1 ms
- TLS handshake
- 7 ms
- First byte
- 11 ms
- Total
- 25 ms
网络
- Host
- flappyfruit.fun
- Port
- 443
- Transport
- HTTPS
结果解读
Flappy Fruit is reachable from all 4 monitoring regions.
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.
下一步操作
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 Flappy Fruit down right now?
Outages typically come from CDN/DNS issues, failed deploys, regional routing problems, or DDoS. We can't see Flappy Fruit's internal cause, we only confirm reachability from each monitoring region. If all 4 regions failed, it's a confirmed outage on Flappy Fruit's side. If only some failed, the impact is regional.
Is Flappy Fruit down for everyone or just me?
Look at the per-region grid above. If every region succeeded, the issue is local to your network, flush DNS, switch networks, or disable your VPN. If two or more regions failed, the outage is on Flappy Fruit's side.
How often does isitdown.io re-check Flappy Fruit?
Every 5 minutes via background HTTP probes from US East, US West, Europe, and Asia. You can also re-run on demand by reloading, the verdict above reflects the latest probe.
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.
<a href="https://isitdown.io/website/flappyfruit.fun"><img src="https://isitdown.io/badge/flappyfruit.fun.svg" alt="Flappy Fruit status"></a>
相关 · crypto-gaming
方法论
- 探测方式
- We send a GET request to the target URL from each region and time the full response.
- 计为宕机的条件
- Every region fails the request (connect refused, DNS error, timeout, or HTTP 5xx).
- 计为降级的条件
- At least one region succeeds but at least one fails, the outage is partial or regional.
- 细节
- Per-region results include HTTP status code, response time, and best-effort DNS / connect / TLS / first-byte phase timings when the Node HTTP client exposes them.
- 频率
- Every 5 minutes, in parallel across 4 monitoring regions (US East Virginia, US West Oregon, Europe London, Asia Singapore).
- 限速目标
- 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.
- 数据来源
- Our verdict is based on direct multi-region 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.