Is github.com Down in France?

Use this free website status checker to run a real time status check for this website URL. Enter the domain or enter the URL, then compare results from multiple locations.

Use the Check button to check website availability and compare website status with site status before deeper troubleshooting.

A web site can fail only for some visitors when there is a local network issue, stale DNS cache, ISP routing problems, VPN interference, or country-specific edge failures.

That usually means partial website downtime rather than a full outage for everyone.

If our check reaches the site but you cannot, the problem is usually local to your browser, DNS cache, network, firewall, VPN, or ISP route.

Try another browser or device, switch networks, and run another status check. If needed, compare the result with country-based checks.

HTTP status codes help explain what happened between your browser and the web server. For example, 403 means blocked access, 404 means missing content, and 502 or 503 often point to upstream failures.

Read these codes together with response time trends for better website monitoring and faster diagnosis of technical issues.

Login issues often happen when the authentication system, session storage, captcha flow, or account backend is failing while the main site still loads normally.

That kind of partial outage can look like a working homepage with broken sign-in, endless redirects, or repeated password prompts.

github.com averaged 465 ms across the last 1 checks. The most recent origin response time was 465 ms.

A slow response time usually means the site is reachable but under load, experiencing network latency, or serving requests more slowly than usual.

Developer platforms often fail by feature, such as API requests, repository views, builds, package downloads, or dashboards.

Check whether the issue is limited to one endpoint, organization, token, or recent 403 or 429 responses.

A platform incident can affect API or backend services even while the main website still appears up.

Token validation, OAuth, and private resource access often break independently from the public site.

Test whether the same action works with a fresh login, another token, or a different account.

If public pages load but authenticated API calls fail, the auth backend may be degraded.

Build, CI, and package services are commonly isolated from the main UI and can fail on their own.

Check whether only one region, runner, package registry, or deployment target is affected.

If the dashboard loads but builds fail, the backend job or artifact systems may be the problem.

Yes. Developer services often protect APIs and package downloads with rate limits, abuse controls, or WAF rules.

Slow retries, review recent 403 or 429 responses, and test from another network or token if possible.

If only automated calls fail, the issue may be access control rather than downtime.