Where most complaints about this service are coming from, over the last 24 hours.
Shows where the service URL was unreachable during the detected outage periods. Percentages indicate the share of failed checks from monitoring locations in each country.
Tap what’s going wrong — one click helps thousands of others see the outage.
If Postman desktop refuses to open or crashes immediately, the most common culprit is a corrupted cache. Navigate to %AppData%\Postman (Windows) or ~/Library/Application Support/Postman (macOS), delete the Cache folder, and relaunch. If that doesn't help, reinstall the app — but export your collections first via File → Export.
When every request fails with 'Could not get any response' or 'ECONNREFUSED', check a few things in order:
If {{variable}} stays as a literal string in your request instead of resolving to a value, you've likely selected the wrong environment or none at all. Use the environment dropdown in the top-right corner and confirm the variable name matches exactly — Postman is case-sensitive here. Also check that the variable is set in the active scope, not just defined in a collection with no environment selected.
Cloud sync sometimes gets stuck after a network interruption. Sign out from the avatar menu, sign back in, and wait 30–60 seconds for the sync indicator to settle. If collections still don't match across devices, use File → Export on the up-to-date machine and import manually on the other.
Authentication errors almost always mean a token is expired or the auth header isn't being sent. Open the Postman Console (View → Show Postman Console) and inspect the actual request headers — not the UI, but what was really sent. If you use collection-level auth, make sure the request's own auth is set to 'Inherit from parent', not 'No Auth'.