Google Search Console is almost never down globally. When you can't access it, the problem is typically on your end: cached login tokens, browser extensions blocking scripts, or you're logged into the wrong Google account that lacks property access. Hard-refresh the page (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) and verify you're using the account that owns or has been granted access to the property. Google publishes real-time status at status.search.google.com/summary. If Search Console shows a red or yellow icon there, you're seeing a genuine outage—these happen maybe once or twice a year and usually resolve in under two hours. Regional issues are rarer but can occur if Google's servers serving Canadian traffic have a routing problem; switching your VPN or waiting 20 minutes usually clears it. Common false-alarm scenarios we see at Ottawa SEO: - Property not verified: The site was verified under a different account or the DNS TXT record expired. Re-verify ownership. - API quota exceeded: If you're pulling data via the API (which we do for 500+ domains), you can hit rate limits. The web UI still works, but programmatic access pauses. - Delayed data: Search Console data lags 24–48 hours. If yesterday's clicks aren't showing, that's normal processing delay, not downtime. - Mobile app glitches: The iOS/Android apps are less stable than the web version. Use search.google.com/search-console on desktop when troubleshooting. If you confirm it's actually down, check Twitter/X for "Google Search Console down"—webmasters and agencies report outages within minutes. Meanwhile, pull any critical data from your own server logs or Google Analytics 4 so you're not blocked on performance decisions. We keep local CSV exports of Search Console queries and pages updated weekly precisely because the platform occasionally hiccups, and client reporting can't wait on Google's uptime.