@brMu 是上门办的，但是退号得去营业厅办取消套餐。

@nc4697 一年或者两年，到期了继续转...哪里有折扣转哪里

@iovekkk 是的，我打听到联通都是 500M 的，估计那个客户经理想多赚点。我的移动一开始也说 300M ，后面听到其它人有 600M ，我就说要 600M ，也给了。

@ArJun 不是，转网都有优惠，移动转电信好像也有 3-5 折，电信宽带香。

CDN 分级别的，看视频的热门度，很多都是野的 CDN ，就是 PCDN ，那用的都是别人的家宽，和热门视频用的机房宽带完全不一样。

Wechat 和 Weixin 是两个不同产品。

单可用区失效还是多可用区失效？

国行和美版不一样，美版有毫米波，频率越高能量越大。

搞那么复杂，WINDOWS 右键，共享，不就可以了吗？为什么还要第三方软件或者配置

要是国内访问的话，cloudfront 的线路比 cloudflare 差不是一点。

@ameizing 我不对公网开放端口的，通过 wireguard 连回我家里组局域网。

事件
EC2 operational issue
开始时间
2021 年 12 月 22 日 在 8:35:51 晚上 UTC+8
状态
开放
结束时间
-
区域 /可用区
us-east-1
类别
问题
特定于账户
No
受影响的资源
-
描述
API Error Rates

[04:35 AM PST] We are investigating increased EC2 launch failures and networking connectivity issues for some instances in a single Availability Zone (USE1-AZ4) in the US-EAST-1 Region. Other Availability Zones within the US-EAST-1 Region are not affected by this issue.

[05:01 AM PST] We can confirm a loss of power within a single data center within a single Availability Zone (USE1-AZ4) in the US-EAST-1 Region. This is affecting availability and connectivity to EC2 instances that are part of the affected data center within the affected Availability Zone. We are also experiencing elevated RunInstance API error rates for launches within the affected Availability Zone. Connectivity and power to other data centers within the affected Availability Zone, or other Availability Zones within the US-EAST-1 Region are not affected by this issue, but we would recommend failing away from the affected Availability Zone (USE1-AZ4) if you are able to do so. We continue to work to address the issue and restore power within the affected data center.

[05:18 AM PST] We continue to make progress in restoring power to the affected data center within the affected Availability Zone (USE1-AZ4) in the US-EAST-1 Region. We have now restored power to the majority of instances and networking devices within the affected data center and are starting to see some early signs of recovery. Customers experiencing connectivity or instance availability issues within the affected Availability Zone, should start to see some recovery as power is restored to the affected data center. RunInstances API error rates are returning to normal levels and we are working to recover affected EC2 instances and EBS volumes. While we would expect continued improvement over the coming hour, we would still recommend failing away from the Availability Zone if you are able to do so to mitigate this issue.

[05:39 AM PST] We have now restored power to all instances and network devices within the affected data center and are seeing recovery for the majority of EC2 instances and EBS volumes within the affected Availability Zone. Network connectivity within the affected Availability Zone has also returned to normal levels. While all services are starting to see meaningful recovery, services which were hosting endpoints within the affected data center - such as single-AZ RDS databases, ElastiCache, etc. - would have seen impact during the event, but are starting to see recovery now. Given the level of recovery, if you have not yet failed away from the affected Availability Zone, you should be starting to see recovery at this stage.

[06:13 AM PST] We have now restored power to all instances and network devices within the affected data center and are seeing recovery for the majority of EC2 instances and EBS volumes within the affected Availability Zone. We continue to make progress in recovering the remaining EC2 instances and EBS volumes within the affected Availability Zone. If you are able to relaunch affected EC2 instances within the affected Availability Zone, that may help to speed up recovery. We have a small number of affected EBS volumes that are still experiencing degraded IO performance that we are working to recover. The majority of AWS services have also recovered, but services which host endpoints within the customer’s VPCs - such as single-AZ RDS databases, ElasticCache, Redshift, etc. - continue to see some impact as we work towards full recovery.

[06:51 AM PST] We have now restored power to all instances and network devices within the affected data center and are seeing recovery for the majority of EC2 instances and EBS volumes within the affected Availability Zone. For the remaining EC2 instances, we are experiencing some network connectivity issues, which is slowing down full recovery. We believe we understand why this is the case and are working on a resolution. Once resolved, we expect to see faster recovery for the remaining EC2 instances and EBS volumes. If you are able to relaunch affected EC2 instances within the affected Availability Zone, that may help to speed up recovery. Note that restarting an instance at this stage will not help as a restart does not change the underlying hardware. We have a small number of affected EBS volumes that are still experiencing degraded IO performance that we are working to recover. The majority of AWS services have also recovered, but services which host endpoints within the customer’s VPCs - such as single-AZ RDS databases, ElasticCache, Redshift, etc. - continue to see some impact as we work towards full recovery.

[08:02 AM PST] Power continues to be stable within the affected data center within the affected Availability Zone (USE1-AZ4) in the US-EAST-1 Region. We have been working to resolve the connectivity issues that the remaining EC2 instances and EBS volumes are experiencing in the affected data center, which is part of a single Availability Zone (USE1-AZ4) in the US-EAST-1 Region. We have addressed the connectivity issue for the affected EBS volumes, which are now starting to see further recovery. We continue to work on mitigating the networking impact for EC2 instances within the affected data center, and expect to see further recovery there starting in the next 30 minutes. Since the EC2 APIs have been healthy for some time within the affected Availability Zone, the fastest path to recovery now would be to relaunch affected EC2 instances within the affected Availability Zone or other Availability Zones within the region.

为何会挂呢？我的树莓派放山上做气象站两年多了，还没挂过。

金沙江大拐弯居然想进去看还要拦路收费，恶心死，果断不看。

没人推荐坦克 500 ？国产陆巡，这个价格无敌。

1. 据我所知目前所有运营商的光猫不支持汇聚，不知运营商是否会给你 2.5G 口的光猫。
2. 如果 1 不成立，下面的就没必要 SFP+了。就算有 2.5G 的光猫，我看到楼主并没有 NAS ，似乎也没必要上 SFP+，全部 2.5G 有线+WIFI6 组网足矣。
3. 不建议用 PON Stick ，发热量巨大，能烧开水，非常不稳定，做好丢包掉线找不到原因的准备，而且千兆以上价格不菲。
4. 为何要用 mw5g ？直接上 WIFI6 了，带一个 2.5g 口的 WIFI6 设备 300 左右一个的价格。

广州宏发大厦去过一次，绕了很久才上 4 层，超级窄。