Out of interest what had spontaneously caused those previously working specific firewalls to experience these problems.
Was it a result of planned maintenance, a lack of maintenance, an external source acting upon the firewalls ?
We now know the what but not the why, which would go some way to reassuring people of the likelyhood of a similar issue occuring.
a fair question ... the post incident report which we got this morning highlighted a planned change that was incorrectly deployed on Friday. So we're confident that it wont happen again, but we are reviewing all the processes around making changes of this type.
Not sure that last bit is correct. The giffgaff app was definitely not working at 6:30pm on Friday evening (and it wasn't just me that was experiencing that). Service was not restored to the app until some time during Saturday (daytime).
So what was that about? Was that a separate issue?
Thanks for the update, but my giffgaff app wasn't back to working order until Sunday night, which was annoying. Anyway, thankfully I was able to access it via a mobile browser (Chrome), so wasn't too bad. But hopefully this type of error can be avoided next time (i.e. as long as people can learn from mistakes, then minor glitches like this aren't too bad).