On 10/31/17 9:24 PM, Kubilay Kocak wrote: > Bugmeister (team responsible for the FreeBSD Bugzilla service) is aware > of the issue, which after initial investigation, has been reported > (escalated) to the FreeBSD infrastructure team, Cluster Admin. > > Root cause and estimated time to resolution (ETR) are currently unknown. > > Updates will be provided via at least this list (freebsd-ports), but > also potentially other appropriate channels as additional information > becomes available. >
Cluster Admin has identified the primary cause and are working toward resolving the issue [1]. Services interrupted are limited to those hosted in a single cluster. Estimated time to resolution is ~1hr. Services may be intermittently available until resolution is complete. [1] https://twitter.com/clusteradm/status/925296641036472320 _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
