Known Issues
Current known issues, their status, and mitigation strategies for Adult Model Protection
Overview
This page documents known issues affecting the Adult Model Protection platform. We maintain transparency about current limitations and actively work to resolve them. Each issue includes its status, impact, and any temporary workarounds or mitigations in place.
Last Updated: February 16, 2026 (Updated: Bing re-enabled, new scan types added)
Active Issues
No active issues at this time. All search engines are operational.
Resolved Issues
✅ Bing Search Engine - Re-enabled (RESOLVED)
Issue ID: BUG-2025-1101
Severity: High
Status: ✅ Resolved
Reported: November 11, 2025
Resolved: February 16, 2026
Category: Automated Scanning
Description
The Bing search engine integration was experiencing HTTP 503 errors due to incorrect API parameters. SerpAPI advised using mkt (market) and location parameters instead of the deprecated cc (country code) parameter.
Root Cause
The cc (country code) parameter was causing inaccurate results and 503 errors on SerpAPI's Bing integration. Switching to mkt (e.g., en-US) and location (e.g., United States) resolved the issue.
Resolution
- Updated all Bing engine configurations to use
mktandlocationparameters - Bing web search, Bing Images, and Bing Reverse Image Search all re-enabled
- Verified working correctly with adult content queries
- Deployed February 16, 2026
Current Engine Status
All 5 search engines + 2 image engines + forum search are now active:
- Google - Primary text search engine
- Bing - Re-enabled with corrected parameters ✅
- Yahoo - Reliable backup
- DuckDuckGo - Privacy-focused search
- Yandex - International coverage
- Google Images - Visual content detection
- Bing Images - Additional image search coverage (NEW)
- Google Forums - Reddit, Quora, and forum monitoring (NEW)
✅ Bing URL Encoding - Incorrect Results (RESOLVED)
Issue ID: BUG-2025-1110
Severity: Critical
Status: ✅ Resolved
Resolved: November 11, 2025
Category: Automated Scanning
Description
Bing was returning results from incorrect domains (Wikipedia, news sites) instead of target adult content sites when using site-specific search queries.
Root Cause
The URLSearchParams API was URL-encoding quotes in the search query ("Model Name" → %22Model+Name%22), which broke Bing's site: operator syntax.
Solution
Manually constructed API URLs with only spaces encoded as +, preserving quote characters unencoded. This matches SerpAPI's exact format and allows the site: operator to function correctly.
Verification
- ✅ Bing now returns results from target sites only
- ✅ No more Wikipedia or news article results
- ✅ All three search engines working correctly
- ✅ Deployed to production November 11, 2025
Monitoring & Escalation
How We Track Issues
-
Detection: Issues are identified through:
- Automated monitoring and error tracking
- User reports and support tickets
- Regular testing and quality assurance
- Third-party provider status pages
-
Triage: Each issue is assessed for:
- Severity (Critical, High, Medium, Low)
- Impact (number of users affected)
- Scope (feature area affected)
- Root cause (internal vs. third-party)
-
Resolution: Issues are resolved through:
- Internal code fixes
- Third-party provider coordination
- Workarounds and mitigations
- User communication
Escalation Path
Internal Issues:
- Identified and logged
- Assigned to development team
- Fixed and tested
- Deployed to production
- Users notified
Third-Party Issues:
- Identified and logged
- Reported to provider
- Tracked on provider's status page
- Temporary workaround implemented
- Users notified of timeline
- Re-enabled when provider fixes issue
Impact by Severity
Critical (🔴)
- Platform is unavailable or severely degraded
- Data loss or security issues
- Affects all or most users
- Requires immediate action
High (🟠)
- Major feature is broken or unavailable
- Affects significant number of users
- Workaround available but limited
- Requires urgent resolution
Medium (🟡)
- Feature is partially broken or degraded
- Affects some users or specific use cases
- Workaround available
- Should be resolved soon
Low (🟢)
- Minor feature issue or cosmetic problem
- Affects few users
- Workaround available
- Can be resolved in regular maintenance
Performance & Limitations
Current Limitations
Scanning Coverage:
- Active Text Engines: Google, Bing, Yahoo, DuckDuckGo, Yandex (5 of 5)
- Active Image Engines: Google Images, Bing Images (2 of 2)
- Forum Monitoring: Google Forums (Reddit, Quora, Facebook groups)
- Reverse Image: Google Reverse Image, Bing Reverse Image
- Disabled Engines: None
- Coverage: Full capacity
Search Limitations:
- Maximum 50 pages per search engine (500 results)
- Rate limiting: 1 request per second per engine
- Timeout: 60 seconds per request
- Geographic restrictions: US-based searches only
Database Limitations:
- Model names: Unlimited for all paid plans (Free: 1)
- Maximum 500+ monitored sites per account
- Result retention: 90 days (configurable)
- Export limit: 10,000 results per export
Frequently Asked Questions
Q: Will my scanning be affected?
A: Minimally. Google and Yahoo provide ~80-85% of the coverage that all three engines would provide. You'll continue to receive comprehensive results.
Q: Will I be charged for the missing Bing results?
A: No. You're only charged for successful API calls. Disabled engines don't incur charges.
Q: When will Bing be fixed?
A: We don't have a specific timeline. SerpAPI is working on the issue. We check weekly and will re-enable immediately when it's fixed.
Q: Are my results being manually reviewed?
A: Yes. Our trained agents continue to manually search Bing results at no additional cost to ensure you don't miss unauthorized uses.
Q: What should I do if I find an issue?
A: Please report it to our support team at [email protected] with:
- Description of the issue
- When it started
- Steps to reproduce (if applicable)
- Screenshots (if applicable)
Reporting Issues
How to Report
If you encounter an issue not listed here:
- Email Support: [email protected]
- In-App Support: Use the help widget in your dashboard
- Documentation: Check our troubleshooting guide
Information to Include
- Issue Description: What's happening?
- Affected Feature: Which feature is affected?
- Steps to Reproduce: How can we reproduce it?
- Expected Behavior: What should happen?
- Actual Behavior: What's actually happening?
- Screenshots: Visual evidence (if applicable)
- Browser/Device: What are you using?
- Timestamp: When did it occur?
Issue History
November 2025
| Date | Issue | Status | Category |
|---|---|---|---|
| Nov 12 | Bing Search Engine - Incorrect Results | 🔴 Active | Automated Scanning |
| Nov 11 | Bing URL Encoding - Incorrect Results | ✅ Resolved | Automated Scanning |
Contact & Support
Questions about known issues?
- Email: [email protected]
- Help Centre: https://docs.adultmodelprotection.com
Want to report an issue?
- Use the in-app support widget
- Email: [email protected]
- Include as much detail as possible
Last Updated: November 12, 2025
Next Review: November 19, 2025
Status: 1 Active Issue, 1 Resolved Issue