We were in the middle of shifting our entire architecture to Lambda when all hell broke loose.<p>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&#x27;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.<p>Days later, AWS us-east-1 went offline. Much of the internet went with it.<p>After it came online, everything was working well for me. We enjoyed near instant response times. Lambda was great, for a few days.<p>Then it started again. Hours of delay before the S3 events actually started the Lambda functions, and the logs once again lying.<p>We moved away from S3 triggers because it was unreliable. I really hope they fix the issues, but I&#x27;m not interested in relying on something that doesn&#x27;t work, with zero help in the forums, and requires an expensive service contract just to report broken services.