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

AS29615 ·

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

Warning: AS29615 (PORTODIGITAL-AS) announces 1 IPv4 and 1 IPv6 prefixes. 4 warnings

AS pageAS29615
HolderPORTODIGITAL-AS Associacao Porto Digital
AllocationRIPE NCC, Portugal (PT), allocated 2015-05-26
Prefixes (IPv4 / IPv6)1 / 1
RPKI valid0% (0 / 2)
Upstreams and peers4

What to fix

  1. Warning

    2 of 2 announced prefixes have no ROA (RPKI not found): 185.101.176.0/22, 2a06:2000::/29.

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS29615 and a max length equal to the prefix length:

    185.101.176.0/22 AS29615 max-length /22
    2a06:2000::/29 AS29615 max-length /29

    Open in RPKI / ROA validator Guide

  2. Warning

    1 of 2 announced prefixes have no IRR route object: 2a06:2000::/29.

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

    route6: 2a06:2000::/29
    origin: AS29615

    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 2 of 2 announced prefixes have no ROA (RPKI not found): 185.101.176.0/22, 2a06:2000::/29.
  • Pass: AS29615 announces 1 IPv4 and 1 IPv6 prefixes.
  • Warning: 2 of 2 announced prefixes have no ROA (RPKI not found): 185.101.176.0/22, 2a06:2000::/29.
  • Warning: 1 of 2 announced prefixes have no IRR route object: 2a06:2000::/29.
  • Info: 4 upstreams and peers, 0 downstream networks seen.
HolderPORTODIGITAL-AS Associacao Porto Digital
IPv4 prefixes1
IPv6 prefixes1
RPKI2 not found
Without IRR route object1
Downstream networks0
Routes to fix
PrefixRPKI
185.101.176.0/22 No ROA
2a06:2000::/29 No ROA

Announced prefixes 2

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

Open in ASN & BGP prefix lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NamePORTODIGITAL-AS
HandleAS29615
RangeAS29615
Statusactive
Registered2015-05-26T13:51:04Z
Last changed2024-08-09T16:57:23Z
Abuse contactabuse@portodigital.pt
Allocation
Registry (RIR)RIPE NCC
CountryPortugal (PT)
Delegated on2015-05-26
StatusAllocated
Delegated rangeAS29615

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

Contacts
RoleNameEmail
registrant Associacao Porto Digital
registrant pt-aportodigital-1-mnt
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role abuse@portodigital.pt

Source: https://rdap.db.ripe.net/autnum/29615. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

Open in WHOIS / RDAP lookup
PeeringDB No IRR as-set is listed.
  • Pass: AS29615 is in PeeringDB as Associacao Porto Digital.
  • 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.
NetworkAssociacao Porto Digital
AS numberAS29615
Type, Not Disclosed
TrafficNot Disclosed
Ratio requiredNo
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup