We are experiencing a degradation in service this morning. AWS is having a major outage and by extension, some of our services are not working as they should.
Our team is actively on the lookout, investigating, and actively communicating with the AWS team. We anticipate that things should be running smoothly very soon. I am deeply sorry for the inconvenience this caused to your workflows and will keep this thread updated!
@gdemaderios Is there any contingency in place? Is Postman hosted on more than one cloud or On-prem? Or is it a single point of failure, and we have to wait it out?
Is there a way to send HTTP requests directly without enter a workspace? My work is held up right now, so I’m consider using another software like ApiFox.
The update from AWS as of a few minutes ago is that a potential root cause has been identified. The issue appears to be related to DNS resolution of the DynamoDB API endpoint in US-EAST-1, and they’re working hard to mitigate it ASAP.
There are significant signs of recovery, and many external services are slowly starting to come back to life now.
When will there be an offline version?
How is it possible that if you shut down the servers one day, you’ll take our entire collections to the grave with you?
This behavior in Postman is coming back to haunt us, because it always has to sync collections and environments and all that with the cloud instead of storing the data locally (for emergencies). But obviously, that’s not what they want. Now AWS is down, and with it, all Postmans.
Oh wait, the app is just a layer for the web application? Nothing runs natively anymore? Well, at least my move to alternatives is already in progress.
While https://status.postman.com/ still shows 100% operational. Postman and everything covered is just so broken for years now