For information required to report connectivity issues: https://wikitech.wikimedia.org/wiki/Reporting_a_connectivity_issue

In T267089#6599101, @Peachey88 wrote:

For information required to report connectivity issues: https://wikitech.wikimedia.org/wiki/Reporting_a_connectivity_issue

Thanks. What other information do you need? I'd think the information I've given may be sufficient. Check the logs/load for a traffic dip some minutes before I filed this task. If nothing is there, check for a traffic dip from the Netherlands some minutes before I filed this task. If again there is nothing, it's probably not worth investigating any further. If there was a traffic dip, you probably don't need any more information from me.

See the list on https://wikitech.wikimedia.org/wiki/Reporting_a_connectivity_issue : A traceroute for example, if this is still a problem.
You wrote "This might have been some routing issue, but could also just be my ISP." And that's one of the many factors why more info is needed.

In T267089#6599101, @Peachey88 wrote:

For information required to report connectivity issues: https://wikitech.wikimedia.org/wiki/Reporting_a_connectivity_issue

Thanks, but BTW -- when linking this page to trouble reporters, please always use the version on wikitech-static:
https://wikitech-static.wikimedia.org/wiki/Reporting_a_connectivity_issue

It doesn't matter in this case as the reporter had only a temporary issue, but, the wikitech-static link is hosted on different infrastructure, so it should be reachable for users and troubleshooters even when our sites are not.

In T267089#6600271, @CDanis wrote:

Thanks for the report @AlexisJazz.

There was a known issue that occurred at the esams edge site during the time window you describe. Whereas traffic to Beta Cluster goes direct to eqiad, which is why it still worked for you.

Thank you! Things like that also get described on https://wikitech.wikimedia.org/wiki/Incident_documentation, am I correct?