Github443 端口规律性超时，想请大家试试自己所在地区是否有同样的情况。

sillydaddy

2021-03-10 11:31:11 +08:00

分别用公司的网络(北京移动)，还有自己的 4G(北京移动，北京联通)热点测了一下。
测试方法：tcping -t github.com 443，浏览器并没有打开 github.com ，只是单纯的 tcping...

规律如下：

公司网络(北京移动) ，4G 热点(北京移动)：
跟楼主一样，每次超时，时间是非常准确的 3 分钟。比北京的“大姨妈式进京证”还要准确。
超时后，会出现短暂的 ping 通，时间不等，最短只 ping 通一次，最长几十秒。

4G 热点(北京联通)：
非常有规律的超时，且每次超时只维持 1，2 次 No response，其余时间都是 ping 通。每段 ping 通的时长，大概是 10s 或者 5s 。没有过多测试。这部分的具体数据如下：

```
C:\Users\**>tcping -t github.com 443

** Pinging continuously. Press control-c to stop **

Probing 52.74.223.119:443/tcp - Port is open - time=1206.298ms
Probing 52.74.223.119:443/tcp - Port is open - time=139.423ms
Probing 52.74.223.119:443/tcp - No response - time=2001.500ms
Probing 52.74.223.119:443/tcp - No response - time=2001.029ms
Probing 52.74.223.119:443/tcp - Port is open - time=545.484ms
Probing 52.74.223.119:443/tcp - Port is open - time=153.312ms
Probing 52.74.223.119:443/tcp - Port is open - time=153.441ms
Probing 52.74.223.119:443/tcp - Port is open - time=137.531ms
Probing 52.74.223.119:443/tcp - Port is open - time=141.392ms
Probing 52.74.223.119:443/tcp - Port is open - time=154.307ms
Probing 52.74.223.119:443/tcp - Port is open - time=157.207ms
Probing 52.74.223.119:443/tcp - Port is open - time=1150.087ms
Probing 52.74.223.119:443/tcp - Port is open - time=167.929ms
Probing 52.74.223.119:443/tcp - Port is open - time=143.909ms
Probing 52.74.223.119:443/tcp - Port is open - time=293.581ms
Probing 52.74.223.119:443/tcp - Port is open - time=1175.954ms
Probing 52.74.223.119:443/tcp - Port is open - time=152.318ms
Probing 52.74.223.119:443/tcp - Port is open - time=143.159ms
Probing 52.74.223.119:443/tcp - Port is open - time=149.835ms
Probing 52.74.223.119:443/tcp - Port is open - time=272.407ms
Probing 52.74.223.119:443/tcp - Port is open - time=141.300ms
Probing 52.74.223.119:443/tcp - Port is open - time=1174.043ms
Probing 52.74.223.119:443/tcp - Port is open - time=157.583ms
Probing 52.74.223.119:443/tcp - Port is open - time=160.159ms
Probing 52.74.223.119:443/tcp - Port is open - time=1171.108ms
Probing 52.74.223.119:443/tcp - Port is open - time=140.294ms
Probing 52.74.223.119:443/tcp - Port is open - time=1146.048ms
Probing 52.74.223.119:443/tcp - Port is open - time=156.782ms
Probing 52.74.223.119:443/tcp - Port is open - time=145.642ms
Probing 52.74.223.119:443/tcp - Port is open - time=134.585ms
Probing 52.74.223.119:443/tcp - No response - time=2001.431ms
Probing 52.74.223.119:443/tcp - Port is open - time=1158.397ms
Probing 52.74.223.119:443/tcp - Port is open - time=147.623ms
Probing 52.74.223.119:443/tcp - Port is open - time=146.323ms
Probing 52.74.223.119:443/tcp - Port is open - time=280.270ms
Probing 52.74.223.119:443/tcp - Port is open - time=1182.085ms
Probing 52.74.223.119:443/tcp - Port is open - time=176.244ms
Probing 52.74.223.119:443/tcp - Port is open - time=156.240ms
Probing 52.74.223.119:443/tcp - Port is open - time=165.209ms
Probing 52.74.223.119:443/tcp - Port is open - time=145.192ms
Probing 52.74.223.119:443/tcp - Port is open - time=1173.106ms
Probing 52.74.223.119:443/tcp - Port is open - time=153.359ms
Probing 52.74.223.119:443/tcp - Port is open - time=139.380ms
Probing 52.74.223.119:443/tcp - Port is open - time=152.978ms
Probing 52.74.223.119:443/tcp - Port is open - time=170.191ms
Probing 52.74.223.119:443/tcp - Port is open - time=176.179ms
Probing 52.74.223.119:443/tcp - Port is open - time=176.526ms
Probing 52.74.223.119:443/tcp - Port is open - time=155.801ms
Probing 52.74.223.119:443/tcp - Port is open - time=153.890ms
Probing 52.74.223.119:443/tcp - Port is open - time=153.561ms
Probing 52.74.223.119:443/tcp - Port is open - time=140.476ms
Probing 52.74.223.119:443/tcp - Port is open - time=1160.078ms
Probing 52.74.223.119:443/tcp - Port is open - time=151.960ms
Probing 52.74.223.119:443/tcp - Port is open - time=1157.914ms
Probing 52.74.223.119:443/tcp - Port is open - time=1172.587ms
Probing 52.74.223.119:443/tcp - No response - time=2000.507ms
Probing 52.74.223.119:443/tcp - Port is open - time=156.721ms
Probing 52.74.223.119:443/tcp - Port is open - time=1169.221ms
Probing 52.74.223.119:443/tcp - Port is open - time=168.544ms
Probing 52.74.223.119:443/tcp - Port is open - time=142.525ms
Probing 52.74.223.119:443/tcp - Port is open - time=138.443ms
Probing 52.74.223.119:443/tcp - Port is open - time=148.958ms
Probing 52.74.223.119:443/tcp - Port is open - time=140.405ms
Probing 52.74.223.119:443/tcp - Port is open - time=153.996ms
Probing 52.74.223.119:443/tcp - Port is open - time=151.621ms
Probing 52.74.223.119:443/tcp - Port is open - time=158.897ms
Probing 52.74.223.119:443/tcp - Port is open - time=149.869ms
Probing 52.74.223.119:443/tcp - Port is open - time=135.513ms
Probing 52.74.223.119:443/tcp - Port is open - time=147.747ms
Probing 52.74.223.119:443/tcp - Port is open - time=1173.130ms
Probing 52.74.223.119:443/tcp - Port is open - time=154.095ms
Probing 52.74.223.119:443/tcp - Port is open - time=159.471ms
Probing 52.74.223.119:443/tcp - Port is open - time=152.155ms
Probing 52.74.223.119:443/tcp - Port is open - time=178.374ms
Probing 52.74.223.119:443/tcp - Port is open - time=162.425ms
Probing 52.74.223.119:443/tcp - Port is open - time=153.748ms
Probing 52.74.223.119:443/tcp - No response - time=2001.547ms
Probing 52.74.223.119:443/tcp - Port is open - time=147.753ms
Probing 52.74.223.119:443/tcp - Port is open - time=150.426ms
Probing 52.74.223.119:443/tcp - Port is open - time=146.645ms
Probing 52.74.223.119:443/tcp - Port is open - time=140.087ms
Probing 52.74.223.119:443/tcp - Port is open - time=161.604ms
Probing 52.74.223.119:443/tcp - Port is open - time=1136.879ms
Probing 52.74.223.119:443/tcp - Port is open - time=155.782ms
Control-C
```

aver4vex

2021-03-10 11:34:33 +08:00

特殊时期，正常操作。别浪费时间在这上面

XIU2

2021-03-10 11:43:04 +08:00

就看两星期后是否会恢复了，如果没有恢复那估计离全面应用该机制不远了。

zeropercenthappy

2021-03-10 13:37:17 +08:00

@aver4vex 梯子刚好也挂了，可太难受了

ttoott200

2021-03-10 13:44:43 +08:00

用浏览器有时候可以打开，有时提示「连接已重置」，有时提示「 github.com 的响应时间过长」

XIU2

2021-03-10 13:47:25 +08:00

@ttoott200 #5 这是因为同一时间总会有一个（或多个） IP 是可用的状态，而似乎是随机或轮流进行 “超时” 的，可能是为了模拟丢包吧，这样很多人都会觉得是 Github 自身的问题（特别是不懂行的）。。。

2kCS5c0b0ITXE5k2

2021-03-10 14:04:51 +08:00

谷歌退出前就开始间歇性被干扰

systemcall

2021-03-10 14:58:13 +08:00

复习一下：
Google 全部上不去之前，是连接上去 10 分钟后阻断，让用户以为是 Google 自己的问题
现在的是开始访问就随机阻断，让用户有时候可以上。不过不仅上了 sni 嗅探来阻断连接，还通过这个连接来阻断对应的 IP 。看样子是在弄机器学习
反制：
用很多个代理的 IP 来把正常的 IP 这样子弄几下，天天换着弄，把墙搞疯

12101111

2021-03-10 15:10:20 +08:00

使用 https://github.com/12101111/nettest 测试
没有发现有阻断的情况, 就是延迟感人
网络是深圳电信，GitHub 的 IP 是新加坡 AWS

180 packets transmitted, 170 received, 5.56% packet loss, time 153181.598 ms
rtt min/avg/max/mdev = 287.697/901.068/4458.686/940.316 ms

https://gist.github.com/12101111/2788b039645579a682a866debf67d1e9

jdhao

2021-03-10 15:11:50 +08:00

有啊，wget 或者 git clone 都会概率性失败，挫败感很强

v2tudnew

2021-03-10 15:29:18 +08:00

@sillydaddy 你这没必要整个贴上去，太占地方了

dorothyREN

2021-03-10 18:21:18 +08:00

超不超时不清楚，反正最近几天 push 代码就没成功过

titan2006

2021-03-10 21:40:27 +08:00

当年谷歌也是这么被挤兑走的

zeromake

2021-03-11 08:22:12 +08:00

git 走 ssh 协议倒是一点事都没有

XIU2

2021-03-11 16:06:34 +08:00

@zeromake #14 因为 SSH 协议走的不是 443 端口，目前该机制只针对 443 端口。

不过这会议都结束了，该机制依然存在，不确定是不是要等两天才会取消，要么就是以后长期应用，甚至全面应用该机制。

zeropercenthappy

2021-03-12 08:52:48 +08:00

截止 21 年 3 月 12 日，广东电信、联通均未恢复。
凉凉。

learningman

2021-03-12 10:55:55 +08:00

@XIU2 问题是不懂行的谁用 github 啊。。。

XIU2

2021-03-12 11:04:40 +08:00

@learningman

并不是只有程序员才会去访问 Github 的（你不能只站在程序员的角度去看待问题）。

因为很多软件、网站、主题等等都是在 Github 上面开源的，因此也有很多普通人去反馈问题、提供建议，或者没注册账号只是单纯的去看项目的使用文档、下载文件（如 Release ）等等。

这些 “普通人” 占据很大的比例（其中大部分人都没注册账号，只看不发言）。

CrazyBoyFeng

2021-03-12 13:23:34 +08:00

@systemcall #8
阻断只影响到当前用户（本地 ip 或远程代理 ip ）与 github 的连接。弄正常 ip 对其他人没有影响吧？