Unstable network at Linevast
Summary
After massive network problems the day before, I publicly asked the hosting provider Linevast when a stable connection could be expected again; I did not know the cause. The network problems occurred on 30 March 2016. My public question to Linevast followed on 31 March 2016.
Ideas
- An outage becomes traceable through its time window, provider and observed impact.
- Public questions can add status information when there is no incident report.
- An unknown cause should be kept clearly apart from the observed symptoms.
- Reachability alone says little about packet loss, latency and usable quality.
Insights
- Transparent status communication is a part of reliable hosting in its own right.
- Without measurements and a final report, unexplained outages are hard to assess later.
- For operators, stability means more than a server that simply answers.
Facts
- No confirmed technical cause was available.
Recommendations
- Log outages with timestamps and measurements from several networks.
- Keep confirmed causes strictly apart from assumptions.
- Ask for a comprehensible incident report after longer outages.
References
Links to the original source and the Web Archive open in a new tab.