Checked 1s ago·4/4 regions returned data·every 5 min · HTTP probe·direct probe, not crowd-reported
各区域结果
🇺🇸US East正常
17 msHTTP 301
🇺🇸US West正常
265 msHTTP 301
🇬🇧Europe正常
281 msHTTP 301
🇸🇬Asia正常
18 msHTTP 301
HTTP 详情
HTTP status
301
Response time
17 ms
Region consensus
4/4 reachable
24h success rate
100% (1/1 probes)
24h latency
145–145 ms · 145 ms avg
Last successful probe
1s ago
耗时分解
DNS lookup
8 ms
TCP connect
2 ms
TLS handshake
3 ms
First byte
4 ms
Total
17 ms
网络
Host
singtel.com
Port
443
Transport
HTTPS
结果解读
Singtel 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.
下一步操作
Check your DNS
Flush your DNS cache: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS.
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 Singtel down right now?
Outages typically come from CDN/DNS issues, failed deploys, regional routing problems, or DDoS. We can't see Singtel's internal cause — we only confirm reachability from each monitoring region. If all 4 regions failed, it's a confirmed outage on Singtel's side. If only some failed, the impact is regional.
Is Singtel 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 Singtel's side.
How often does isitdown.io re-check Singtel?
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.
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.
数据来源
Direct probes from our monitoring infrastructure. We do not aggregate crowd reports, Twitter mentions, or DownDetector signals — every result on this page is a live network request.