Skip to content

Outage tracker

You.com: incident history

The last 24 hours in detail, You.com's declared incident record, and our regional check results beside it.

← Back to You.com's check readings

We started checking You.com on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when You.com reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is You.com's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what You.com's own status page declared. Below it, any public chatter we saw about You.com and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what You.com's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about You.com in the last 24 hours, which is not evidence that nothing is wrong.
You.com's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is You.com's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention You.com next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East100.00%446
US-West100.00%340
Europe99.68%313
Asia-Pacific100.00%188

Their declared record

You.com's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Authentication OutageMinor incident
Oct 5, 2026, 1:59 PM UTC to Oct 5, 2026, 1:59 PM UTC (0 min)resolved
their latest update (Oct 5, 2026, 1:59 PM UTC): We have identified and resolved the issue. Impacted: APIs - Agentic Search
Issue resolvedMinor incident
Jul 8, 2026, 8:19 PM UTC to Jul 8, 2026, 8:19 PM UTC (0 min)resolved
their latest update (Jul 8, 2026, 8:19 PM UTC): We have resolved the issue.
Search & Contents API OutageMinor incident
Jun 9, 2026, 4:44 PM UTC to Jun 9, 2026, 4:44 PM UTC (0 min)resolved
their latest update (Jun 9, 2026, 4:44 PM UTC): This incident has been resolved. Impacted: APIs - Search/Index
Increased Site ErrorsMinor incident
May 21, 2026, 4:03 PM UTC to May 21, 2026, 4:03 PM UTC (0 min)resolved
their latest update (May 21, 2026, 4:03 PM UTC): The system has returned to normal.
Issue identified and fix is deployedMinor incident
Mar 13, 2026, 8:51 PM UTC to Mar 13, 2026, 8:51 PM UTC (0 min)resolved
their latest update (Mar 13, 2026, 8:51 PM UTC): We are monitoring the deployed fix to ensure resolution.
Subscription IssuesMinor incident
Jan 13, 2026, 6:27 PM UTC to Jan 13, 2026, 6:27 PM UTC (0 min)resolved
their latest update (Jan 13, 2026, 6:27 PM UTC): Fix is deployed and system health seems healthy again. We will continue monitoring the relevant services. Impacted: Chat Product
Degradation in Backend Metrics ServiceMinor incident
Dec 12, 2025, 10:20 PM UTC to Dec 12, 2025, 10:20 PM UTC (0 min)resolved
their latest update (Dec 12, 2025, 10:20 PM UTC): This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. Impacted: Chat Product
Degradation of Backend ServicesMinor incident
Oct 16, 2025, 4:34 PM UTC to Oct 16, 2025, 4:34 PM UTC (0 min)resolved
their latest update (Oct 16, 2025, 4:34 PM UTC): Customers experienced an inconsistency in their user subscription. Impacted: Chat Product
Investigating issues with platformMinor incident
Aug 30, 2025, 3:05 AM UTC to Aug 30, 2025, 3:05 AM UTC (0 min)resolved
their latest update (Aug 30, 2025, 3:05 AM UTC): Fix resolved the observed issues.
Intermittent infrastructure issuesMinor incident
Aug 28, 2025, 1:01 AM UTC to Aug 28, 2025, 1:01 AM UTC (0 min)resolved
their latest update (Aug 28, 2025, 1:01 AM UTC): There were intermittent infrastructure issues affecting accounts state and user authentications due to an infrastructure update. The issue was identified and the network configuration was rolled back.

Showing the 10 most recent of 11 incidents You.com has declared in the history we hold.

These entries are You.com's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

You.com's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.