Notices we send
Incident opened
Which service, which region, what customers may notice. Sent as soon as the provider confirms the problem, not when it is solved.
Progress updates
At agreed intervals while the incident lasts, so nobody has to refresh a status page or call the hotline.
Planned maintenance
Announced days in advance with the exact window and expected impact, plus a reminder shortly before it starts.
Resolved and post-mortem
Confirmation that everything is back, followed by a summary of cause and countermeasures where the provider publishes one.
Operating principles
Status mail is read in stressful moments. It has to be accurate, brief and free of anything else.
Only to those responsible
Notices go to the technical and billing contacts a customer registered for their contract, not to every address on file.
Status mail stays status mail
No upgrade offers, no product news, no satisfaction surveys in an incident or maintenance notice.
Subscribe by service
Customers choose which services they want notices for; the rest stays quiet.
Correct over fast
We would rather send an update five minutes later than send one that has to be withdrawn.
Contact
For hosting providers, for recipients of a notice and for blocklist operators:
Monitored on working days; reports about unwanted mail are handled first.