Live - 300+ check locations
Is Perplexity down right now?
HostTracker's monitoring network reached www.perplexity.ai and completed a full check without errors. It has been up for 40d 7h.
Stop finding out from a search - HostTracker's website monitoring checks the services you depend on from 300+ locations and alerts you the moment one changes.
Up
for 40d 7h
- Last check
- just now
- Next check
- -
- HTTP
- -
Checking www.perplexity.ai right now
A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.
Perplexity status
What Perplexity's own status page reports - separate from HostTracker's own checks above.
Operational according to Perplexity's status page, updated just now
No open incidents on Perplexity's status page.
Perplexity parts
4 parts on its status page- Website
- App
- Computer
- API
Last 90 days on Perplexity's status page
The newest 1025 incidents: 7 critical, 10 major, 6 minor and 2 not rated.
- Elevated API errors and timeouts Minor impact 37m
- Issue with usage based billing Critical impact 1m
- We have identified few connectors that are impacting users. Major impact 1m
- Computer Tasks Degraded Not rated 16m
- Computer Sandbox Errors Minor impact 1m
- Investigating API issue Critical impact 1m
- Computer Sandbox Issue Minor impact 1m
- Computer sandbox issues Critical impact 1m
- Computer Sandbox Issue Major impact 1m
- Computer Sandbox Issue Critical impact 1m
HostTracker is not affiliated with Perplexity. Incident text is quoted briefly from their status page, with a link to the full post.
Want this on Slack, Teams, SMS or email, only for the parts you use? See Vendor Watch below.
How Perplexity has behaved
Every figure here comes from HostTracker's own checks of www.perplexity.ai, not from the vendor's status page.
Response time
12ms avg · 74ms peak
What we check
-
Ping12 ms average, every 10 minutesOK
90-day uptime
100.000% over 42 measured days · 0 incidents
- Operational
- Degraded
- Down
- No data
Incident history
Last 90 daysNo incidents recorded in the last 90 days.
Get alerted the next time Perplexity goes down
One alert per incident, on Slack, Teams, SMS or email, and only for the parts you use. To start, we pre-select API and Website.
- Perplexity's own post, linked and quoted
- Problem reports from people on this page
30-day trial, no card. Perplexity comes pre-selected - nothing is watched until you press Start watching.
Already have an account? Sign in
HostTracker is not affiliated with Perplexity.
Is Perplexity not working for you?
Tell us what is broken. One click, no account.
One report per visitor per hour. We keep only the country and the problem type, never your IP address.
Problem reports, last 24 hours
Reports come from visitors of this page. A sharp rise above the usual level, together with failed checks in the live check below, means the problem is on Perplexity's side, not yours.
Top reported problems
Share of reports in the last 2 hours.
About Perplexity outages
Written by the HostTracker monitoring team · updated from live probe data.
Perplexity is an AI answer engine that pairs live web search with a language model to produce cited, sourced responses rather than a chat reply drawn only from training data - which gives it two layers that can fail separately. A search-backend incident can leave Perplexity able to generate fluent answers with stale or missing sources, while an incident at the underlying model provider can do the reverse: search results return fine but the generated answer stalls or errors out. It's also used through more than one surface - the website, dedicated apps, and a browser extension - and these can diverge, with one working normally while another fails after an update or a regional issue specific to that client.
Common causes of Perplexity downtime
Not sure whether it's Perplexity or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.
Search-backend incidents that degrade the live web results Perplexity cites, producing answers with missing or stale sources even when the model itself is responding
Incidents at the underlying model providers Perplexity uses to generate answers, which can stall or error out responses while search itself works
Rate limiting on free and subscriber tiers that blocks further queries in a way that can resemble a service failure
Divergence between the web app, the dedicated apps and the browser extension, where one surface fails after an update while the others keep working normally
Other services we track
AWSOperational
G
InstagramOperational
X
AmazonOperational
T
ShopifyOperational
DHostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 14 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.
Questions people ask during an outage
The live probe run on this page tests www.perplexity.ai from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than Perplexity being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.
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 40d 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 40d 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.