Vendor reports: partial outageOpen · vendor status “investigating”Official status API
[Google Search API] The "Site:" Operator is Ignored
Reported by SerpApi · Maps, Search & Data APIs · source last read 3 min ago
- Vendor start
- Nov 3, 2026, 20:45 UTC
- Vendor's clock
- Resolved
- Not yet
- Still open
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- Not available
- Needs both vendor times
Affected scope
Not stated by the vendor
The vendor's feed gives no region for this incident. It is not assumed to be global.
Potential relevance
SerpApi is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
What to check on your side
Verification steps only. Statuswall cannot see your systems.
- Check API error rates and quota responses for calls to SerpApi.
- Check error rates, latency and timeouts in your own monitoring for requests that depend on SerpApi.
- Look at synthetic checks and alerts that exercise SerpApi.
- Compare with recent deploys on your side, so a coincidental change is not blamed on the vendor.
- Follow the vendor's official incident page for scope changes and resolution.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Nov 3, 2026, 20:45 UTCVendor-reported startVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.