Status
one source degradedNothing here is a service you depend on being up: the server runs on your machine. What this page can report is which of the sources it may read are reachable from outside, and one of them is not.
2 of 3
network sources answering
One is slow and one is unreachable from the checker. Both are read-only
and neither stops a tool that does not need them.
0
of your sources here
Packages and the installation are on your machine. Nothing about them is visible to this page, by construction.
4 min
since the last check
Checked every five minutes from one location, which is a claim about that location and not about yours.
The six sources
Two of them are yours and cannot be reported on from here, which is stated in the table rather than left as a blank row.
| Source | What it needs | State | Last checked |
|---|---|---|---|
| knowledge | Nothing running — it ships with the server | answering | 4 min ago |
| checkout | Nothing running — the server’s own repository | answering | 4 min ago |
| packages | Files on disk, on your machine | not ours to report | — |
| installation | A booted installation, on your machine | not ours to report | — |
| docs.typo3.org | Outbound reach from your machine | slow · 2.4 s | 4 min ago |
| releases.typo3.org | Outbound reach from your machine | unreachable | 4 min ago |
What a degraded source costs you
A tool that declared it falls back to the next source it declared and says so in the result. Nothing waits, nothing retries silently, and no answer arrives without the substitution named in it.
docs.typo3.org is answering slowly
Documentation lookups take about 2.4 s instead of 300 ms.
Every other tool is unaffected: nothing else on this list reads from it.
releases.typo3.org is unreachable from the checker
Version discovery falls back to what the installation itself
declares, which is the release you are running rather than the newest
one that exists.
What this page is not
It is one location asking, every five minutes
A source that answers here may be unreachable from your network, and
the reverse. The tool’s own result is the authority for the machine it
ran on — this page is a hint about the sources, not a verdict.
There is no incident history, because there is no service
Nothing is hosted for you to depend on. What would be an outage
elsewhere is a degraded answer here, and the answer says so at the moment
it is given.