Is Perplexity down right now?

Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.

No - as of the most recent check, www.perplexity.ai is responding normally to HostTracker's monitoring network, and has been up for 21d 7h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, www.perplexity.ai is responding normally to HostTracker's monitoring network, and has been up for 21d 7h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

It can be a narrower fault than a full outage. Perplexity generates answers by combining live web search with a language model, and a problem in the search-backend layer specifically can leave the model still producing fluent text while the citations behind it are missing, stale or wrong. That's a real degradation worth noting, but it's distinct from the service being unreachable - checking www.perplexity.ai's live status here tells you whether the site itself is up, separately from whether its search results are currently trustworthy.

Perplexity is used through several separate surfaces - the website, dedicated mobile and desktop apps, and a browser extension - and these don't always fail together. An app update, a regional app-store issue, or a bug specific to one client can break it there while the website keeps working perfectly, and the reverse happens too. If one surface fails and another works, the underlying service is very likely healthy and the problem is local to that specific client.

A response that starts and then stalls usually points at an issue with the model provider generating the text rather than the search layer that gathered sources for it - Perplexity separates the two, so search can complete successfully while generation fails afterward. This is a distinct failure pattern from the site being unreachable altogether, and retrying the query often succeeds if it was a transient issue on the model-serving side.