User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Profound down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → tryprofound.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 54 min ago. Last stored result reached it in 30 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 26 ms | 0 |
| Mon 17 | 0 | 0.0 | 145 ms | 0 |
| Mon 19 | 0 | 0.0 | 57 ms | 0 |
| Mon 21 | 0 | 0.0 | 62 ms | 0 |
| Mon 23 | 0 | 0.0 | 126 ms | 0 |
| Tue 01 | 0 | 0.0 | 44 ms | 0 |
| Tue 03 | 0 | 0.0 | 25 ms | 0 |
| Tue 05 | 0 | 0.0 | 48 ms | 0 |
| Tue 08 | 0 | 0.0 | 37 ms | 0 |
| Tue 10 | 0 | 0.0 | 26 ms | 0 |
| Tue 12 | 0 | 0.0 | 52 ms | 0 |
| Tue 14 | 0 | 0.0 | 9 ms | 0 |
| Tue 16 | 0 | 0.0 | 101 ms | 0 |
| Tue 19 | 0 | 0.0 | 67 ms | 0 |
| Tue 21 | 0 | 0.0 | 98 ms | 0 |
| Tue 23 | 0 | 0.0 | 117 ms | 0 |
| Wed 01 | 0 | 0.0 | 24 ms | 0 |
| Wed 04 | 0 | 0.0 | 54 ms | 0 |
| Wed 06 | 0 | 0.0 | 148 ms | 0 |
| Wed 08 | 0 | 0.0 | 13 ms | 0 |
| Wed 10 | 0 | 0.0 | 96 ms | 0 |
| Wed 13 | 0 | 0.0 | 119 ms | 0 |
| Wed 15 | 0 | 0.0 | 40 ms | 0 |
| Wed 17 | 0 | 0.0 | 32 ms | 0 |
| Wed 19 | 0 | 0.0 | 273 ms | 0 |
| Wed 21 | 0 | 0.0 | 97 ms | 0 |
| Wed 23 | 0 | 0.0 | 33 ms | 0 |
| Thu 02 | 0 | 0.0 | 122 ms | 0 |
| Thu 04 | 0 | 0.0 | 25 ms | 0 |
| Thu 06 | 0 | 0.0 | 276 ms | 0 |
| Thu 08 | 0 | 0.0 | 133 ms | 0 |
| Thu 10 | 0 | 0.0 | 24 ms | 0 |
| Thu 12 | 0 | 0.0 | 48 ms | 0 |
| Thu 14 | 0 | 0.0 | 234 ms | 0 |
| Thu 16 | 0 | 0.0 | 44 ms | 0 |
| Thu 18 | 0 | 0.0 | 288 ms | 0 |
| Thu 20 | 0 | 0.0 | 166 ms | 0 |
| Thu 22 | 0 | 0.0 | 22 ms | 0 |
| Thu 23 | 0 | 0.0 | 120 ms | 0 |
| Fri 01 | 0 | 0.0 | 46 ms | 0 |
| Fri 03 | 0 | 0.0 | 73 ms | 0 |
| Fri 05 | 0 | 0.0 | 182 ms | 0 |
| Fri 07 | 0 | 0.0 | 120 ms | 0 |
| Fri 09 | 0 | 0.0 | 26 ms | 0 |
| Fri 11 | 0 | 0.0 | 62 ms | 0 |
| Fri 14 | 0 | 0.0 | 15 ms | 0 |
| Fri 16 | 0 | 0.0 | 169 ms | 0 |
| Fri 17 | 0 | 0.0 | 30 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Profound badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Profound yet. Outages of 10 minutes or more get their own page here.
Having trouble with Profound?
One report per service every 10 minutes from this network. No account.
Follow Profound
Get an email when Profound goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Profound alerts to Slack, Discord or a webhook — free.
About Profound
We track Profound (tryprofound.com) as part of the AI group. Profound is the AI marketing platform built for the agentic era. See what your customers ask AI, deploy agents to act on it, and measure the results in a collaborative workbench
Profound publishes an official status page at status.tryprofound.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 101 ms average, 15–288 ms range across 13 successful checks.
Questions
Is Profound down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Profound last down?
We have not recorded a public Profound incident since monitoring began 8 days ago.
What is Profound's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Profound respond?
101 ms on average over the last 24 hours (15–288 ms).
Does Profound have an official status page?
Yes, at https://status.tryprofound.com.
Profound not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Profound here at once, the problem is on Profound's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Profound. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.