SNCF Connect help and reporting
Use the official help route for SNCF Connect; identify the specific product and action described on this page.
Live Domain Check
Run a live reachability check for sncf-connect.com. Compare the regional responses with the problem you see in SNCF Connect.
Find SNCF Connect help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
SNCF Connect combines journey search and booking with Mon Identifiant SNCF. Its help explains that account authentication and access to individual SNCF services can behave differently.
The checker above requests sncf-connect.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual SNCF Connect action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
For separate shopping & services services, compare these individual checks: La Poste status check, leboncoin status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse shopping and payment checks.
Use the official help route for SNCF Connect; identify the specific product and action described on this page.
Open the website in your browser and compare it with the result above. This link opens the service, not its status page.
We have not linked a separate status page for this service. Check the official help page for current notices.
Open SNCF Connect help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Route, travel date, failing step and error time; keep booking references, passenger details and ticket codes private.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to SNCF Connect.
These are troubleshooting comparisons, not claims that SNCF Connect is currently experiencing a particular incident.
Record whether the failure appears during route search, identification, payment or ticket retrieval. Preserve any existing ticket and purchase confirmation.
Compare the same journey date and train in the relevant booking view. A sold-out train or disruption to travel is different from a sign-in loop or an empty payment page.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use the comparison and support guidance above for the specific action. Keep the original check and error timestamps together; a cached result can be older than the problem you are seeing.
Repeat the same action in a second browser or on another available connection, keeping the item and account the same. Change one thing at a time so the result is comparable. Leave required workplace or school security controls in place.
Follow the website troubleshooting guide for connection checks. Preserve any unsent work before refreshing a form or changing a session.
Record whether the failure appears during route search, identification, payment or ticket retrieval. Preserve any existing ticket and purchase confirmation. Compare the same journey date and train in the relevant booking view. A sold-out train or disruption to travel is different from a sign-in loop or an empty payment page.
Use the community buttons on this page to share whether the service works for you. For help from SNCF Connect, use the official help/reporting resource linked above. Use the official help route for SNCF Connect; identify the specific product and action described on this page.
Record whether the failure appears during route search, identification, payment or ticket retrieval. Preserve any existing ticket and purchase confirmation. Compare the same journey date and train in the relevant booking view. A sold-out train or disruption to travel is different from a sign-in loop or an empty payment page.
Route, travel date, failing step and error time; keep booking references, passenger details and ticket codes private.