The main contact address for SixXS is firstname.lastname@example.org, which is the sole email address one should use to contact SixXS. Due to the international effort put into SixXS the official and sole language used is English.
We make status updates and announce news headlines on Twitter account @tweetsix. For questions though please use email as it is a publish-only feed, we do not follow it for questions/comments.
In case you are having issues with our services, don't hesitate to contact us.
But please follow the guidelines given below as it makes it so much easier to resolve problems.
Also, by reading the below guidelines and especially the FAQ most issues can be resolved.
When having configuration issues, don't hesitate to make use of the Forums.
We ask you to respect the following when contacting us:
Current Approval Queues
Didn't get a reply? Remember that patience is a virtue. If you uphold to the above rules then just wait a few days. At times there is an email backlog on our side, but we will come back to you at one point. There is also quite a lot happening behind the scenes and we actually also still have real work to do which gets priority. Resending the message doesn't make the message come through quicker, it will only cause the pile of emails to answer become longer and thus a reply to be delayed further. Also note that you might receive responses from multiple members of the opers team and that all the oper members read your messages, thus when addressing, address the whole team ('Hi SixXS') and not a individual team member.
As we strive to make the SixXS service available and useable for everybody, we are always interested in feedback. Thus if you encounter something which is not clear, too difficult, requires explanation or could be done better or in a different way which would improve the experience for the users, then do not hesitate to describe the problem and email it to our contact address. One can of course also discuss this in the Forum's "What can be done better" thread.
Abuse and related messages should be sent directly to email@example.com. SixXS has an Incident Response Team, as registered in the RIPE database with the IRT-SIXXS handle. Also see our Abuse FAQ and the above contact information. In case of reporting SPAM/UCE/Viruses, either attach them in a ZIP file or PGP encrypt your message. SixXS managed prefixes can be found in whois and in our own PoP Prefix List. IPv4 endpoint information of all tunnels can be found by quering whois.sixxs.net for the IPv6 address. When including data in the email that might be considered spam/virus, please either password-protect zip it and/or pastebin it somewhere refering to it in the email. Unfortunately we received too much spam on the abuse address to not restrict this.
SixXS uses the RIPE organization object ORG-SIXX1-RIPE and the role objects SIXT1-RIPE for RIPE, SATR1-AP for APNIC and STRA1-ARIN for ARIN which are applied to the various registry objects which are managed by SixXS. In case of issues with any object associated with that do not hesitate to contact us.
Reporting problems / Troubleshooting / Checklist
When describing a problem, either to the Opers in an email to the above address, or with a post in the Forum or in the Ticket System, please provide the following information where available and use it as a checklist to figure out where your problem might be, without it helping you resolv your problem becomes pretty much impossible, but with these details it becomes much easier, thus provide as much information as possible:
As stated below, we are not a helpdesk, but we are willing to help; we do need to have these details though, otherwise there is not much help that we can give. When these details are not provided, we will reply and simply point to this list.
Note that you should have read the FAQ first which we will refer to it directly. Some questions are also asked and answered in the Forums which is another place you can look first. We also handle the rule which says stupid questions become stupid answers.
The SixXS Forums provide a central place for IPv6 users around the world to communicate with each other. Even though it requires a SixXS login to post it isn't restricted to SixXS users. The forum is not meant for reporting problems or issues you have with your account or connectivity. Use the above contact details for those issues.
IRC Chat Channel
If you need to contact the SixXS Opers, depending on the problem, use the Ticket system or email.
SixXS Opers and Staff are not present on IRC to respond to your questions or comments.
We additionally have two status-only channels: #sixxs on both IRCnet and Freenode. Monitoring/status messages are available in this channel: User, tunnel, and subnet review queues, PoP status and other monitoring information is reported on this channel by the SixXS robot. These channels are moderated (+m) as they are solely status channels, please use the #ipv6 channel on Freenode for any IPv6 questions as there are a lot of active knowledgeable people present there who can help with an answer to your questions.
irssi users might want to use:
Though this channel allows for discussion about IPv6 and SixXS in general, it is not a contact method towards SixXS Opers/Staff even though they might be present.