<div dir="ltr"><div>Hello folks,</div><div><br></div><div>Our infra also runs in the same network, so if you notice issues, they're most likely related to the same network issues.<br></div><div><br><div class="gmail_quote"><div dir="ltr">---------- Forwarded message ---------<br>From: <b class="gmail_sendername" dir="auto">Fabian Arrotin</b> <span dir="ltr"><<a href="mailto:arrfab@centos.org">arrfab@centos.org</a>></span><br>Date: Fri, Jul 20, 2018 at 12:49 PM<br>Subject: [Ci-users] [FYI] GitHub connectivity issue<br>To: <a href="mailto:ci-users@centos.org">ci-users@centos.org</a> <<a href="mailto:ci-users@centos.org">ci-users@centos.org</a>><br></div><br><br>Hi,<br>
<br>
Just to let all Projects using CI that our monitoring complained a lot<br>
about "flapping" connectivity to some external nodes, including <a href="http://github.com" rel="noreferrer" target="_blank">github.com</a>.<br>
After some investigations, it seems that there are some peering issues<br>
(or routing) at Level3, but errors come and go.<br>
<br>
We can't do anything but report internally and see if then error can be<br>
reported "upstream" at the link provider level.<br>
<br>
So this message is more about the fact that if your tests are having<br>
issues with some external connectivity, that can be related to that issue.<br>
<br>
-- <br>
Fabian Arrotin<br>
The CentOS Project | <a href="https://www.centos.org" rel="noreferrer" target="_blank">https://www.centos.org</a><br>
gpg key: 56BEC54E | twitter: @arrfab<br>
<br>
_______________________________________________<br>
Ci-users mailing list<br>
<a href="mailto:Ci-users@centos.org" target="_blank">Ci-users@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/ci-users" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/ci-users</a><br>
</div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">nigelb<br></div></div></div></div>