Distfile availability status for databases/mariadb55-server
Status codes:
- numeric values represent RFC 2616 status codes
- NXDOMAIN means that the hostname could not be resolved
- network timeouts result in code 500
It is possible that a failed check could work now. Status codes between 500-599 are transient errors and the status you see represents the period of time when the distfile was checked.
Ports that set DEPRECATED, FETCH_CMD, FETCH_ENV, FETCH_BEFORE_ARGS, FETCH_AFTER_ARGS, or have a do-fetch: target are simply skipped.
All the tables have clickable headers that sort the table by the clicked column.
back
show bad only,
cvsweb,
other ports from this maintainer
| URL |
Checked |
Last OK |
Status |
| http://mirror.layerjet.com/mariadb/mariadb-5.5.30/kvm-tarbake-jaunty-x86/mariadb-5.5.30.tar.gz |
2013-05-23, 11:23:42 |
|
200 |
| http://gd.tuwien.ac.at/db/mariadb/mariadb-5.5.30/kvm-tarbake-jaunty-x86/mariadb-5.5.30.tar.gz |
2013-05-23, 23:38:56 |
|
200 |
| http://mirrors.fe.up.pt/pub/mariadb/mariadb-5.5.30/kvm-tarbake-jaunty-x86/mariadb-5.5.30.tar.gz |
2013-05-24, 05:25:43 |
|
200 |
| http://ftp.osuosl.org/pub/mariadb/mariadb-5.5.30/kvm-tarbake-jaunty-x86/mariadb-5.5.30.tar.gz |
2013-05-23, 10:19:14 |
|
200 |
| http://mariadb.org/ |
2013-05-23, 13:14:10 |
|
200 |
| http://mirrors.supportex.net/mariadb/mariadb-5.5.30/kvm-tarbake-jaunty-x86/mariadb-5.5.30.tar.gz |
2013-05-23, 08:14:37 |
|
200 |
| http://mirror2.hs-esslingen.de/pub/Mirrors/mariadb/mariadb-5.5.30/kvm-tarbake-jaunty-x86/mariadb-5.5.30.tar.gz |
2013-05-24, 01:34:30 |
N/A |
404 |
| http://mirror.switch.ch/mirror/mariadb/mariadb-5.5.30/kvm-tarbake-jaunty-x86/mariadb-5.5.30.tar.gz |
2013-05-23, 16:58:40 |
N/A |
404 |
| http://mirror.de.gsnw.de:56431/mariadb/mariadb-5.5.30/kvm-tarbake-jaunty-x86/mariadb-5.5.30.tar.gz |
2013-05-24, 03:32:04 |
N/A |
500 |
| http://mirror.aarnet.edu.au/pub/MariaDB/mariadb-5.5.30/kvm-tarbake-jaunty-x86/mariadb-5.5.30.tar.gz |
2013-05-23, 08:39:57 |
2013-05-22, 14:24:25 |
500 |