Submission-Type: new
Site: mirror.nevaedge.net
Archive-architecture: amd64 arm64 armel armhf hurd-i386 hurd-amd64 i386 loong64 mips mips64el mipsel powerpc ppc64el riscv64 s390x
Archive-http: /debian/
Maintainer: NevaEdge NOC <noc@nevaedge.com>
Country: RU Russian Federation
Location: Saint Petersburg
Sponsor: NevaEdge https://nevaedge.com
Comment: Full archive synced with ftpsync (upstream mirror.yandex.ru) four times a day at 03/09/15/21 MSK. Own hardware in Saint Petersburg, 1 Gbit/s uplinks; served over HTTPS from several edge nodes under one name. Trace: /debian/project/trace/mirror.nevaedge.net




Trace Url: http://mirror.nevaedge.net/debian/project/trace/
Trace Url: http://mirror.nevaedge.net/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirror.nevaedge.net/debian/project/trace/mirror.nevaedge.net

  Hello,





  a correction to our submission, please use the fields below instead of


  the original ones.





  Archive-architecture was wrong: it listed hurd-i386, hurd-amd64, mips


  and powerpc, which are not part of the main archive. /debian/ is a full


  mirror of everything ftp-master carries:





  Site: mirror.nevaedge.net


  Archive-architecture: amd64 arm64 armel armhf i386 loong64 mips64el
mipsel ppc64el riscv64 s390x

  Archive-http: /debian/


  Comment: Full archive synced with ftpsync four times a day
(03:30/09:30/15:30/21:30 MSK). Upstream is now mirror.mephi.ru (fed by
syncproxy2.eu.debian.org); mirror.yandex.ru has been
  unreliable since 12 Oct. Own hardware in Saint Petersburg, 1 Gbit/s
uplinks; served over plain HTTP and HTTPS from several edge nodes under one
name.



  Also fixed on our side since the original submission:


  - /debian/ is served over plain HTTP without a redirect to HTTPS;


  - the trace file is fresh again (syncs were failing 12-15 Oct due to


    the upstream), see


http://mirror.nevaedge.net/debian/project/trace/mirror.nevaedge.net





  Thanks,


  NevaEdge NOC