Excess flood – you attempted to send too much data to the IRC server too quickly. The server thought you were attempting to flood it, and so it disconnected you. If this is happening to you a lot, you should check to see if your client offers a setting that will prevent this (mIRC users: Options -> IRC -> Flood).

Max sendQ exceeded – you failed to receive the data from the server quick enough; the server tried to send you too much data and closed the connection. This could happen if you use /who on larger channels too often.

Ping timeout – In order to confirm that connections are still active, servers regularly send out ping requests. When a client doesn’t respond to this within a set period of time, 2 minutes on GeekShed, it believes that the connection no longer active, and closes it. If this happening to you often, you should try using the closest server to you (or the next closest, if you’re already using the closest).

Connection reset by peer – when the IRC client uncleanly closes the connection to the server , the server may not realize that the connection has been terminated. In this situation, the user still appears to be online (a ghost user). The next time the server attempts to send data to the client, it realizes the connection no longer exists and resets it; the ghost is then disconnected.

Broken pipe – when there is a sudden break in the connection between the IRC server and client, the user will disconnect with this message.

*.geekshed.net *.geekshed.net – this is a netsplit, or when one server loses its connection from the rest of the network. For a more detailed explanation, as well as images, view the WikiPedia entry on Netsplits.

G:lined or Z:lined – for some reason, the user has been banned from the network. The reason, as well as a URL where the person may find more information is always given when staff ban someone. For information on the ban appeal process, please see the Ban Appeals page.

Killed (nick (reasons)) – this is given when a user has been forcibly disconnected from the network by a staff member. The staff member’s name and a reason are always given. This should be viewed as a warning, and the user may be banned if the behavior continues.