based on user reports and queries over the last 24 hours
Postman outage statistics
- Official Website at https://www.postman.com;
- Support Center at https://support.postman.com;
- Community Forums at https://community.postman.com;
- GitHub Issues at https://github.com/postmanlabs;
- Status Page at https://status.postman.com;
- Submit ticket at https://support.postman.com/hc/en-us/requests/new;
- Premium support for paid plans.
- Official Website - https://www.postman.com;
- Blog - https://blog.postman.com;
- Documentation - https://learning.postman.com/docs;
- Status Page - https://status.postman.com;
- Community - https://community.postman.com;
- X (Twitter) - https://twitter.com/getpostman;
- LinkedIn - https://www.linkedin.com/company/postman-platform;
- YouTube - https://www.youtube.com/c/postman;
- GitHub - https://github.com/postmanlabs;
- Release Notes - https://www.postman.com/release-notes.
Service disruptions manifest as Postman app not opening, cloud sync failing, workspace inaccessible, collections not loading, or complete platform unavailable.
- Check internet connection stable;
- Visit https://status.postman.com for updates;
- Restart Postman application completely;
- Clear Postman cache and cookies;
- Try web version at https://web.postman.co;
- Update to latest Postman version;
- Disable VPN temporarily;
- Check firewall not blocking Postman;
- Wait 15-30 minutes for recovery;
- Monitor @getpostman on X for status.
Request issues include "Could not send request", timeout errors, connection refused, SSL errors, or requests hanging indefinitely.
- Check API endpoint URL correct;
- Verify internet connection working;
- Disable SSL certificate verification temporarily;
- Check proxy settings configured;
- Verify request method correct (GET/POST);
- Review headers and authentication;
- Test with simple GET request;
- Check firewall allows outbound connections;
- Increase timeout settings;
- Try sending via web version.
Sync problems include collections missing, changes not saving, "sync error" messages, workspace conflicts, or version control issues.
- Sign out and sign back in;
- Force sync from settings menu;
- Check cloud sync enabled;
- Verify stable internet connection;
- Resolve workspace conflicts manually;
- Export collection as backup;
- Check account storage limits;
- Clear local cache and re-sync;
- Verify team workspace permissions;
- Contact support for sync recovery.
Authentication problems include login failing, OAuth not working, API key errors, bearer token issues, or credential validation failures.
- Verify login credentials correct;
- Reset password if needed;
- Clear authentication tokens;
- Re-authenticate OAuth connections;
- Check API key format valid;
- Verify authorization header correct;
- Use environment variables for tokens;
- Test auth endpoint separately;
- Review auth type selected properly;
- Check token not expired.
Variable issues include variables not resolving, scope conflicts, initial values wrong, current values missing, or syntax errors.
- Check variable name spelling exact;
- Use double curly braces: {{variable}};
- Verify environment selected correctly;
- Set both initial and current values;
- Check variable scope (global/environment/collection);
- Review pre-request scripts;
- Verify no conflicting variable names;
- Use console to debug variables;
- Check variable persistence settings;
- Export and reimport environment.
Testing problems include tests not running, assertions failing, scripts timing out, console errors, or test results incorrect.
- Check JavaScript syntax in tests;
- Review test script logic carefully;
- Use console.log for debugging;
- Verify pm object methods correct;
- Check response format matches expectations;
- Review assertion syntax (pm.expect);
- Test scripts run after response;
- Check for async/promise issues;
- Verify newman compatibility if needed;
- Review Postman sandbox limitations.
Mock server problems include mock unavailable, incorrect responses, examples not matching, mock URL wrong, or rate limits exceeded.
- Verify mock server URL correct;
- Check example responses defined;
- Match request method and path exactly;
- Review mock server settings;
- Check mock server published;
- Verify request headers match;
- Test with exact example request;
- Check mock server not paused;
- Review rate limit quotas;
- Recreate mock if corrupted.
Newman issues include "newman command not found", run failures, reporter errors, collection import problems, or CI/CD integration failing.
- Install Newman: `npm install -g newman`;
- Verify Node.js installed properly;
- Update Newman: `npm update -g newman`;
- Export collection in v2.1 format;
- Use correct file path to collection;
- Specify environment file with `-e`;
- Check reporter installed correctly;
- Review Newman documentation;
- Use verbose flag for debugging;
- Verify collection JSON valid.
Documentation problems include docs not publishing, changes not reflecting, custom domain issues, version conflicts, or formatting broken.
- Republish documentation manually;
- Check collection changes saved;
- Verify publish settings correct;
- Clear browser cache for docs;
- Review custom domain configuration;
- Check version published is latest;
- Verify public link accessible;
- Review markdown formatting;
- Check examples included properly;
- Wait for CDN propagation.
Collaboration problems include team members missing access, role permissions wrong, invite emails not sent, workspace limits exceeded, or billing issues.
- Verify team member email correct;
- Check workspace role assigned properly;
- Resend invitation if needed;
- Review team workspace plan limits;
- Check billing account active;
- Verify member accepted invite;
- Review workspace permissions settings;
- Check seat availability;
- Sync workspace after changes;
- Contact admin for access issues.
Monitor issues include scheduled runs failing, monitor paused, notifications not sent, results missing, or quota exceeded.
- Check monitor enabled/not paused;
- Verify schedule configured correctly;
- Review monitor run results/logs;
- Check notification settings active;
- Verify integration webhooks working;
- Review monitor quota limits;
- Test collection runs manually first;
- Check environment variables set;
- Verify API endpoints reachable;
- Review monitor failure alerts.
Agent problems include agent not connecting, localhost requests failing, interceptor issues, cookies not capturing, or proxy errors.
- Download latest Postman Agent;
- Enable agent in settings;
- Check agent running in background;
- Verify localhost port accessible;
- Use agent for browser requests;
- Check interceptor extension installed;
- Review proxy configuration;
- Restart agent service;
- Check browser compatibility;
- Use desktop app for localhost.
Import/export problems include file format errors, import failing, corrupted exports, version incompatibility, or data loss.
- Verify file format valid JSON;
- Use Postman collection v2.1 format;
- Check file not corrupted;
- Try importing smaller collection;
- Export from same Postman version;
- Validate JSON syntax first;
- Import via URL if file fails;
- Check file encoding UTF-8;
- Review import error messages;
- Use API to import programmatically.
Postman
Your message will be published in about
5 minutes
Service administration will see your message