Is Indeed Down?
When we last reached Indeed directly, it answered and refused us — origin returns HTTP 403 bot challenge from all regions. An answer is proof the origin was serving traffic, but it measures our access, not the service, so we publish no percentage.
Last checked · checks run every 30 minutes
Why there is no uptime figure on this page
The last time we fetched Indeed's page directly, the origin answered and turned our client away rather than serving the page. That answer tells us the origin was reachable and responding, but it is a response about our automation, not about whether Indeed works for you.
A percentage built from those checks would measure our own access, so we do not publish one. What this page does show is each region's most recent result, which you can weigh yourself.
30-day history
Reachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
A static asset loaded in 59ms. That proves the edge is up, but not that the site works.
A static asset loaded in 85ms. That proves the edge is up, but not that the site works.
A static asset loaded in 302ms. That proves the edge is up, but not that the site works.
A static asset loaded in 52ms. That proves the edge is up, but not that the site works.
A static asset loaded in 41ms. That proves the edge is up, but not that the site works.
A static asset loaded in 93ms. That proves the edge is up, but not that the site works.
A static asset loaded in 56ms. That proves the edge is up, but not that the site works.
A static asset loaded in 189ms. That proves the edge is up, but not that the site works.
A static asset loaded in 33ms. That proves the edge is up, but not that the site works.
A static asset loaded in 200ms. That proves the edge is up, but not that the site works.
A static asset loaded in 84ms. That proves the edge is up, but not that the site works.
A static asset loaded in 44ms. That proves the edge is up, but not that the site works.
A static asset loaded in 275ms. That proves the edge is up, but not that the site works.
A static asset loaded in 44ms. That proves the edge is up, but not that the site works.
A static asset loaded in 196ms. That proves the edge is up, but not that the site works.
A static asset loaded in 99ms. That proves the edge is up, but not that the site works.
A static asset loaded in 30ms. That proves the edge is up, but not that the site works.
A static asset loaded in 91ms. That proves the edge is up, but not that the site works.
What Indeed does
Indeed is the world's largest job search engine, aggregating listings from thousands of company career pages, job boards, and staffing agencies. It serves both job seekers who search and apply for positions, and employers who post job listings and manage candidates. Indeed processes millions of job applications daily across over 60 countries.
What an outage looks like
When Indeed is down, job seekers cannot search for or apply to positions. Application submissions may fail, losing cover letters and responses. Employers cannot access their candidate dashboard or post new listings. Saved job searches and email alerts may not be delivered on schedule.
What to do about it
Wait and retry after a few minutes, as Indeed outages are typically brief. If you were in the middle of a job application, check your email for a confirmation to see if it went through. For urgent applications, try visiting the employer's website directly and apply through their careers page.
Is it down for everyone, or just you?
If this page says Indeed is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.
Related services
Indeed outage FAQ
Will my job application be lost if Indeed goes down?
Can I still find jobs if Indeed is down?
Does Indeed going down affect employer accounts?
Are Indeed job alerts affected by outages?
How we measure this
- We request Indeed's public endpoint every 30 minutes from Fly.io regions across six continents — 18 of them answered the most recent check.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Indeed publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it — and when Indeed blocks our checks entirely, we report the vendor's own status directly.
Get alerted when Indeed goes down
This page refreshes every 30 minutes. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.
Start Free Monitoring