Site buggy for anyone else?

Discussion in 'Off Topic' started by Crash, Jan 17, 2011.

  1. Crash

    aa Crash func_nerd

    Messages:
    3,191
    Positive Ratings:
    5,017
    TF2maps has been acting pretty strange for me for that past week or so. It has about a 50/50 shot of actually loading the main page, and another 50/50 shot at the forums. Sometimes they both work but are just slow to load. I thought it was a problem with Google Chrome at first, as it seemed to work fine in Firefox, but then it started doing it there as well.

    Just wondering if anyone else has had this experience with the site lately, or if it's something on my end? I don't have a problem with any other site I go to, so I assume somethings up?

    Sorry if this is the wrong forum for this question.
     
  2. Zhan

    Zhan L5: Dapper Member

    Messages:
    208
    Positive Ratings:
    123
    I recently also having the same problems, and it's definitely some sort of DNS issue. You could try flushing your DNS cache, or if that doesn't work, use a different DNS server (like Google's Public DNS).
     
    • Thanks Thanks x 1
  3. heyyou

    heyyou L4: Comfortable Member

    Messages:
    151
    Positive Ratings:
    100
    I use Firefox and I've had the same issue. I usually have to reload the page 3-4 times to get to the home page sometimes, similar but not as bad for other pages on site. This is a recent issue for me.
     
  4. Crash

    aa Crash func_nerd

    Messages:
    3,191
    Positive Ratings:
    5,017
    That seemed to do the trick so far, let's see if it sticks.

    (Changing the DNS server, that is)
     
  5. PL-7764

    PL-7764 L6: Sharp Member

    Messages:
    376
    Positive Ratings:
    84
    I asked about this before, and got the same suggestions, which I followed, with no success from any of them. :\ I was on a totally different network for all of this weekend with a brand-new computer and got the same bugginess, which when combined with the number of other people now suddenly having the same problem makes me question whether it really is a client-side issue.