We were in the middle of shifting our entire architecture to Lambda when all hell broke loose. I had delayed Lambda function calls. S3 triggers for Lambda were

We were in the middle of shifting our entire architecture to Lambda when all hell broke loose. I had delayed Lambda function calls. S3 triggers for Lambda were taking hours to actually start the process, but the logs were showing the actions happening immediately. They weren't happening immediately. It was easy to see that the S3 files were not being moved for hours, but the logs were reporting the wrong time. Days later, AWS us-east-1 went offline. Much of the internet went with it. After it came online, everything was working well for me. We enjoyed near instant response times. Lambda was great, for a few days. Then it started again. Hours of delay before the S3 events actually started the Lambda functions, and the logs once again lying. We moved away from S3 triggers because it was unreliable. I really hope they fix the issues, but I'm not interested in relying on something that doesn't work, with zero help in the forums, and requires an expensive service contract just to report broken services.