Yesterday I got email from SBML mailing list about release of BioModels Database's first Mirror site at Caltech. I am very much surprise, especially why BioModels database need a mirror site, consider the fact- size of whole BioModels database is around 3.46 MB (compressed twelfth release) which consist of 293 models including both curated non curated branch. Now days this is very common trend to have multiple mirrors for biological databases, for example there are about 17 official BNL PDB web site mirrors. A mirror resource can be a database mirror (such as ClamAV), web site mirror (such as PDB or BioModels), or it can be a repository mirror (such as SourceForge). One of the primary reason to maintain mirrors is to increase resources availability, and these mirrors help to uphold minimum services in failure and high traffic situations. Normally user should be automatically redirected to closest mirror service, which will ensure accessibility and speed of a resource. Geographic distribution of web content via mirror sites is critical to balance the traffic between all mirrors. Most of biological database mirrors are web site mirrors and they are also not mirrors in true sense, they are more isolated replicates of the principal database. Principal server (URL) never redirects users to their nearest geographical mirrors, not even in high traffic situations, believe it or not most of us never use these mirror sites. If I have to browse the PDB structures then I will just point my browser to main RSCB website, and not to those 17 PDB mirrors. Maintaining these bio-mirrors by putting so much resources on hold does not serve any purpose, at least I am not convinced why we need this kind of mirrors. BioModels is special case and due to it's small size it does not need very huge resources to maintain a mirror, but I am not sure about others.