مشکل در netWork کمپانی leasweb
سلام
دوستان من یک سرور از کمپانی نت دایرکت یا همان لیزوب دارم !
که صبح با Delay مواجعه شدم !
دلیل چی هست ؟
آیا شما نیز همچین مشکلی را دارید ؟
نمونه زیر از سرور گرفته شده است .
کد:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 178.162.245.127: bytes=32 time=359ms TTL=48
Request timed out.
Request timed out.
Request timed out.
Reply from 178.162.245.127: bytes=32 time=332ms TTL=48
Request timed out.
Request timed out.
Reply from 178.162.245.127: bytes=32 time=401ms TTL=48
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 178.162.245.127: bytes=32 time=329ms TTL=48
Request timed out.
Request timed out.
پاسخ : مشکل در netWork کمپانی leasweb
بله
کد:
I would like to inform you that your email is received in good order.
We have some network issues at the moment.
همچنان مشکل وجود داره
پاسخ : مشکل در netWork کمپانی leasweb
شما متوجه نشدید تا کی مشکل پایدار هستش ؟؟
تازگی ها خیلی این مشکل بوجود اماده !
پاسخ : مشکل در netWork کمپانی leasweb
اصولا لیزوب آلمان ( نت دایرکت خدا بیامرز ) دیتاسنتر کاملا استانداردی نبود
ولی از وقتی لیزوب این دیتاسنتر رو خریداری کرد تغییرات اساسی دادند
احتمالا الان هم شاهد یکی از همین تغییرات هستید
پاسخ : مشکل در netWork کمپانی leasweb
کد:
Reply from 95.168.161.168: bytes=32 time=373ms TTL=48
Reply from 95.168.161.168: bytes=32 time=336ms TTL=48
Reply from 95.168.161.168: bytes=32 time=331ms TTL=48
Reply from 95.168.161.168: bytes=32 time=344ms TTL=48
Reply from 95.168.161.168: bytes=32 time=338ms TTL=48
Reply from 95.168.161.168: bytes=32 time=345ms TTL=48
Reply from 95.168.161.168: bytes=32 time=368ms TTL=48
Reply from 95.168.161.168: bytes=32 time=325ms TTL=48
Reply from 95.168.161.168: bytes=32 time=344ms TTL=48
Reply from 95.168.161.168: bytes=32 time=328ms TTL=48
Reply from 95.168.161.168: bytes=32 time=337ms TTL=48
Reply from 95.168.161.168: bytes=32 time=342ms TTL=48
Reply from 95.168.161.168: bytes=32 time=341ms TTL=48
Reply from 95.168.161.168: bytes=32 time=320ms TTL=48
Reply from 95.168.161.168: bytes=32 time=339ms TTL=48
Reply from 95.168.161.168: bytes=32 time=328ms TTL=48
Reply from 95.168.161.168: bytes=32 time=331ms TTL=48
Ping statistics for 95.168.161.168:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
من که مشکلی ندارم :-?
پاسخ : مشکل در netWork کمپانی leasweb
نقل قول:
نوشته اصلی توسط
rn4j1m1
کد:
Reply from 95.168.161.168: bytes=32 time=373ms TTL=48
Reply from 95.168.161.168: bytes=32 time=336ms TTL=48
Reply from 95.168.161.168: bytes=32 time=331ms TTL=48
Reply from 95.168.161.168: bytes=32 time=344ms TTL=48
Reply from 95.168.161.168: bytes=32 time=338ms TTL=48
Reply from 95.168.161.168: bytes=32 time=345ms TTL=48
Reply from 95.168.161.168: bytes=32 time=368ms TTL=48
Reply from 95.168.161.168: bytes=32 time=325ms TTL=48
Reply from 95.168.161.168: bytes=32 time=344ms TTL=48
Reply from 95.168.161.168: bytes=32 time=328ms TTL=48
Reply from 95.168.161.168: bytes=32 time=337ms TTL=48
Reply from 95.168.161.168: bytes=32 time=342ms TTL=48
Reply from 95.168.161.168: bytes=32 time=341ms TTL=48
Reply from 95.168.161.168: bytes=32 time=320ms TTL=48
Reply from 95.168.161.168: bytes=32 time=339ms TTL=48
Reply from 95.168.161.168: bytes=32 time=328ms TTL=48
Reply from 95.168.161.168: bytes=32 time=331ms TTL=48
Ping statistics for 95.168.161.168:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
من که مشکلی ندارم :-?
کد:
http://leasewebnoc.com/status.php?i=685
پاسخ : مشکل در netWork کمپانی leasweb
نقل قول:
نوشته اصلی توسط
tukanet
اصولا لیزوب آلمان ( نت دایرکت خدا بیامرز ) دیتاسنتر کاملا استانداردی نبود
ولی از وقتی لیزوب این دیتاسنتر رو خریداری کرد تغییرات اساسی دادند
احتمالا الان هم شاهد یکی از همین تغییرات هستید
نقل قول:
نوشته اصلی توسط
rn4j1m1
کد:
Reply from 95.168.161.168: bytes=32 time=373ms TTL=48
Reply from 95.168.161.168: bytes=32 time=336ms TTL=48
Reply from 95.168.161.168: bytes=32 time=331ms TTL=48
Reply from 95.168.161.168: bytes=32 time=344ms TTL=48
Reply from 95.168.161.168: bytes=32 time=338ms TTL=48
Reply from 95.168.161.168: bytes=32 time=345ms TTL=48
Reply from 95.168.161.168: bytes=32 time=368ms TTL=48
Reply from 95.168.161.168: bytes=32 time=325ms TTL=48
Reply from 95.168.161.168: bytes=32 time=344ms TTL=48
Reply from 95.168.161.168: bytes=32 time=328ms TTL=48
Reply from 95.168.161.168: bytes=32 time=337ms TTL=48
Reply from 95.168.161.168: bytes=32 time=342ms TTL=48
Reply from 95.168.161.168: bytes=32 time=341ms TTL=48
Reply from 95.168.161.168: bytes=32 time=320ms TTL=48
Reply from 95.168.161.168: bytes=32 time=339ms TTL=48
Reply from 95.168.161.168: bytes=32 time=328ms TTL=48
Reply from 95.168.161.168: bytes=32 time=331ms TTL=48
Ping statistics for 95.168.161.168:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
من که مشکلی ندارم :-?
[Germany] Network issues [Update]
Thu 13 Oct 2011 13:44
Expected Downtime: Unknown
Location: Wupertal Germany
Reason: Hardware failure
*******************************
Dear customer,
At the moment we experience some troubles in the German part of our network, datacenter Wupertal. The cause of this is that a link between the XMR and the core went down.
We are currently in contact with the provider to have an engineer onsite to resolve the issue as soon as possible.
Please be patient while we are working on this problem.
Regards,
LeaseWeb BV
UPDATE @ 17:40
We located the faulty segment on the circuit. The engineer is now on the way to the site to measure and repair the segment.
UPDATE @ 18:50
The engineer is stuck in the traffic so it is taking a bit longer then expected. We can expect him to arrive within 1 hour
UPDATE @ 19:30
The engineer has arrived. Now locating the fault and repair
UPDATE @ 20:30
Broken Fiber Strand found, checking fastest possible solution for fix
UPDATE @ 20:50
Splicing Team is on there way to remove broken part and splice in a new part
UPDATE @ 21:55
Fiber Strand is not reparable, new cable is beeing pulled
UPDATE @ 23:40
around 200 Meters cable pulled, pigtail splicing begins shortly
UPDATE @ 02:15
Everything is back online
=====
پاسخ : مشکل در netWork کمپانی leasweb
واسه ما هم پینگ می ده ، سی پنل هم با سرعت کم باز می شه ولی سایت ها اصلا باز نمی شن .
پاسخ : مشکل در netWork کمپانی leasweb
کد:
Pinging 95.168.161.168 with 32 bytes of data:
Reply from 95.168.161.168: bytes=32 time=174ms TTL=51
Reply from 95.168.161.168: bytes=32 time=170ms TTL=51
Reply from 95.168.161.168: bytes=32 time=172ms TTL=51
Reply from 95.168.161.168: bytes=32 time=170ms TTL=51
Reply from 95.168.161.168: bytes=32 time=170ms TTL=51
Reply from 95.168.161.168: bytes=32 time=170ms TTL=51
Reply from 95.168.161.168: bytes=32 time=174ms TTL=51
Reply from 95.168.161.168: bytes=32 time=174ms TTL=51
پاسخ : مشکل در netWork کمپانی leasweb
UPDATE @ 02:15
Everything is back online
پاسخ : مشکل در netWork کمپانی leasweb
کد:
Pinging 95.168.161.168 with 32 bytes of data:
Reply from 95.168.161.168: bytes=32 time=298ms TTL=46
Reply from 95.168.161.168: bytes=32 time=297ms TTL=46
Reply from 95.168.161.168: bytes=32 time=299ms TTL=46
Reply from 95.168.161.168: bytes=32 time=299ms TTL=46
Reply from 95.168.161.168: bytes=32 time=298ms TTL=46
Reply from 95.168.161.168: bytes=32 time=300ms TTL=46
Reply from 95.168.161.168: bytes=32 time=298ms TTL=46
Reply from 95.168.161.168: bytes=32 time=299ms TTL=46
Reply from 95.168.161.168: bytes=32 time=298ms TTL=46
Reply from 95.168.161.168: bytes=32 time=299ms TTL=46
Ping statistics for 95.168.161.168:
Packets: Sent = 10, Received = 10, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 297ms, Maximum = 300ms, Average = 298ms
