Skip to content

Connector Health Report

This page provides real-time health status for all implemented connectors. Health checks verify that connectors can successfully access their target websites.

  • Total Connectors: 52
  • Healthy: 27
  • Unhealthy: 25
  • Last checked: 2026-02-25
Status Count Percentage
✅ Healthy 27 52%
❌ Unhealthy 25 48%
Connector Status Error
99acres-in ❌ UNHEALTHY Stream error (INTERNAL_ERROR) from peer
allhomes-au ✅ HEALTHY -
aqar-sa ❌ UNHEALTHY Forbidden
argenprop-ar ✅ HEALTHY -
commercialrealestate-au ✅ HEALTHY -
domain-au ✅ HEALTHY -
funda-nl ✅ HEALTHY -
harcourts ✅ HEALTHY -
harcourts-au ✅ HEALTHY -
harcourts-nz ✅ HEALTHY -
hausples-pg ✅ HEALTHY -
homedy ❌ UNHEALTHY Forbidden
homegate-ch ❌ UNHEALTHY Forbidden
homely-au ❌ UNHEALTHY Forbidden
homes-co-nz ✅ HEALTHY -
homes-nz ✅ HEALTHY -
housingsamoa-com ❌ UNHEALTHY DNS lookup failed: no such host
idealista-es ❌ UNHEALTHY Forbidden
immobiliare-it ❌ UNHEALTHY Forbidden
immobilienscout24-de ✅ HEALTHY -
inmuebles24 ❌ UNHEALTHY Forbidden
lamudi-mx ✅ HEALTHY -
maltapark ✅ HEALTHY -
marketmeri-pg ✅ HEALTHY -
mercadolibre-ar ✅ HEALTHY -
olx-br ❌ UNHEALTHY Forbidden
onthehouse-au ✅ HEALTHY -
openstreetmap ✅ HEALTHY -
point2homes-ca ✅ HEALTHY -
property-au ❌ UNHEALTHY Too Many Requests (429)
property-com-fj ❌ UNHEALTHY Connection reset by peer
property-com-pg ❌ UNHEALTHY DNS lookup failed: no such host
property-pg ❌ UNHEALTHY DNS lookup failed: no such host
realcommercial-au ❌ UNHEALTHY Too Many Requests (429)
realestate-au ❌ UNHEALTHY Too Many Requests (429)
realestate-nz ✅ HEALTHY -
realtor ✅ HEALTHY -
realtor-ca ✅ HEALTHY -
redfin ✅ HEALTHY -
reiwa-au ✅ HEALTHY -
rent-au ❌ UNHEALTHY Forbidden
rightmove-co-uk ✅ HEALTHY -
seloger-fr ❌ UNHEALTHY Forbidden
suumo-jp ✅ HEALTHY -
view-au ❌ UNHEALTHY Forbidden
vivanuncios-mx ❌ UNHEALTHY Forbidden
vivareal-br ❌ UNHEALTHY Forbidden
zapimoveis-br ❌ UNHEALTHY Forbidden
zigbang-kr ❌ UNHEALTHY Forbidden
zillow ✅ HEALTHY -
zolo-ca ❌ UNHEALTHY Forbidden
zonaprop-ar ❌ UNHEALTHY Forbidden

Status: ❌ UNHEALTHY
Error: failed to access https://homedy.com: Forbidden
Issue: Website returns 403 Forbidden, likely due to anti-bot protection
Possible Solutions:

  • Increase delay between requests
  • Rotate user agents
  • Use proxy rotation
  • Check if official API is available

Status: ❌ UNHEALTHY
Error: dial tcp: lookup housingsamoa.com on 1.1.1.1:53: no such host
Issue: DNS lookup failed - domain may not exist or is no longer registered
Possible Solutions:

  • Verify domain is still active
  • Check if domain has changed
  • Remove connector if site is permanently down

Status: ❌ UNHEALTHY
Error: Forbidden
Issue: Website returns 403 Forbidden, likely due to anti-bot protection
Possible Solutions:

  • Implement more sophisticated headers
  • Use browser automation if necessary
  • Check for API access

Status: ❌ UNHEALTHY
Error: Forbidden
Issue: Website returns 403 Forbidden, likely due to anti-bot protection
Possible Solutions:

  • Implement CAPTCHA handling
  • Use proxy rotation
  • Increase delays significantly

Status: ❌ UNHEALTHY
Error: dial tcp: lookup property.com.pg on 1.1.1.1:53: no such host
Issue: DNS lookup failed - domain may not exist or is inaccessible
Possible Solutions:

  • Verify domain accessibility
  • Check network connectivity
  • Remove if site is permanently down

Status: ❌ UNHEALTHY
Error: dial tcp: lookup property.com.pg on 1.1.1.1:53: no such host
Issue: DNS lookup failed - same domain as property-com-pg
Possible Solutions:

  • Verify domain accessibility
  • Consider consolidating with property-com-pg

Status: ❌ UNHEALTHY
Error: Too Many Requests
Issue: Website returns 429 Too Many Requests - rate limiting
Possible Solutions:

  • Significantly increase delay between requests
  • Implement exponential backoff
  • Reduce concurrent requests
  • Consider API access if available

Status: ❌ UNHEALTHY
Error: Forbidden
Issue: Website returns 403 Forbidden, likely due to anti-bot protection
Possible Solutions:

  • Implement more sophisticated anti-bot evasion
  • Use browser automation
  • Check for API access

Status: ❌ UNHEALTHY
Error: Forbidden
Issue: Website returns 403 Forbidden, likely due to anti-bot protection
Possible Solutions:

  • Implement CAPTCHA handling
  • Use proxy rotation
  • Check for official API

Status: ❌ UNHEALTHY
Error: Forbidden
Issue: Website returns 403 Forbidden, likely due to anti-bot protection
Possible Solutions:

  • Implement sophisticated anti-bot evasion
  • Use browser automation
  • Check for API access

Status: ❌ UNHEALTHY
Error: failed to access zolo.ca: Forbidden
Issue: Website returns 403 Forbidden, likely due to anti-bot protection
Possible Solutions:

  • Increase delay between requests
  • Rotate user agents
  • Use proxy rotation

Status: ❌ UNHEALTHY
Error: Forbidden
Issue: Website returns 403 Forbidden, likely due to anti-bot protection
Possible Solutions:

  • Implement more sophisticated headers
  • Use browser automation if necessary
  • Check for API access

Cause: Anti-bot protection blocking requests
Solutions:

  • Implement realistic browser headers
  • Rotate user agents
  • Use proxy rotation
  • Increase delays between requests
  • Consider browser automation

Cause: Rate limiting - too many requests too quickly
Solutions:

  • Increase delay between requests significantly
  • Implement exponential backoff
  • Reduce concurrent requests
  • Respect rate limit headers

Cause: Domain doesn’t exist or is inaccessible
Solutions:

  • Verify domain is still active
  • Check network connectivity
  • Verify DNS configuration
  • Remove connector if site is permanently down

Cause: Network issues or site is down
Solutions:

  • Check network connectivity
  • Verify site is accessible
  • Implement retry logic with backoff
  • Check firewall settings
Terminal window
cd connectors
./scripts/check_connector_health.sh

This script will:

  1. Iterate through all registered connectors
  2. Run health check for each
  3. Report status and errors
  4. Generate a summary
Terminal window
cd connectors
./bin/connector -connector <name> -health-check

Example:

Terminal window
./bin/connector -connector homes-co-nz -health-check

You can also check connector health programmatically:

connector := homes_co_nz.NewConnector()
err := connector.HealthCheck()
if err != nil {
log.Printf("Connector unhealthy: %v", err)
}

Each connector implements a HealthCheck() method that:

  1. Attempts to access the target website
  2. Verifies basic connectivity
  3. Returns an error if access fails
  4. Returns nil if healthy

Example implementation:

func (h *Connector) HealthCheck() error {
testURL := "https://www.example.com"
err := h.collector.Visit(testURL)
if err != nil {
return fmt.Errorf("failed to access %s: %w", testURL, err)
}
return nil
}
  • Run health checks daily or weekly
  • Monitor error trends
  • Track recovery from temporary issues
  • Document persistent failures

Set up alerts for:

  • Connectors that become unhealthy
  • Connectors that remain unhealthy for extended periods
  • Sudden increases in error rates
  • Update selectors when websites change structure
  • Adjust rate limits based on site responses
  • Remove connectors for permanently unavailable sites
  • Update anti-bot evasion techniques as needed

If you’d like to help fix unhealthy connectors:

  1. Identify the Issue: Review the error message and connector code
  2. Test Locally: Run health checks and scraping tests
  3. Implement Fix: Update the connector with fixes
  4. Verify: Run health checks to confirm fix
  5. Document: Update this page with resolution details

See Creating a New Connector for development guidelines.