From Wikimedia Commons, the free media repository
Jump to: navigation, search
This template is deprecated.
Български | বাংলা | Čeština | Dansk | Deutsch | Zazaki | English | Esperanto | Español | Eesti | فارسی | Suomi | Français | Galego | Magyar | Italiano | 日本語 | 한국어 | Lietuvių | Македонски | മലയാളം | Nederlands | Polski | Português | Русский | Slovenščina | Српски / srpski | Svenska | ไทย | Türkçe | 中文 | 中文(简体)‎ | +/−
hist Toolserver status
Last update 1 July 2014
MySQL rosemary down
MySQL daphne down
MySQL yarrow down
Replag s1 N/A
Replag s2 N/A
Replag s3 N/A
Replag s4 N/A
Replag s5 N/A
Replag s6 N/A

This box shows the status of the Toolserver. This is a set of servers mainly from Wikimedia Deutschland that provides users a place to host their tools, such as web services and bots.

The information is updated hourly by BryanBot. If there is no update after an hour, it is likely that the entire toolserver is down.

The toolserver MySQL databases contain a replica of all Wikimedia wiki databases. Replication lag indicates how far the replication is behind real time. Services that read information from those databases will not return actual values, but values as they were at a time interval equal to the lag earlier. Replication lag particularly concerns Duesentrieb's check usage, which will return out-dated information if replication lag exists. It is possible that while the user bot (BryanBot) is up, the databases are down. When the databases are down, bots and web services that require them will not function.

Different wikis are on different database clusters (s1, s2, s3, s4, s5 and s7) and can thus have a different replication lag. See this post for information on s1, s2 and s3. Since February 2007, Commons has moved to s4 and de.wikipedia.org to s5. See also lag statistics graphs for a graphical view of the replication.