Yes, but I am not sure, what you are intending to measure there exactly. DBpedia Association runs on 15k€ membership fees yearly, which we mostly spend on travel grants so core community members can come to meetings.
Other than that it is a free services, as-is, without guarantees. So when there is a hickup, we need a couple of days/weeks to fix it.
Ideally, we would raise enough money to have a dedicated person maintaining the service and then breakage or delay will not occur any more. So if you are measuring this, you are actually assessing an economic factor, i.e. DBpedia not having enough money and staff to keep this in pristine condition at all times and provide SLA.
We could do a kickstarter…
Note that the delay here was caused by a wrongly configured log filling the boot partition and therefore didn’t allow writing to downloads.dbpedia.org any more. This is being fixed and also we added a check, which let’s us recognize earlier that such things happen. So it is improving, but only slowly.