Dismiss Notice
Join Physics Forums Today!
The friendliest, high quality science and math community on the planet! Everyone who loves science is here!

Complaint Facing problems while reaching PF

  1. May 18, 2018 at 12:58 AM #1

    Wrichik Basu

    User Avatar
    Gold Member

    From today morning, I am facing problems in reaching PF.

    At first, it was saying that the site cannot be reached. It was not a problem of my internet connection, as other sites like google, youtube, yahoo and amazon were opening with the proper speed. This is what Opera browser was showing:

    View attachment 225876

    Finally, after an hour's try, I could finally reach the site, and went to the media gallery to upload videos. But the connection to the server was lost midway while uploading videos, and all the uploads were gone.

    It took me another half-an-hour trying to reach the Feedback section.

    I have used ping on CMD, and this is what it returned for PF and other sites:

    Code (Text):
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\soumitra>ping www.youtube.com

    Pinging youtube-ui.l.google.com [2404:6800:4007:809::200e] with 32 bytes of data:
    Reply from 2404:6800:4007:809::200e: time=327ms
    Reply from 2404:6800:4007:809::200e: time=81ms
    Reply from 2404:6800:4007:809::200e: time=151ms
    Reply from 2404:6800:4007:809::200e: time=140ms

    Ping statistics for 2404:6800:4007:809::200e:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 81ms, Maximum = 327ms, Average = 174ms

    C:\Users\soumitra>ping www.physicsforums.com

    Pinging www.physicsforums.com [] with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:\Users\soumitra>ping www.yahoo.com

    Pinging atsv2-fp.wg1.b.yahoo.com [2406:2000:ec:815::4] with 32 bytes of data:
    Reply from 2406:2000:ec:815::4: time=161ms
    Reply from 2406:2000:ec:815::4: time=266ms
    Reply from 2406:2000:ec:815::4: time=225ms
    Reply from 2406:2000:ec:815::4: time=218ms

    Ping statistics for 2406:2000:ec:815::4:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 161ms, Maximum = 266ms, Average = 217ms

    C:\Users\soumitra>ping www.amazon.com

    Pinging d3ag4hukkh62yn.cloudfront.net [] with 32 bytes of data:
    Reply from bytes=32 time=97ms TTL=242
    Reply from bytes=32 time=96ms TTL=242
    Reply from bytes=32 time=155ms TTL=242
    Reply from bytes=32 time=154ms TTL=242
    I am facing the problem from both desktop as well as mobile. In desktop, chrome, opera and firefox returned the same error.

    Requesting @Greg Bernhardt to look into the problem.

  2. jcsd
  3. May 18, 2018 at 1:27 AM #2
    What about tracert results?
  4. May 18, 2018 at 3:05 AM #3


    User Avatar
    2017 Award

    Staff: Mentor

    Wifi through the same internet connection or an independent internet connection?

    For me it works well.
    In general: To check if it is a local problem or not you can also use http://downforeveryoneorjustme.com/
  5. May 18, 2018 at 4:39 AM #4

    Wrichik Basu

    User Avatar
    Gold Member

    @mfb It's on two different mobiles with two different networks. Desktop is taking Internet from one through USB tethering. Both mobiles showing same problem. I don't know whether this will be posted properly, because the site is automatically loading a few times, and I'm trying to do it fast. Please edit if any problem occurs.
  6. May 18, 2018 at 9:57 AM #5

    Wrichik Basu

    User Avatar
    Gold Member

    Could finally get back and now everything is working properly.
  7. May 18, 2018 at 10:36 AM #6
    Could have been a country level router that was acting up. Glad you're back!
  8. May 18, 2018 at 5:15 PM #7


    User Avatar
    Science Advisor

    I had the same message here in California around 0100GMT 18May. I did a page refresh (F5 key) a couple times and the problem resolved.
Share this great discussion with others via Reddit, Google+, Twitter, or Facebook

Have something to add?
Draft saved Draft deleted