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.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Problem: AS52747 (AS52747) announces 21 IPv4 and 6 IPv6 prefixes. 1 problem · 3 warnings
| AS page | AS52747 |
|---|---|
| Holder | AS52747 - Wsp Servicos de Telecomunicacoes Ltda |
| Allocation | LACNIC, Brazil (BR), allocated 2013-02-05 |
| Prefixes (IPv4 / IPv6) | 21 / 6 |
| RPKI valid | 96% (26 / 27) |
| Upstreams and peers | 10 |
| Peering policy | Open |
What to fix
-
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.
-
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
-
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.
-
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.
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.
| Holder | AS52747 - Wsp Servicos de Telecomunicacoes Ltda |
|---|---|
| IPv4 prefixes | 21 |
| IPv6 prefixes | 6 |
| RPKI | 26 valid · 1 invalid |
| Without IRR route object | 2 |
| Downstream networks | 10 |
| Prefix | RPKI |
|---|---|
| 2804:235c:10::/45 | RPKI invalid |
Announced prefixes 27
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.lacnic.net.
- Pass: Found at rdap.lacnic.net.
| Name | ASN52747 |
|---|---|
| Handle | 52747 |
| Range | AS52747 |
| Country | BR |
| Registered | 2013-02-05T09:23:43Z |
| Last changed | 2026-10-10T12:42:46Z |
| Abuse contact | oscar@wsp.net.br |
| Registry (RIR) | LACNIC |
|---|---|
| Country | Brazil (BR) |
| Delegated on | 2013-02-05 |
| Status | Allocated |
| Delegated range | AS52747 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| 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 lookupPeeringDB 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.
| Network | Wsp Servios de Telecomunicaes (WSP Telecom) |
|---|---|
| AS number | AS52747 |
| Type | Cable/DSL/ISP, Regional |
| Website | https://wsp.net.br |
| Prefixes (IPv4 / IPv6) | 150 / 50 |
| Traffic | 50-100Gbps, Mostly Inbound |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-04-24 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup