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

AS263499 ·

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

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

AS pageAS263499
HolderAS263499 - Telecom Conectividade
AllocationLACNIC, Brazil (BR), allocated 2013-12-23
Prefixes (IPv4 / IPv6)7 / 17
RPKI valid100% (24 / 24)
Upstreams and peers1
Peering policyOpen

What to fix

  1. Warning

    18 of 24 announced prefixes have no IRR route object: 2804:12cc:1000::/36, 2804:12cc:8000::/36, 2804:12cc:5000::/36, 2804:12cc:c000::/36, 2804:12cc::/33 (+13).

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

    route6: 2804:12cc:1000::/36
    origin: AS263499
    
    route6: 2804:12cc:8000::/36
    origin: AS263499
    
    route6: 2804:12cc:5000::/36
    origin: AS263499

    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 18 of 24 announced prefixes have no IRR route object: 2804:12cc:1000::/36, 2804:12cc:8000::/36, 2804:12cc:5000::/36, 2804:12cc:c000::/36, 2804:12cc::/33 (+13).
  • Pass: AS263499 announces 7 IPv4 and 17 IPv6 prefixes.
  • Pass: All 24 announced prefixes are RPKI valid.
  • Warning: 18 of 24 announced prefixes have no IRR route object: 2804:12cc:1000::/36, 2804:12cc:8000::/36, 2804:12cc:5000::/36, 2804:12cc:c000::/36, 2804:12cc::/33 (+13).
  • Info: One upstream or peer seen (AS61591): an outage there takes the whole network off the internet.
HolderAS263499 - Telecom Conectividade
IPv4 prefixes7
IPv6 prefixes17
RPKI24 valid
Without IRR route object18
Downstream networks0

Upstreams and peers seen to the left 1

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.
NameASN263499
Handle263499
RangeAS263499
CountryBR
Registered2013-12-23T10:56:32Z
Last changed2019-05-03T17:57:13Z
Abuse contactrogerioveloso@westlink.com.br
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2013-12-23
StatusAllocated
Delegated rangeAS263499

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

Contacts
RoleNameEmail
registrant Telecom Conectividade
administrative, abuse WESTLINK TECNOLOGIA E COMUNICAÇÃO rogerioveloso@westlink.com.br

Source: https://rdap.lacnic.net/rdap/autnum/263499. 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: AS263499 is in PeeringDB as Telecom Internet.
  • 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.
NetworkTelecom Internet
AS numberAS263499
TypeCable/DSL/ISP, Regional
Websitehttp://www.telecomrj.net.br
Prefixes (IPv4 / IPv6)9 / 0
Traffic100-1000Mbps, Mostly Outbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup