philo$ ping 184.108.40.206
PING 220.127.116.11 (18.104.22.168): 56 data bytes
36 bytes from et-13-0-0-0.pastr3.-.opentransit.net (22.214.171.124): Time to live exceeded
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 5400 8eb6 0 0000 01 01 24f6 192.168.1.112 126.96.36.199
Hi @petersconsult if it's isolated to your geographical region then it sounds like either an issue with your ISP, or perhaps a common carrier that several ISP's use. I did confirm that your website is up and I don't see any issues on the server at all.
If you want to run a traceroute to your server (or to our support portal) and post it here that'll help me identify where the routes and traffic is stopping. Not sure if it'll be something we can influence as it depends on where the traffic stops at.
@petersconsult No need to be sorry. Problems with websites and connectivity can be any number of various issues, and you don't really know which one until you start digging. Either way thou, now we can tell our staff if customers from France are having issues connecting this may be why!
@petersconsult an easy way to read a traceroute is to imagine that someone gave you a house address. Then they give you a list of 'turn by turn' directions. So in this example, to reach 188.8.131.52 your traffic must take each 'turn' listed in the traceroute. The problem is that point 5 doesn't exist. So think of it as a bridge that got closed for construction. Normally BGP and routing is smart enough to work around this, but not all carriers (ISPs) update their instructions as often as they should, or other times they may only have one way out (purchased routes) so if that route (bridge) is out then your traffic has no where to go.
Well.. Thank you for the help!
As usual, you all rule!
You should've hear the tech support person at Orange when i started explaining to them what a traceroute is, and how every internet connection goes through a series of 'hops'..