Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

AS52747 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS52747"
JSON Docs

Problem: AS52747 (AS52747) announces 21 IPv4 and 6 IPv6 prefixes. 1 problem · 3 warnings

AS pageAS52747
HolderAS52747 - Wsp Servicos de Telecomunicacoes Ltda
AllocationLACNIC, Brazil (BR), allocated 2013-02-05
Prefixes (IPv4 / IPv6)21 / 6
RPKI valid96% (26 / 27)
Upstreams and peers10
Peering policyOpen

What to fix

  1. Problem

    1 of 27 announced prefixes are RPKI invalid: 2804:235c:10::/45.

    A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

    Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

    Open in RPKI / ROA validator Guide

  2. Warning

    2 of 27 announced prefixes have no IRR route object: 2804:235c:10::/45, 2804:235c:c00::/38.

    Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS52747 in your RIR’s IRR database (or RADB).

    route6: 2804:235c:10::/45
    origin: AS52747
    
    route6: 2804:235c:c00::/38
    origin: AS52747

    Open in ASN & BGP prefix lookup

  3. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  4. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI 1 of 27 announced prefixes are RPKI invalid: 2804:235c:10::/45.
  • Pass: AS52747 announces 21 IPv4 and 6 IPv6 prefixes.
  • Problem: 1 of 27 announced prefixes are RPKI invalid: 2804:235c:10::/45.
  • Info: 26 of 27 announced prefixes are RPKI valid.
  • Warning: 2 of 27 announced prefixes have no IRR route object: 2804:235c:10::/45, 2804:235c:c00::/38.
  • Info: 10 upstreams and peers, 10 downstream networks seen.
HolderAS52747 - Wsp Servicos de Telecomunicacoes Ltda
IPv4 prefixes21
IPv6 prefixes6
RPKI26 valid · 1 invalid
Without IRR route object2
Downstream networks10
Routes to fix
PrefixRPKI
2804:235c:10::/45 RPKI invalid

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.lacnic.net.
  • Pass: Found at rdap.lacnic.net.
NameASN52747
Handle52747
RangeAS52747
CountryBR
Registered2013-02-05T09:23:43Z
Last changed2026-10-10T12:42:46Z
Abuse contactoscar@wsp.net.br
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2013-02-05
StatusAllocated
Delegated rangeAS52747

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant Wsp Serviços de Telecomunicações Ltda
administrative, abuse OSCAR DO NASCIMENTO ALVES FILHO oscar@wsp.net.br

Source: https://rdap.lacnic.net/rdap/autnum/52747. Registration data from rdap.lacnic.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB No IRR as-set is listed.
  • Pass: AS52747 is in PeeringDB as Wsp Servios de Telecomunicaes.
  • Info: Peering policy: Open.
  • Info: Present at 1 internet exchanges with 1 ports (10.2G in total).
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
NetworkWsp Servios de Telecomunicaes (WSP Telecom)
AS numberAS52747
TypeCable/DSL/ISP, Regional
Websitehttps://wsp.net.br
Prefixes (IPv4 / IPv6)150 / 50
Traffic50-100Gbps, Mostly Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-04-24

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup