Quote from: Gws24 on January 20, 2015, 10:55:29 PM

Quote from: wlefever on January 20, 2015, 08:15:00 PM

Quote from: PhilippeStevens on January 20, 2015, 07:15:34 PM

Site down here. Any answer from OVH ?

I haven't seen any response from OVH yet. la revedere ltcgear.

Edit: http://status.ovh.net/?do=details&id=8532

that problem started the 16th....

EDIT: The incident ip range 167.114.102.0/24 is very close to the ltcgear.com ip address 167.114.102.178 but I'm not very versed in ip ranges etc so I don't know how close physically this would be.

167.114.102.178 resides in the same subnet as that /24 (167.114.102.0/24) meaning that whole block of 255 address is owned by that hosting company. So Chris's IP 167.114.102.178/32 is broken into a single /32 routed pubic IP used statically for his server. Just means that the hosting company owns this block, so that whole /24 block is currently affected any IP in that block wont be routed. Best to contact that hosting company for further info.