Planned maintenance
When planned work can affect availability or the user experience, it should be announced clearly with expected time, scope and what may be affected.
Transparency
Incidents, maintenance and service impact.
Last updated
No active incidents.
No planned impact.
How we communicate operations.
This page describes how TapInn announces planned maintenance, incidents and major deviations, and what you are told when something is not working.
In short. TapInn communicates planned maintenance, known incidents and major deviations. During serious operational issues, customers should get clear information about impact, not just technical codes.
When planned work can affect availability or the user experience, it should be announced clearly with expected time, scope and what may be affected.
For incidents affecting login, check-in, export, messages or other core flows, the status communication should describe the symptoms users actually see.
Once an incident is resolved, the communication is to be updated with what was affected, what was done, and whether customers need to do anything manually afterwards.
This page does not show uptime figures. During a deviation you are told what is affected, what users notice and what is being done.