Website · yelp.com

Is Yelp down?

yelp.com web
UP
Yelp · yelp.com
Reachable via all 4 probe methods
HTTPS · 21 ms
100.00% 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: operational all day, 82 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 UP
37 ms HTTP 301
HTTP/2 UP
36 ms HTTP 301
Browser UA UP
21 ms HTTP 301
curl HEAD UP
46 ms HTTP 301

HTTP details

HTTP status
301
Response time
21 ms
Region consensus
4/4 reachable
24h success rate
100% (1/1 probes)
24h latency
35-35 ms · 35 ms avg
Last successful probe
1s ago

90-day uptime

100.00% 82/82 probes succeeded · 1/90 days with data · UTC
≥99.9% ≥99% ≥95% <95% no data

Timing breakdown

First byte
21 ms
Total
21 ms

Network

Host
yelp.com
Port
443
Transport
HTTPS
What this means

Yelp is reachable from all 4 probe methods.

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

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.

Up but slow?

Run the speed test, first-byte, TLS, and download timing with a published grade, plus a check of your own connection.

Browser reset

Try an incognito window or a different browser, a bad extension or cached error page can masquerade as downtime.

FAQ

Why is Yelp down right now?
Outages typically come from CDN/DNS issues, failed deploys, regional routing problems, or DDoS. We can't see Yelp's internal cause, we only confirm reachability from each probe method. If all 4 probe methods failed, it's a confirmed outage on Yelp's side. If only some failed, Yelp is up but blocking or mishandling a specific request type.
Is Yelp 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 Yelp's side.
How often does isitdown.io re-check Yelp?
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 Yelp — 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.

Yelp status
<a href="https://isitdown.io/website/yelp.com"><img src="https://isitdown.io/badge/yelp.com.svg" alt="Yelp status"></a>

Related · web

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=yelp.com&format=json Share: https://isitdown.io/check/yelp.com