TechSpot

Facebook not working in Mexico (ISP is Cablemas)

By elpretentio
Aug 15, 2016
Post New Reply
  1. Facebook and instagram (owned by facebook) simply do not work over wifi here and I'm trying to narrow down wether it is the ISP or facebook throttling traffic coming from mexico. many ISPs down here simply kind of suck, and the speed is mediocre. nonetheless, I ran a ping command and tracert and with the tracert it seems that along the way it the connection times out several times.

    to be clear, the homepage will load, but when proceeding to a profile or any other internal link it fails to load. I've tried using proxys with the Hola VPN plugin through the US and UK but they fail to work consistently if at all.

    here are the ping and tracert logs:

    **********************
    Windows PowerShell transcript start
    Start time: 20160815172435
    Username: DESKTOP-06G7P19\RAW3
    RunAs User: DESKTOP-06G7P19\RAW3
    Machine: DESKTOP-06G7P19 (Microsoft Windows NT 10.0.10586.0)
    Host Application: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
    Process ID: 4680
    PSVersion: 5.0.10586.494
    PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0.10586.494
    BuildVersion: 10.0.10586.494
    CLRVersion: 4.0.30319.42000
    WSManStackVersion: 3.0
    PSRemotingProtocolVersion: 2.3
    SerializationVersion: 1.1.0.1
    **********************
    Transcript started, output file is C:\Users\RAW3\Downloads\powershell_log.txt
    PS C:\Users\RAW3> ping facebook.com

    Pinging facebook.com [69.171.230.68] with 32 bytes of data:
    Reply from 69.171.230.68: bytes=32 time=348ms TTL=69
    Reply from 69.171.230.68: bytes=32 time=278ms TTL=69
    Reply from 69.171.230.68: bytes=32 time=120ms TTL=69
    Reply from 69.171.230.68: bytes=32 time=120ms TTL=69

    Ping statistics for 69.171.230.68:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 120ms, Maximum = 348ms, Average = 216ms
    PS C:\Users\RAW3> tracert facebook.com

    Tracing route to facebook.com [69.171.230.68]
    over a maximum of 30 hops:

    1 1 ms 13 ms 2 ms 192.168.0.1
    2 22 ms 115 ms 13 ms 10.176.128.1
    3 54 ms 19 ms 18 ms 10.3.29.30
    4 72 ms 63 ms 17 ms 10.3.12.134
    5 153 ms 24 ms 35 ms 192.168.202.26
    6 72 ms 98 ms 25 ms 192.168.200.253
    7 24 ms 22 ms 14 ms 192.168.202.6
    8 17 ms 17 ms 12 ms 192.168.202.29
    9 41 ms 67 ms 48 ms bestelmex02-mred-dfo40-vex01-001.bestel.com.mx [200.57.2.194]
    10 * * * Request timed out.
    11 240 ms 187 ms 217 ms ae2.bb02.atl1.tfbnw.net [204.15.23.210]
    12 186 ms 211 ms 170 ms be12.bb01.ord1.tfbnw.net [31.13.27.27]
    13 235 ms 252 ms 229 ms ae8.bb03.prn2.tfbnw.net [31.13.29.187]
    14 118 ms 118 ms 123 ms ae3.dr10.prn1.tfbnw.net [31.13.27.123]
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 115 ms 119 ms 117 ms edge-star-mini-shv-17-prn1.facebook.com [69.171.230.68]

    Trace complete.
    PS C:\Users\RAW3> stop-transcript
    **********************
    Windows PowerShell transcript end
    End time: 20160815172656
    **********************

    seems there were some serious timeouts. thanks for any help. I'm looking to switch ISPs but want to get to the bottom of this beforehand.
     

    Attached Files:

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...