LinkedIn Not Working? Status Checks and Sign-In Fixes
When LinkedIn will not load or keeps sending you back to the sign-in page, the cause is usually on your side: stale browser data, a wrong clock, or an out-of-date DNS record. Start by signing out and back in, clearing your cache and cookies, and trying another browser. If the site freezes or shows a maintenance message, flushing the DNS cache on your computer is the next step.
LinkedIn’s help pages reviewed for this guide do not name a status page, so the quickest outage test is to try the site on another device or network. If it works there, the problem is with your computer, browser or connection.
How do you tell if LinkedIn is down or only broken for you?
Open LinkedIn on a second device, ideally on mobile data instead of your home Wi-Fi. If it loads there, the fault is local and the fixes below apply. If it fails everywhere, LinkedIn’s help pages describe no outage workaround, so wait and try again later.
The same check works for other services. Our guides to Zoom connection failures and Microsoft Copilot problems follow the same logic of checking the right status page before changing settings.
Why does LinkedIn.com freeze, load slowly or show a maintenance message?
According to LinkedIn Help, site freezing, a constant “Site Maintenance” message, slow loading, or an IP address showing in the address bar instead of www.linkedin.com can all point to an outdated DNS cache. DNS (Domain Name System) is the lookup that turns a website name into a numeric address, and your computer stores recent answers. When linkedin.com’s address changes, a stale stored answer can send you to the wrong place.
LinkedIn says you may also need to ask your internet service provider to confirm that its main DNS servers have the current linkedin.com address. On a work network, talk to your IT department before changing anything, because their DNS servers may need the update too.
How do you flush the DNS cache?
LinkedIn lists steps for Windows and Mac. On Windows, the page gives two routes:
- Click the Start logo at the bottom left, choose Run, type “cmd”, then type “ipconfig /flushdns” in the command window and press Enter.
- Alternatively, open the Start menu, choose All Programs, then Accessories, right-click Command Prompt and pick Run as Administrator. Type “ipconfig /flushdns” and press Enter. Your IT group may have locked down the administrator option.
On a Mac, open Finder, go to Applications and then Utilities, and run the Terminal application. The page lists two commands for different Mac versions: “lookupd -flushcache” and “dscacheutil -flushcache”. Type the one that works on your system and press Enter.
After any of these, a success message means you should close every browser window and open LinkedIn again. A failure message means you should contact your internet service provider and say you cannot reach a commonly used site.
If flushing does nothing, LinkedIn says you can point your computer at a different DNS service, such as Google Public DNS or OpenDNS Basic (free with signup). The company recommends this only for advanced users who fully control their network, and suggests reading all configuration instructions first.
What fixes a LinkedIn feature that errors out or misbehaves?
The Troubleshoot common LinkedIn issues page suggests testing the feature after each step, so you can see which one helped:
- Click the Me icon at the top of your LinkedIn homepage, choose Sign Out, and sign in again.
- Sign in from your browser’s Incognito mode.
- Clear the cache and cookies in your current browser.
- Try a different browser, such as Firefox or Safari if you were using Chrome. LinkedIn recommends the latest versions, meaning the current and previous major releases.
If none of that works, contact LinkedIn with a description of the problem and the steps that reproduce it, the browsers and versions you tried, and a screenshot.
Why does LinkedIn keep asking you to sign in?
The Repeatedly asked to sign in page points first to the date and time setting on your computer. Correcting it often resolves the loop. It also suggests clearing your browser’s cache and cookies.
On a company or school network, firewalls or security blocks may stop parts of the site from working, so LinkedIn suggests asking your corporate administrator or helpdesk. If you are still stuck, contact LinkedIn.
What if you cannot sign in to the LinkedIn Recruiter app or mobile site?
These steps come from the Recruiter sign-in help page and apply to LinkedIn Recruiter users:
- Make sure your device is online.
- Enter the same email address you use on the desktop version of www.linkedin.com.
- Tap Show in the password box to check what you typed, on the app or on mobile web.
- Tap Forgot your password? at the bottom of the sign-in page, or use the Password Reset feature.
- If you use Safari on an iPhone, open Settings, tap Safari, and turn off Block All Cookies. Under Advanced, switch JavaScript on.
- Turn off private browsing: in Safari, tap the Tabs icon at the lower right, tap Private, then Start Page and Done. A dark address bar with the word Private means it is on.
If the Recruiter app still refuses to sign you in, uninstall and reinstall it. LinkedIn also says it supports only iOS 13.0 and Android Marshmallow (6.0 / API level 23) and newer, and asks Recruiter app users to upgrade to those versions.
Streaming and meeting apps have their own sign-in fixes. See our guide to Google Meet joining and audio problems for a comparable set of checks.
Quick answers
Does clearing cookies sign me out of LinkedIn?
Clearing cookies removes stored site data from your browser, so expect to sign in again afterward. LinkedIn lists it as a fix for both general errors and repeated sign-in prompts.
Is flushing the DNS cache safe?
LinkedIn presents it as a standard first step for freezing, slow loading or maintenance messages. Changing to a different DNS service is a bigger step that the company recommends only for advanced users.
Who should I contact if the fixes fail?
Contact LinkedIn with the steps to reproduce the problem, your browsers and versions, and a screenshot. On a work network, start with your IT department or helpdesk.
Checked against official sources in November 2026. Apps, menus and error codes change: check the official help page for the current steps.