Re: Login de gvip

Eng° Marcelo Peres

18 anos atrás

Olá amigo, Dei uma analisada pelo host tracker e realmente parece estar fora do ar. Veja o resultado: http://gvip.geovision.com.tw/login/ Location Result Page Size Response time Kb/sec IP Partner Received responses: 22 Fail Average: - - Frankfurt, Germany Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 Crohoster Frankfurt, Germany Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 Crohoster Amsterdam, NL Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.51 sec 61.59.37.171 Crohoster SPb, RU Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.52 sec 61.59.37.171 SpaceWeb Dallas, TX, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 Provisov.Net Houston, TX, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 Thinksmart Hosting Maidenhead, UK Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 82.42 sec 61.59.37.171 RuangWeb.com Dallas, TX, Us Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 Moonsoft Systems Nanterre, France Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 Alorys Fort Worth, TX, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 81.48 sec 61.59.37.171 New5Hosting Montreal, QC, Canada Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 PersianServices Light Server Canyon Country, CA, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 HostIran Networks Orlando, FL, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 Apto Hosting Fremont, CA, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 Gearworx Portland, OR, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 VMHosting San Jose, CA, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 McColo corp Portland, OR, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.51 sec 61.59.37.171 Ashworth Consulting Kiev, Ukraine Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.51 sec 61.59.37.171 ProstoHosting.NET Philadelphia, PA, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 Bluetreehost WanChai, Hong Kong Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.51 sec 61.59.37.171 Zolar Co Ltd Canyon Country, CA, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 HostIran Networks Montreal, QC, Canada Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.51 sec 61.59.37.171 HostIran Networks Orlando, FL, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 61.59.37.171 PIE Hosting Um abraço