MTNL Mumbai Issues with facebook

[Mr.cool]

Hello friends,
from last few weeks am facing some issues loading facebook.
Facebook.com is loading is extremely slow.
Not facing this issue with any other website like google ,youtube,gmail etc.
I really dont know whats the issue.
Any help would be highly appreciated.

 

[x720]

DNS?

 

[amish]

Working fine here.

 

[GameTanx]

Try this and see if it works.
Log in to your router webpage 192.168.1.1
Look for a setting called MTU somewhere in those pages.
If it's set at 1500, change it to 1492.
Save settings and reboot the router.

 

[Mr.cool]

DNS?

so i just changed my dns from google dns to open yesterday night and yes facebook was loading fine i though finally issue solved but again same thing started to happen in morning :/

 

[Mr.cool]

Working fine here.

whats ur starting IP address ?
Mine is 59.182.xxx

 

[Mr.cool]

Try this and see if it works.
Log in to your router webpage 192.168.1.1
Look for a setting called MTU somewhere in those pages.
If it's set at 1500, change it to 1492.
Save settings and reboot the router.

i just tried this and seems it is working fine as of now .
i will check for some more time and let you know if it resolved the issue or not

 

[Mr.cool]

still facing some issues.
the only thing is that its happening to specific time now,
Normally after 11 pm facebook works perfectly but in morning the same issue occurs. :/
i did some test with command prompt for facebook and for google.
while doing ping test for facebook it shows some packet lost but it doesnt happen with google.

 

[Mr.cool]

Still facing issues plus speed issues now.
complained to mtnl and connection worked fine for a day and now again same issue.
just getting 1 mbps speed on 2 mbps line :/.
some times i get packet loss upto 50 %

 

[panzer008]

Its a problem with your port...... I was on the same port till a month ago..... 59.182.x.x..... facebook use to give a lot of problems...... but through VPN it use to be ok..... even updating Play Store apps use to be a pain during day time..... after 7PM everything use to normalize....seems like 59.182.x.x has loads of traffic during day time....

On new port 182.59.x.x..... no such problems.....

ping facebook.com -t

Pinging facebook.com [173.252.120.6] with 32 bytes of data:
Reply from 173.252.120.6: bytes=32 time=333ms TTL=74
Reply from 173.252.120.6: bytes=32 time=334ms TTL=74
Reply from 173.252.120.6: bytes=32 time=335ms TTL=74
Reply from 173.252.120.6: bytes=32 time=336ms TTL=74
Reply from 173.252.120.6: bytes=32 time=341ms TTL=74
Reply from 173.252.120.6: bytes=32 time=335ms TTL=74
Reply from 173.252.120.6: bytes=32 time=334ms TTL=74
Reply from 173.252.120.6: bytes=32 time=343ms TTL=74
Reply from 173.252.120.6: bytes=32 time=332ms TTL=74
Reply from 173.252.120.6: bytes=32 time=342ms TTL=74
Reply from 173.252.120.6: bytes=32 time=343ms TTL=74
Reply from 173.252.120.6: bytes=32 time=343ms TTL=74
Reply from 173.252.120.6: bytes=32 time=334ms TTL=74
Reply from 173.252.120.6: bytes=32 time=335ms TTL=74
Reply from 173.252.120.6: bytes=32 time=335ms TTL=74
Reply from 173.252.120.6: bytes=32 time=341ms TTL=74
Reply from 173.252.120.6: bytes=32 time=334ms TTL=74
Reply from 173.252.120.6: bytes=32 time=333ms TTL=74
Reply from 173.252.120.6: bytes=32 time=332ms TTL=74
Reply from 173.252.120.6: bytes=32 time=342ms TTL=74
Reply from 173.252.120.6: bytes=32 time=343ms TTL=74
Reply from 173.252.120.6: bytes=32 time=342ms TTL=74

Ping statistics for 173.252.120.6:
    Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 332ms, Maximum = 343ms, Average = 337ms