| ▲ | 6LLvveMx2koXfwn an hour ago | |
Not sure whether it has been updated since your comment, but the sentence now reads:
edit: although they also have 1.2 days of downtime (in a day) for their 'worst days' of downtime table, which suggests some auto number crunching is not working as expected. | ||
| ▲ | gen220 an hour ago | parent [-] | |
Yes I tweaked it! The number and copy were mismatched and are no longer! That worst day is likely an overlapping incidents accounting issue; I tried to account for overlapping incidents in another view but probably failed to port it over there. Should be fixed soon! | ||