I’d like to propose adding service health/status visibility to the Outscraper API.
At times, certain services become temporarily unavailable or unstable. Currently, there is no programmatic way to clearly distinguish between user-side errors and internal service issues. Because of this, integrations continue sending requests, and end users experience failures without understanding whether the issue is upstream or local.
It would be very helpful if the API could expose structured service status information or return a clear, machine-readable “service temporarily unavailable” response when an internal issue is detected.
This would allow developers to pause affected processes, display accurate system notifications, implement smarter retry logic, and improve overall stability.
For teams building client-facing platforms on top of Outscraper, this would significantly increase reliability and reduce unnecessary support load.
I believe this improvement would make Outscraper even more robust for production-level integrations. Would love to hear feedback from the community.