On 15/02/2020 11:36, Pannawit NiPA.CLOUD via CentOS-mirror wrote:

Hi Centos-mirror

We have come back again. pls update info as below.

HTTP: http://mirrors.nipa.cloud/centos/ HTTPS: https://mirrors.nipa.cloud/centos/ RSYNC: rsync://mirrors.nipa.cloud/centos FTP: ftp://mirrors.nipa.cloud/centos/

Sync schedule: Every 4 hrs Bandwidth: 10Gbit/s Location: Thailand ,Bangkok Sponsor: NIPA.CLOUD 1st Cloud Thailand Sponsor URL: https://www.nipa.cloud IPv4 address to authorize: 45.121.60.165 IPv6 address to authorize: 2406:7900:9000:200::61 Email contact: noc@nipa.co.th Mirroring AltArch : no

Thank you.

/Best Regards,/ /Pannawit B./ /Network Engineer Sup./ /NIPA Technology Co.,Ltd./ /T.+662-6397878 #119 M. +668-6-328-3030 /

---

*From: *"pannawit" pannawit@nipa.cloud *To: *"CentOS-mirror" CentOS-mirror@centos.org *Sent: *Sunday, December 31, 2017 12:13:29 PM *Subject: *[CentOS-mirror]  New CentOS mirror for Thailand

HTTP: http://mirrors.nipa.cloud/centos/ RSYNC: rsync://mirrors.nipa.cloud/centos/ FTP: ftp://mirrors.nipa.cloud/centos/

Sync schedule: Every 4 hrs Bandwidth: 10Gbit/s Location: Thailand ,Bangkok Sponsor: #1 Public Cloud Thailand Sponsor URL: https://www.nipa.cloud IPv4 address to authorize: 103.212.36.188 callto:103.212.36.188 IPv6 address to authorize: 2406:7900:9000:103:212:36:0:188 Email contact: noc@nipa.co.th Mirroring AltArch : no

As your mirror was considered "dead", I simply removed it and replaced with new/up2date entry in DB , so ...

Your mirror http://mirrors.nipa.cloud/centos/ has been added to the mirrors DB It will be listed as a public mirror (and on https://mirror-status.centos.org / https://www.centos.org/download/mirrors/ ) in the following minutes/hours. Your IP address[es] (45.121.60.165 2406:7900:9000:200::61) has/have been added in the ACL and so you should be able to rsync from msync.centos.org in the next ~10min

Kind Regards,