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

AS266623 ·

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

Warning: AS266623 (AS266623) announces 7 IPv4 and 3 IPv6 prefixes. 3 warnings

AS pageAS266623
HolderAS266623 - 18.843.555 LTDA
AllocationLACNIC, Brazil (BR), allocated 2017-06-09
Prefixes (IPv4 / IPv6)7 / 3
RPKI valid100% (10 / 10)
Upstreams and peers13
Peering policyOpen

What to fix

  1. Warning

    2 of 10 announced prefixes have no IRR route object: 2804:3ed4:8000::/33, 2804:3ed4::/33.

    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 AS266623 in your RIR’s IRR database (or RADB).

    route6: 2804:3ed4:8000::/33
    origin: AS266623
    
    route6: 2804:3ed4::/33
    origin: AS266623

    Open in ASN & BGP prefix lookup

  2. 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

  3. 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 2 of 10 announced prefixes have no IRR route object: 2804:3ed4:8000::/33, 2804:3ed4::/33.
  • Pass: AS266623 announces 7 IPv4 and 3 IPv6 prefixes.
  • Pass: All 10 announced prefixes are RPKI valid.
  • Warning: 2 of 10 announced prefixes have no IRR route object: 2804:3ed4:8000::/33, 2804:3ed4::/33.
  • Info: 13 upstreams and peers, 7 downstream networks seen.
HolderAS266623 - 18.843.555 LTDA
IPv4 prefixes7
IPv6 prefixes3
RPKI10 valid
Without IRR route object2
Downstream networks7

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.
NameASN266623
Handle266623
RangeAS266623
CountryBR
Registered2017-06-09T11:20:55Z
Last changed2017-06-09T11:20:55Z
Abuse contactbgp@newconnectpe.com.br
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2017-06-09
StatusAllocated
Delegated rangeAS266623

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

Contacts
RoleNameEmail
registrant 18.843.555 LTDA
administrative, abuse Pedro Francisco bgp@newconnectpe.com.br

Source: https://rdap.lacnic.net/rdap/autnum/266623. 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: AS266623 is in PeeringDB as Pedro F Arruda Junior.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkPedro F Arruda Junior (NewConnect)
AS numberAS266623
Type, Regional
Websitehttp://www.newconnectpe.com.br
Prefixes (IPv4 / IPv6)7 / 1
Traffic10-20Gbps, Heavy Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup