+1 to that. AWS had issues in zone C today (and still not fully recovered). On the bunq status page there were no mentions that something was wrong, and the only clues we have that bunq was affected are the spikes on the latency graphs.
Would be great to see more proactivity there :-)
