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.
Warning: AS262424 (AS262424) announces 14 IPv4 and 18 IPv6 prefixes. 3 warnings
| AS page | AS262424 |
|---|---|
| Holder | AS262424 - InterSoft Internet Software EIRELI |
| Allocation | LACNIC, Brazil (BR), allocated 2011-03-24 |
| Prefixes (IPv4 / IPv6) | 14 / 18 |
| RPKI valid | 100% (32 / 32) |
| Upstreams and peers | 3 |
| Peering policy | Open |
What to fix
-
Warning
21 of 32 announced prefixes have no IRR route object: 2804:6164:200::/42, 177.44.134.0/24, 2804:6164:c0::/42, 2804:6164:a000::/35, 2804:6164:8000::/35 (+16).
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 AS262424 in your RIR’s IRR database (or RADB).
route6: 2804:6164:200::/42 origin: AS262424 route: 177.44.134.0/24 origin: AS262424 route6: 2804:6164:c0::/42 origin: AS262424
-
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 21 of 32 announced prefixes have no IRR route object: 2804:6164:200::/42, 177.44.134.0/24, 2804:6164:c0::/42, 2804:6164:a000::/35, 2804:6164:8000::/35 (+16).
- Pass: AS262424 announces 14 IPv4 and 18 IPv6 prefixes.
- Pass: All 32 announced prefixes are RPKI valid.
- Warning: 21 of 32 announced prefixes have no IRR route object: 2804:6164:200::/42, 177.44.134.0/24, 2804:6164:c0::/42, 2804:6164:a000::/35, 2804:6164:8000::/35 (+16).
- Info: 3 upstreams and peers, 9 downstream networks seen.
| Holder | AS262424 - InterSoft Internet Software EIRELI |
|---|---|
| IPv4 prefixes | 14 |
| IPv6 prefixes | 18 |
| RPKI | 32 valid |
| Without IRR route object | 21 |
| Downstream networks | 9 |
Upstreams and peers seen to the left 3
Announced prefixes 32
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 | ASN262424 |
|---|---|
| Handle | 262424 |
| Range | AS262424 |
| Country | BR |
| Registered | 2011-03-24T18:28:23Z |
| Last changed | 2017-08-04T13:33:56Z |
| Abuse contact | gbi@gbi.com.br |
| Registry (RIR) | LACNIC |
|---|---|
| Country | Brazil (BR) |
| Delegated on | 2011-03-24 |
| Status | Allocated |
| Delegated range | AS262424 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | InterSoft Internet Software EIRELI | |
| administrative, abuse | eliezer santana lima | gbi@gbi.com.br |
Source: https://rdap.lacnic.net/rdap/autnum/262424. 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: AS262424 is in PeeringDB as InterSoft Internet Software EIRELI.
- Info: Peering policy: Open.
- Info: Present at 1 internet exchanges with 1 ports (10G in total).
- Warning: No IRR as-set is listed.
- Warning: No public NOC, policy or technical contact.
| Network | InterSoft Internet Software EIRELI (Rede InterSoft) |
|---|---|
| AS number | AS262424 |
| Type | Cable/DSL/ISP, Regional |
| Website | https://planos.redeintersoft.com.br/ |
| Prefixes (IPv4 / IPv6) | 400 / 600 |
| Traffic | 50-100Gbps, Heavy Inbound |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-07-14 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup