56

Stack Overflow will be experimenting with some new HTTP traffic management technologies. Users should not see any negative effects. That said, we felt it would be prudent to announce that the test times will be:

The tests will affect all of our public websites and we will be closely monitoring traffic during these times.

The tooling has passed our initial testing which we could perform passively. These tests will be more active.

10
  • 7
    Can you tell what tools you're switching to? Do note that there is already a list, though likely not very up-to-date, but still, you did share those things in the past. :) Jun 16 at 7:03
  • 13
    @ShadowWizardSaysNoMoreWar we're in the evaluation phase so don't want to name any vendors at this stage.
    – Josh Zhang StaffMod
    Jun 16 at 12:56
  • 3
    I've noticed several outages since this test started, normally lasting just a few minutes. Other sites load fine during this time.
    – mousetail
    Jun 20 at 14:25
  • 3
    Will this have any impact on users of Tor, or is the treatment of proxies and anonymity services not being changed? Jun 21 at 2:04
  • 9
    We've had a series of DDoS attacks that were mitigated within 30 seconds, thus no incident on stackstatus but none of them were during the first hour long testing period. Also there will be no change in traffic policies for Tor or other proxies.
    – Josh Zhang StaffMod
    Jun 21 at 13:06
  • 1
    i don't think your tool works :) seems like your network gives me 503 errors from my area (on my public IP, and my IP block), from my area VPN provider's IP. Canada and netherland do work. Please see my previous comment. Monitor should tell you about errors? Why is stackstatus.net not reporting my issues?
    – HelpNeeder
    Jun 25 at 7:01
  • 2
    @forest distrusts StackExchange Stackexchange has problems when using proxies, is this what you tallking about?
    – convert
    Jun 25 at 11:10
  • 2
    @HelpNeeder the tool we're testing doesn't throw 5xx errors, generally it'll be 4xx such as 407 or 429.
    – Josh Zhang StaffMod
    Jun 25 at 13:15
  • 4
    @HelpNeeder we have identified the issue, and updated StackStatus. Because the error is at the CDN level, we never saw it in our internal logs. We will be making updates to make this type of CDN error more visible to us in the future.
    – Josh Zhang StaffMod
    Jun 27 at 20:45

1 Answer 1

22

Thank you for the (early) heads-up. I have two questions though:

  • What is the goal you're trying to achieve by implementing this tool?
  • Can the maintenance entrance on StackStatus include a hyperlink, rather than a plain text URL?
6
  • 10
    Feature request already in place to allow hyperlinks for the status page! As far as the goal, we're evaluating 3rd party software and can't get into too much details unfortunately. There could be a post in the future if things go well.
    – Josh Zhang StaffMod
    Jun 15 at 18:04
  • 17
    I don't know anything about the tool (read: this is a guess, mods around the network haven't been told why, as far as I know), but considering the timing, I'm highly inclined to believe it's DDoS management-related. Feels like that's where HTTP management, whatever that really implies, is critical as well Jun 16 at 13:07
  • 2
    @ZoestandswithUkraine Yes it is probably a web application firewall service of some kind.
    – TylerH
    Jun 16 at 13:39
  • 1
    What maintenance entrance on StackStatus? I see nothing there, only the "Test New Status Page And Communication Tools". No hint for any other activity. (Also nothing in the "history" page). Jun 19 at 7:40
  • 1
    @ShadowWizardSaysNoMoreWar it appears it has been retracted.
    – Luuklag
    Jun 19 at 7:49
  • 6
    Oh. Well at its current state, this new stackstatus site is useless. I do hope they will improve it. Jun 19 at 7:50

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .